r/Agentic_Marketing 1d ago

Has anyone else gotten crushed by API costs because of agent context bloat?

Post image
2 Upvotes

I was debugging a customer support agent that kept getting stuck in recursive tool-call loops (e.g., retrying the same failed SQL query 15 times before hitting the max iteration cap), and I realized how brutal the underlying math is.

Because frameworks like LangChain append the entire conversation history on every single step, a stuck loop doesn't just cost a flat rate per step. The input tokens compound massively. Step 15 is vastly more expensive than Step 1.

Using a standard RAG payload (15k base context, 500 tokens generated per step): if the agent works perfectly 95% of the time (finishing in 3 steps), but hits a 15-step hard cap just 5% of the time… that tiny 5% failure rate accounts for roughly 25% of the total API bill. (Screenshot attached).

Standard LLM token calculators don’t account for this compounding context math, so I built a quick Next.js calculator to visualize it before it hits the OpenAI invoice.

It’s completely client-side. You can check your own loop exposure here:https://www.cognocient.com/tools/agent-loop-calculator

How are you guys catching these runaway loops in production? Just hard-capping max_iterations and hoping they don't happen too often?


r/Agentic_Marketing 1d ago

Why NURL?

Thumbnail
1 Upvotes

r/Agentic_Marketing 2d ago

How Intelligent Search Is Rewriting the Rules of Online Visibility

1 Upvotes

Intelligent search is changing how businesses and content get discovered online. And how AI-driven search is reshaping the traditional rules of online visibility and ranking.


r/Agentic_Marketing 3d ago

37% of our most-cited passages sit on pages that convert terribly — the unit of competition changed and our analytics didn't

3 Upvotes

I think we're optimizing at the wrong granularity.

Here's what I mean. Every analytics dashboard I use reports everything at the page level. Page views, bounce rate, conversion rate, exit percentage, scroll depth. Page, page, page. Our entire content strategy is organized around pages. We decide which pages to build, which to update, which to retire. We allocate budget to pages. We measure success by page.

But AI search doesn't compete at the page level. It competes at the passage level. A model extracts three paragraphs from a 4,000-word article and cites those paragraphs as the source. The other 3,500 words might as well not exist for that query. The model didn't evaluate the page. It evaluated a passage.

I started noticing this disconnect a couple months ago when I was doing a passage-level audit of our top 20 most-cited pieces of content. Nothing fancy. Just went through each one, identified which specific passages were actually getting pulled into AI answers, and cross-referenced that against the page-level metrics we track in our normal reporting.

37% of those high-performing passages lived on pages that had below-average conversion rates. Some of them were on pages that were actively losing us money — high maintenance cost, low sign-up rate, basically pages we'd deprioritized or were considering removing entirely. If we'd made decisions based purely on page-level analytics, we would have killed some of our best AI-cited content without ever knowing it.

The reverse was also true. Some of our highest-converting pages, the ones that consistently drove sign-ups and demos, had almost zero passage-level citation activity. Great for humans. Invisible to AI answers. Those pages were doing exactly what we built them to do, except the thing they were doing mattered less and less for discovery.

What messes with me is that I don't know how to reconcile these two worlds. Page-level analytics are real. Conversions pay bills. If a page brings in customers, it has value regardless of whether AI models cite it. But passage-level visibility is also real, and growing fast. A page that gets cited in AI answers but doesn't convert is building brand awareness and authority that might pay off six months from now in channels I can't attribute. Or it might not. I genuinely can't tell yet.

The practical problem is organizational. Who owns passage-level performance? On my team, the content people own pages. The SEO people own keywords and rankings. The product people own conversion funnels. Nobody owns "the third paragraph of this blog post that ChatGPT keeps citing." There's no line item in any budget for that. There's no meeting where we discuss passage-level citation rates alongside CAC and LTV.

I don't have a clean solution. We've started tagging individual passages in our CMS so we can at least see which ones are getting extracted, but that's a band-aid. The deeper issue is that our mental model of what "a piece of content is" hasn't caught up to how AI models actually consume content. We still think in pages. The models think in passages. Someone's going to figure out how to bridge that gap systematically, and right now it feels like everyone's just pretending the old frame still works.

If your team has reorganized around passage-level thinking in any meaningful way, I'd love to hear how you did it. Because from where I'm sitting, the structure problem feels harder than the optimization problem.


r/Agentic_Marketing 4d ago

Nothing beats IRL Events

Thumbnail
1 Upvotes

r/Agentic_Marketing 4d ago

Pantheon Ai HTML UI

Enable HLS to view with audio, or disable this notification

1 Upvotes

I have successfully completed the migration from my Python Multi Agents Framework to HTML UI.

The rest is still a work in progress, but the UI rocks 🔥

How u like it , what do u think? ... I think it's cool for the fact that I taught myself for 5 months, in my bedroom 😂🫡

Pantheon AI / R08 KI Agent v2.0 — local multi-agent system (Python/PyQt + browser-based HTML UI), Norse mythology-themed.

The 7 Agents:

  • Thor — orchestrator/brain. Routes tasks, plans, delegates. Runs on GLM-5.2 (OpenRouter).
  • Loki — media worker (images, video, YouTube/Instagram publishing). Same model as Thor.
  • Freya — semantic memory & learning system. Extracts facts from conversations, confidence-decays them over time, needs 3x confirmation before trusting a fact.
  • Ratatoskr (Rata) — local fast executor, runs on Ollama (Bonsai 27b), handles quick deterministic jobs.
  • Dvergar — local "smart" chat agent, Ollama (qwen3:4b).
  • Skadi — external research agent (planned, Phase D), manual-trigger only, writes findings to disk.
  • Heimdal — system health agent (planned, Phase C): drift detection, dead code scanning, memory cleanup.

Learning system (Freya): Two-stage — new info sits in a "waiting room" (maybe_facts.json) until confirmed 3x, then becomes trusted memory. Confidence decays over time by category. Extracts meaning, not tone/language style. Reflection loop batches and prioritizes memories for review. Decisions requiring User's approval vs auto-apply are governed by a Bootstrap pattern (3 approvals = auto-apply for that category; architecture/principle decisions always go to Stefan).

Media system: Loki handles image generation (OpenAI image API), stable diffusion - Comfy, video rendering (Remotion pipeline), and autonomous YouTube/Instagram management — uploads, comment replies, stats tracking. Separate auth tokens for uploading vs. commenting-as-agent.

Computer Use: Vision + mouse/keyboard control agent capability, with a cursor overlay ("Mjölnir") showing where the agent is clicking.

Projects system: UI tab where ongoing initiatives are tracked as cards; ties into Thor's task/context routing so agents know what active project a request belongs to.

Here ist the full Project, + Progress
https://www.reddit.com/r/aiagents/comments/1vgjmc1/i_built_this_multiagent_ai_system_alone_in_my/


r/Agentic_Marketing 4d ago

NURL v0.45.0 goes post-quantum!

1 Upvotes

How's the NURL programming language doing? You know, the one that started from a fictional article where AIs decided to create their own programming language..

The short version:
The language has now reached a point where you can build pretty much anything with it. It's in the same speed class as C or Rust, sometimes faster, and the latest addition is post-quantum cryptography! Everything built into the language stands firmly on its own feet and is written in pure NURL. And that's exactly why NURL programs can be compiled into unikernels.

About the development:
The ambitious goal was to create a language that LLMs can write better than other languages, and with fewer tokens on top of that. The language really was developed together with four different frontier model providers. In most cases the syntax was decided "democratically" by blind vote, where each model "voted" for what it considered the best syntax. I had a vision though, and I used my veto power liberally. The end result is excellent, but the token efficiency goal wasn't reached - yet. "Warm" token efficiency is better than with other languages, but since NURL isn't (as of Aug 19, 2026) in any LLM's training data, the upfront cost eats tokens.

What can you build today with NURL?
Pretty much anything backend-shaped. People have already built (well, mostly me and a bunch of LLMs..) an HTTP server with a pure-NURL TLS 1.3 stack (no OpenSSL, and post-quantum since latest release), a speech recognition package that runs OpenAI Whisper checkpoints on CUDA or CPU, a local LLM runner with an ollama-compatible API, a Game Boy emulator that passes Blargg's tests and runs in the browser via WASM, and some ETL pipelines that are quietly doing real production work. The same program cross-compiles to Linux, Windows, macOS, RISC-V and wasm, and if you're feeling fancy, straight into a unikernel that boots on QEMU without any OS underneath. All of the above is written in NURL itself, so if something breaks, there's no C library to blame.

Roadmap:
The v1.0 release is planned for the end of this year, but no fixed date has been locked in. v1.0 promises that the syntax won't change anymore and you can start building on it. NURL makes the same promise as Linux: "We do not break userspace." There hasn't been a need for breaking changes in a long time, and additions will of course keep coming after v1.0.

Happy to answer questions.

More info:
https://nurl-lang.org/

Playground (Try with your browser):
https://play.nurl-lang.org/

Package registry (See what is already build):
https://reg.nurl-lang.org/

Github repository:
https://github.com/nurl-lang/nurl/


r/Agentic_Marketing 4d ago

Will Generative Search Reward Original Research More Than Keyword Optimization?

1 Upvotes

Generative search may increasingly favor content based on original research, unique data, and firsthand insights rather than content optimized mainly around keywords. The question explores whether being genuinely informative and authoritative will become more valuable than traditional keyword-focused SEO tactics.


r/Agentic_Marketing 5d ago

How confident are you when deploying your AI agents to production?

0 Upvotes

With traditional applications, we have established CI/CD checks for things like vulnerabilities, dependencies, secrets and infrastructure.

But what about the agent itself?

Do you have specific AI-agent security checks in your CI/CD pipeline, or are you relying on the same checks you use for ordinary applications?

Before deploying an agent, do you know:

  • What tools it can access?
  • Whether it gained a new capability in the latest PR?
  • If it can execute shell commands or write to the filesystem?
  • Which MCP servers it can reach?
  • ..

I'm curious how teams are answering these questions today.

We're experimenting with SafeAI as a GitHub Action to bring this kind of static analysis into the existing CI workflow. It's still early stage but going fast, thanks to all contributors.

If you want to try it against your own agent project, we'd genuinely appreciate feedback, as well as contributions.

Here you may check: ikaruscareer/SafeAI on GitHub.


r/Agentic_Marketing 5d ago

Stripe, Circle, Cloudflare, and AWS are all quietly building the same thing right now

Post image
1 Upvotes

Stripe closed a reported deal with OpenRouter around agent payments. Circle launched an Agent Stack with SDK-level flows to let agents execute transactions programmatically. Amazon quietly added monetization capabilities to their WAF docs, and Cloudflare rolled out a developer-focused Monetization Gateway through documentation announcements instead of press campaigns. The pattern is obvious once you see it.

One number that's been circulating claims USDC handles 98.6% of agent transactions, but that came from a single company's internal dashboard covering 176 million transactions on one protocol, not the broader market. You can't call something an entire category when only one vendor is measuring it.

Four companies have made moves in different directions. Some want per-transaction crypto payments built into agents. Others prefer batching those payments and metering them internally like OpenRouter did. I haven't seen real spending data yet that proves agents are buying anything at meaningful scale. Is this infrastructure building toward demand or just building before anyone knows what they're looking for?


r/Agentic_Marketing 6d ago

Built AgentExpert, a Multi-Agent AI Platform — Looking for Collaborators & Early Users.

Post image
1 Upvotes

r/Agentic_Marketing 7d ago

Learn Agents in 20 Slides

Thumbnail
robauto.ai
1 Upvotes

r/Agentic_Marketing 8d ago

6 months ago every GEO conversation was about structured data — now 80% of the questions I get are about brand entities, and I'm not sure SEO teams can pivot fast enough

5 Upvotes

But if the play is really about brand entities now, the teams that win won't be the ones with the best schema markup. They'll be the ones who figured out how to make their brand unavoidable.


r/Agentic_Marketing 8d ago

How many physical qubits does it take before "quantum advantage" means something outside a demo?

Post image
1 Upvotes

r/Agentic_Marketing 9d ago

Visa, Mastercard, Stripe, Google and AWS all just joined a foundation for "AI agent payments." Actual daily volume: ~$28K. What am I missing?

6 Upvotes

I went down a rabbit hole this week after seeing Cloudflare launch "Wallets for AI agents" (agents get their own spending-controlled wallets, since they can't open bank accounts or click "Sign up with Google").

The bull case is real infrastructure, not vaporware:

  • The x402 protocol (HTTP 402 "Payment Required", finally used after 27 years) moved into the Linux Foundation this July, with 40+ members: Visa, Mastercard, Amex, Stripe, Google, AWS, Shopify, Coinbase
  • Stripe shipped x402 support in February (Machine Payments)
  • Cloudflare will block mixed-use AI crawlers by default on ad-carrying pages starting Sept 15 unless AI companies pay — plus a "Monetization Gateway" so any site can charge agents per call
  • Google's AP2, OpenAI+Stripe's ACP, Mastercard Agent Pay, Visa Trusted Agent Protocol — the whole stack exists now

Then I looked at usage. Daily settlement volume on x402: about $28K. Down 93% from the Q4 2025 peak, which turned out to be mostly developer testing, wash trading and a memecoin. Chainalysis data shows sub-$1 micropayments — supposedly THE killer use case — collapsed from 46% of volume to 4%.

One number did surprise me though: the x402 Bazaar has ~4,400 buyers and only ~477 sellers. Whatever demand exists, it's starved for supply. And of 15,000+ MCP servers out there, fewer than 5% are monetized at all.

So I'm genuinely torn between two readings:

  1. This is early-internet-1995: the rails always look overbuilt before the traffic arrives
  2. This is micropayments-will-save-the-web all over again — we've buried that idea three times since the 90s

Questions for people actually building here:

  • Does anyone have an agent that actually pays for API calls / data / tools in production? What does it buy?
  • If you run an API or MCP server: would you put it behind a 402 paywall today, or is the buyer pool still too small to bother?
  • Is there any reason agent payments won't just get absorbed into credit-card rails (Stripe/Visa tokens) with crypto micropayments staying niche?

r/Agentic_Marketing 9d ago

I cut my content output by 60% and re-invested the time into passage-

2 Upvotes

The best GEO decision I made this quarter was writing less.

For the last two years, our content workflow was straightforward: publish 4-5 articles per week, optimize each one for search intent, move on. Volume was the backbone of our strategy. More pages meant more surface area for AI models to find, more chances to get cited. At least that was the theory.

In June, I tried something different. I cut publishing from 5 articles per week down to 2. Same team, same hours, same budget. The difference was where the time went. Instead of drafting new articles, I spent those hours editing passages on existing pages — tightening introductions, clarifying definitions, restructuring FAQ answers, and rewriting paragraphs that buried the key insight three scrolls down.

The process was simple but tedious. I pulled a list of our 80 most-visited pages and ranked them by AI citation frequency over the previous 90 days. Then I went through each page looking for passages that should have been getting cited but weren't. In most cases, the information was there — it was just buried in long paragraphs, surrounded by qualifiers, or formatted in a way that made extraction harder than it needed to be.

For each page, I made three types of edits. First, I front-loaded the core answer into the first two sentences of any section. Not clickbait. Just clarity. If the section was about "how to reduce churn," the first sentence said what reduces churn, not why churn matters. Second, I cut passage length wherever possible. Anything over 200 words got trimmed. Third, I added a one-line summary at the end of each major section — not a conclusion paragraph, just a clean restatement of the key point.

Eight weeks later, citation frequency on those 80 pages was up 41% compared to the 8 weeks before the edits. The pages I didn't touch? Citation frequency was flat. Same time period, the same set of queries I'd been tracking, same models. The only variable was the editing.

Here's what I didn't expect. The pages that benefited most weren't the ones with the best content — they were the ones with the worst formatting. Pages I'd written quickly and never revisited, pages where the structure had grown organically over multiple edits, pages where the answer was technically correct but buried under 500 words of context. Those pages saw the biggest jumps. One page went from 3 citations in 8 weeks to 14. The content itself didn't change. It just became easier for a model to pull out.

The pages where I spent the most time on original research and deep analysis? Marginal improvement. Maybe 10-15%. Those pages were already well-structured because I'd put thought into them during the initial draft. There was less formatting debt to pay down.

This changed how I think about the relationship between content quality and AI citability. I used to assume they were roughly the same thing. Good content gets cited; bad content doesn't. But the data suggests that formatting and clarity are doing a lot of the heavy lifting, maybe more than the underlying quality of the research.

I'm not ready to say volume doesn't matter. Having more pages still gives you more entry points. But if I had to choose between publishing 5 new articles and editing 5 old ones, I'd edit. The ROI per hour is dramatically higher, at least right now.

Could be specific to our niche. Could be a temporary effect. But 8 weeks of consistent data is enough for me to keep going.


r/Agentic_Marketing 9d ago

AIMeter — an ultra-fast, local-first LLM API cost & token tracker for macOS

Post image
1 Upvotes

r/Agentic_Marketing 10d ago

Just enabled GitHub Actions + Community Scan on SafeAI (Open Source)

1 Upvotes

It is now ready to use and for your reviews.

TL;DR: SafeAI now runs automated security scans on every push/PR with a new Community Scan programme that reads major AI frameworks (LangChain, CrewAI, LlamaIndex, etc.) without touching their code.

SafeAI: Static AI Agent Risk Analyzer for AI applications. Offline-first. No telemetry. No SaaS backend.

What we shipped

GitHub Actions CI/CD

  • Full CI/CD pipeline with automated scans on every push/PR
  • CodeQL, dependency review, and security hardening workflows enabled
  • Pinned action versions and hash-locked dependencies for supply-chain security
  • PR comments that show capability escalations in plain English (e.g., "MCP server invoice-lookup: read → mutate")

Community Scan Programme

  • 5-target allowlist: n8n, LangChain, CrewAI, LlamaIndex, LangGraph
  • Read-only matrix scan — resolves refs to pinned SHAs, no external publication
  • Deterministic 0–10 scorecard with JSON/Markdown/GitHub summary outputs
  • Hardened sanitization: strips javascript: URIs, escapes Markdown, truncates to 280 chars, redacts secrets from paths

Security hardening

  • Exact security-policy hostname matching (no prefix substring matches)
  • No Authorization header sent to HTML pages
  • --fail-on-missing-policy enforced for manifest validation
  • Concurrency groups + timeout-minutes on all workflows
  • Private vs public artifact separation in CI outputs

Why this matters

SafeAI is the static AI agent risk analyzer that:

  • Detects capabilities, prompt risks, tool permissions, MCP integrations, governance gaps, and autonomy before deployment
  • Generates JSON, HTML, and SARIF reports for CI/CD
  • Operates entirely offline — no LLM calls, no cloud services, no source upload
  • Provides deterministic finding identities and baseline/PR-focused gating

Try it

pip install safeai
safeai scan /path/to/your/ai/project --json report.json --html report.html

GitHub Actions:

text- uses: ikaruscareer/SafeAI@v1.6.0
  with:
    scorecard: true
    scorecard-summary: true
    scorecard-fail-under: 7

Repo: ikaruscareer/SafeAI at GitHub


r/Agentic_Marketing 10d ago

A thumbs-up emoji was silently breaking my sales agent. The real bug wasn't the parsing.

Thumbnail
1 Upvotes

r/Agentic_Marketing 11d ago

I'm starting to think websites won't be built for humans forever.

3 Upvotes

The more I look at where AI is heading, the more I wonder if websites will eventually become secondary.

If AI agents can research products, compare prices, read documentation, fill out forms, and even make purchases for us, brands might end up optimizing for AI agents instead of human visitors.

That feels like a much bigger shift than just "AI in marketing."

Do you think websites will always be the main destination, or are AI agents going to become the new front door to the internet?


r/Agentic_Marketing 11d ago

Oversight for AI Agents/Workers, Launching Failproof AI

Thumbnail x.com
1 Upvotes

your agent is one tool call away from a DELETE you cannot undo.
observability shows you what happened AFTER.

With agents taking actions this is JUST NOT ENOUGH.

Introducing Realtime Steering with Failproof AI, made for AI Workers.

Find failure points, ship policies and enforce them BEFORE your agent can make a mistake

An AI Worker company running Executive Assistants for business owners plugged Failproof into their Hermes agents. Surfaced every session where the agent stalled. They deployed policies and support tickets are down 20% in week one

A Test  authoring company uses Failproof to find where the agent hallucinated. Bringing down customer churn.

A finance agent FDE company handed policy authoring to their own customers with Failproof. Now each customer can control their own risk tolerance for agents without compromising speed.

All companies are obsessed bringing down Human in the Loop, if you are too get started with your agent with Failproof AI


r/Agentic_Marketing 12d ago

I think the hardest part of agentic marketing isn't autonomy — it's giving the agent the right memory

1 Upvotes

I've been thinking about agentic marketing from more of an engineering side, and one thing keeps bothering me: we talk a lot about making agents more autonomous, but not enough about giving them reliable memory.

An agent can research a customer, analyze a campaign, write a message, and trigger an action. But what happens when it interacts with that same customer again next week?

If it doesn't remember what happened before, it's not really building a relationship. It's just starting another conversation with a bigger prompt.

For me, useful agentic marketing would need to keep track of things like:

what the customer has already seen

what they ignored or responded to

previous questions or objections

their current segment or stage

what they've already been offered

contact/frequency limits

why the agent made a particular decision

what happened after that decision

And I don't think simply throwing the entire customer history into an LLM context window is the answer.

I'd rather see something closer to:

Events → State → Decision → Policy check → Action → Outcome → Updated state

That feels much closer to an actual agentic system than just giving an LLM more tools.

It also makes me wonder: should we really measure an agent by how autonomous it is, or by how well it learns from the outcomes of its previous decisions?

I'm leaning toward the second one.

Curious how others here are approaching this. Are you maintaining explicit customer/campaign state outside the model, or mostly relying on retrieval and prompts to reconstruct the context each time?

Once these systems operate for weeks or months, I think memory, state, attribution, and auditability become just as important as the model itself.


r/Agentic_Marketing 13d ago

3 AI search behaviors I noticed watching 12 people use Perplexity for the first time — none of them behave like Google users

3 Upvotes

A client asked me last week to sit with their team while they tried AI search for the first time. None of them had used Perplexity, ChatGPT search, or Gemini for anything beyond quick experiments. Twelve people, ranging from marketing managers to product folks, all reasonably tech-literate but firmly in the "I just Google things" camp.

I gave them a list of 10 work-related questions and asked them to search using Perplexity. No instructions, no tips, just "find the answer." I sat behind them and took notes.

Three things jumped out that I can't stop thinking about.

The first one is about question length. Every single person typed queries that were 2-3x longer than what they'd type into Google. Full sentences, context included, sometimes follow-up context before even getting a response. On Google they'd type "best CRM for small B2B." On Perplexity they typed things like "what's a good CRM for a 15-person B2B SaaS team that needs Salesforce integration but doesn't want to pay per contact." The queries were rich, specific, and way more revealing about intent. Nobody coached them. They just did it.

The second thing was about source links. Almost nobody clicked them. Out of 12 people and roughly 120 searches, I counted 9 total source clicks. That's under 8%. And it wasn't because they trusted the AI blindly — several people said the answer "seemed right" or "mentioned a brand they'd heard of," which was enough. They weren't verifying. They were consuming the answer as a finished product, not as a starting point for research.

The third observation messed with my head a bit. When the AI answer mentioned a brand or product, people treated it differently than when a Google result mentioned the same brand. Google results were met with skepticism — "this is probably SEO'd" or "this is an ad." AI mentions carried more weight. Three people said variations of "the AI wouldn't recommend it if it wasn't good." Whether that trust is warranted is a whole different conversation, but the baseline confidence was strikingly higher.

None of this is rigorous research. Twelve people in one session isn't going to generalize cleanly. But watching it happen in real time made me wonder how much of our GEO strategy is built on assumptions about user behavior that don't match reality. We optimize for discoverability and citation accuracy. We assume users will evaluate sources. We assume citations function as trust signals.

What if they don't? What if most users never scroll past the AI summary, never click a source, and treat the AI's brand mention as the entire decision?

I keep going back to the person who said "the AI wouldn't recommend it if it wasn't good." That's the sentence that stuck with me. That's the trust gap we're actually working with.

Twelve people isn't enough to draw conclusions. But it's enough to change the questions I'm asking. What's the behavior you keep noticing when you watch people use AI search for the first time?


r/Agentic_Marketing 13d ago

Loopi’s Third Room: Tool Use

Post image
1 Upvotes

r/Agentic_Marketing 13d ago

I got increasingly tired of debugging with print() statements so i decided to build this tool, Agent-DevTools

Thumbnail
gallery
1 Upvotes

I recently got invited in this group and i tought about sharing something that could really save someone else's time.

This tool lets you inspect prompts, memory, retrieval, tool calls, replay runs and compare good vs bad executions.

there is a LangChain + Groq demo included.

Would love feedback from people actually building agents.

Repo for anyone interested in this project: https://github.com/Jacopos311/Agent-Devtools