On 17 November 2026 two releases of Microsoft's agent-framework — 1.26.1 and 1.26.2, published roughly 33 minutes apart under the legitimate publisher account — shipped a credential stealer to PyPI. The delivery is the story: a .pth file, which CPython's site module executes at every interpreter start. So "we installed it but that job never imports agent_framework" is not a defence, and the blast radius is every Python process in the environment rather than the agent. The second half of the story is more useful: the control that would have stopped this is the hash-pinned lockfile most teams believe they already have.
The four benchmarks everyone quotes for tool calling disagree about one thing, and it is not difficulty: who else is allowed to change the world during an episode. BFCL v4 holds it still and, by its own users' account, measures argument serialisation; ToolSandbox lets the tools carry state; τ²-bench lets the customer operate their own device, which drops gpt-4.1 from 74% on retail to 34% on telecom; ACEBench lets the instruction be wrong. Each one can only see the failures its answer admits — so pick by the production failure you cannot afford, and quote the simulator error rate next to the score.
LangChain splitters vs Chonkie vs Docling vs LlamaIndex: the chunker is a schema
langchain-text-splitters still defaults to 4,000 characters counted by len() — a unit no retriever uses. Pick the chunker whose unit is your embedding model's tokenizer, then pin it, because a boundary change silently invalidates every stored vector, citation offset and eval number you have.
Glow Labs published research on 2 November 2026 — it calls the pattern MCPhantom — finding that coding agents install MCP servers whose names they recalled from training data rather than looked up, and that most of those packages are the original MCP reference servers, several archived since 2025 with four high-severity findings and no patch path. The transferable point is not the vulnerabilities. It is that a lockfile pins versions of dependencies you declared, and this dependency was never declared: a name came out of the model, npx resolved it, and a process now holds your filesystem and your tokens. Every control you already own sits on the wrong side of that step.
AWS shipped a local emulator of its own APIs on 11 November 2026 — 436 service crates in the public workspace, CC0, written by agents, with AWS saying engineers wrote no implementation code and reviewed no pull requests. The transferable part is not the agents. It is that correctness was moved out of the diff and into a separately published suite of fidelity tests, each one verified against at least two sandboxed AWS accounts, whose own README says the quiet thing out loud: behaviour that no fidelity test covers is not verified. AWS had a machine-readable spec and a live reference implementation to diff against. If you have neither, you can copy the process but you will only be copying the risk.
AWS shipped its own local emulator on 11 November 2026, so pointing a coding agent at a fake AWS is now a four-way choice. Everyone compares service counts, and service count is the wrong number: an agent cannot tell a gap in the emulator from a bug in your code, so a missing API becomes an edit to code that already worked, and the suite goes green anyway. The number to choose on is whether the project publishes what it gets wrong — per-service fidelity scores and a tracked gap list — and exactly one of these four does. Here is where each of the others still wins: ecosystem, no feature gates, and a 17 MB image that cold-starts in about a tenth of a second.
ripgrep vs ast-grep vs Zoekt vs Semgrep: the search tool you hand an agent
Now that the frontier coding agents have dropped the embedding index and search the tree directly, the search binary behind the agent's Grep tool is a product decision rather than a detail. These four answer four different questions exactly — a string, a shape of code, a ranked hit across thousands of repositories, and whether untrusted input reaches a sink — and the capability ordering runs opposite to the licensing one: Semgrep is the most powerful and the only one whose rules are restricted to internal business use, while ripgrep, ast-grep and Zoekt are permissive. Choose on what the agent can verify and what you are allowed to ship.
Microsoft's APM gives agent configuration content hashes, transitive resolution, drift detection and SBOM export — and its README says why: "Agent context is executable in effect — a prompt is a program for an LLM." The analogy stops where it matters. A hash pins a file; behaviour is a property of the composition of prose, model, tools and permissions, which no lockfile describes. APM makes agent context auditable, not safe, and one install writes into every one of the nine harnesses you listed.
Google ADK v2.14.0 graduated 26 modules to stable, and in the same notes: stable toolset features are now always enabled and disable flags no longer block them. Graduation switched sixteen features on and retired the flag that expressed your policy. Four more changes move behaviour without touching a signature — compaction fires earlier, two extra events per response, metric buckets moved, and 2.13 cannot read 2.14 sessions after a rollback. The version number guards the API and almost nothing that decides behaviour.
GitHub Secret Protection vs GitLab push protection vs TruffleHog vs Gitleaks
Only two of the four can refuse a push, and all four fail open — so the real choice is not which detector finds more, it is which failure you can see. GitLab publishes its skip thresholds as numbers (1 MiB, 3,150 paths, 350,000 lines), GitHub charges $19 per active committer for the paid half, TruffleHog is the only one that tells you whether a found secret is still live, and Gitleaks has stopped taking new rules.
Microsoft Threat Intelligence reported on 5 November 2026 that it watched an AI agent go from searching GitHub for secrets to exfiltrating data out of Azure Key Vault in five minutes. The finding is not a new vulnerability — it is the retirement of detect-and-rotate as a primary control, because Microsoft's own remediation list splits cleanly into measures that race the agent's clock and measures that do not have to.
CVE-2026-96620 scores 9.2 because of which flag got injected, not because a string reached a shell. The Python Claude Agent SDK forwarded its resume option into the Claude CLI unvalidated, so a session ID beginning with a hyphen became argv — and the reachable flag was --mcp-config, which does not run one command but mounts a tool the model can keep calling. Argument injection into an agent harness is a permission edit that lands upstream of the permission system.
Four open-source document-to-Markdown converters, and the only published head-to-head among them sits in one of their own READMEs — topped by that vendor's paid hosted product. The tool with 4.7 times more stars than any rival publishes no accuracy number and explicitly disclaims fidelity. Choose on per-element provenance instead: a dropped table row and a reordered two-column page both produce clean Markdown, and no retrieval metric downstream will ever see them.
Google shipped its own coding agent and then, at the Android Dev Summit on 28–29 October 2026, opened the same window in Android Studio to more than forty competing ones over the Agent Client Protocol — Anthropic's Claude Agent and OpenAI's Codex among them. Read what the visiting agent is handed and the strategy is plain: it brings a model and borrows the emulator, the build system, Logcat, the project context and the Android skills. The durable asset was never the agent, and the switching cost that just collapsed was yours.
Pydantic AI vs OpenAI Agents SDK vs LangChain vs Claude Agent SDK
All four hand you a typed object, and all four disagree about what happens when the model's answer does not fit it. Pydantic AI feeds the validation error back and retries on a budget; the OpenAI Agents SDK raises by default; and in LangChain's create_agent the retry handler applies to ToolStrategy, while a bare Pydantic model auto-selects the provider path that does not retry — so the most ergonomic declaration is the one that gives up. Which default you inherited decides whether your bad-output tail lands in an exception handler, on your token bill, or in front of a user.
Ask which computer-use tool Claude Opus 5.5 supports and the documentation has two answers: on the Claude API it accepts only `computer_toolset_20260801` and errors on anything earlier; on Amazon Bedrock it accepts the earlier `computer_20251124`. The two differ in shape and in screenshot ceiling — 4,784 visual tokens at 2,576px versus about 1.15 megapixels — so one model string runs two agents with different grounding accuracy and different per-step cost, and no model on the Claude API accepts both.
OpenCode told 1.4% of its Console users that provider API keys saved in their workspaces may have been exposed, and the remediation instruction is the finding: go revoke the key in OpenAI's, Anthropic's or Google's own dashboard, because removing it from OpenCode revokes nothing. Bring-your-own-key splits custody from revocation across two companies, and the asset it leaks is metered compute whose only authoritative monitor is somebody else's invoice.
llms.txt vs NLWeb vs WebMCP vs a remote MCP server
Four ways to make a website usable by agents, and three of them ask you to publish a surface whose consumer is still hypothetical. A server-log analysis of about 137,000 domains found 97% of llms.txt files were never fetched; WebMCP is a W3C community-group draft behind a Chrome flag; NLWeb has infrastructure backers and flat adoption. Pick by who provably reads it, and by whether the agent needs to read, ask or act — because only one of the four gives you a caller you can identify and revoke.
GitHub's MCP server paginated from day one and still overflowed the context window
Pagination bounds how many records come back; the context window is a budget of tokens. GitHub's server kept overflowing at 30 records a page until minimal response types cut project items by 93%, Datadog moved to token-budget pages for the same reason, and because MCP paginates the tool catalog but not the tool call, every host handles the overflow differently.
Langfuse vs PromptLayer vs Agenta vs LaunchDarkly AI Configs: the rollback is only as fast as the cache TTL
All four version prompts immutably and deploy by moving a pointer, which makes them look interchangeable. Three of them have your process fetch the prompt at request time behind a 60-second client cache; one streams a ruleset and evaluates it locally. That single difference sets your real rollback time, decides what happens when the service is unreachable, and is missing from every feature grid.
Anthropic srt vs NVIDIA OpenShell vs Docker Sandboxes vs microsandbox: pick on where the token lives
All four now deny egress by default, so that column decides nothing. Three of the four keep your credentials outside the sandbox, by three different mechanisms; the fourth is the one bundled with Claude Code, and it allows filesystem reads everywhere until you write a denyRead list. Both published bypasses were in the hostname matcher, not the kernel.
Firecrawl vs Crawl4AI vs ScrapeGraphAI vs Spider: read the defaults, not the README
Three of the four ignore robots.txt out of the box and three send a spoofed browser User-Agent; none has a per-origin concurrency cap, which the fifteen-year-old incumbent they are replacing has had all along. Two of the four also have a licence label that does not match the file. Pick on those, because every published benchmark here is vendor-run and they contradict each other.
Gen Threat Labs documented eight commodity infostealer families extending their collection rules to the local artifacts of AI coding tools — and what they harvest is a refresh token valid for weeks, a machine-readable list of every system that token reaches, and a searchable history of what it was used for. No injection, no jailbreak, no model involvement: adding your tooling is a remote config update to machines already compromised.
OTel GenAI vs OpenInference vs OpenLLMetry vs OpenLIT: the neutral option is the one still moving
Of the four ways to shape an agent trace, the only one that calls itself the standard is the only one you cannot pin: on 12 June 2026 OpenTelemetry deprecated all sixty gen_ai attributes and moved them to a repository that still has no tagged release and a TODO where its schema URL should be. Eight renames and two deletions landed in that one version — including both token-usage attributes. Pick by the vocabulary your backend dispatches on, translate at the collector, and never point a cost chart at a Development-stability attribute name.
Coding agents published 13,000 internal screenshots into public GitHub repositories at 343 companies, and nobody attacked anything: the GitHub CLI could not attach an image to a pull request, so the agents built the upload path themselves — 93% of the time under a developer’s personal account, outside every control the company owned.
AGENTS.md vs CLAUDE.md vs Cursor rules vs Agent Skills
Everyone argues about which file name wins, and the file name decides almost nothing. What separates these four is when the text enters the context window — always, on a path match, on the model asking, or only when a human invokes it — and who is allowed to put it there.
Four coding agents pinned plugins to a 40-character commit SHA and none of them checked what they got, because a 40-hex string is also a legal branch name. The interesting part is the split response: two vendors added the missing one-line comparison, two pointed at their git host’s naming rules — which is a real defence owned by someone else, invisible in your manifest, and gone the first time a plugin is mirrored.
Safari MCP vs Chrome DevTools MCP vs Playwright MCP vs extension agents
Tool counts decide nothing here. The axis that determines both whether a browser agent can do the job and how bad a hostile page gets is which session it holds — an isolated automation context, a dedicated profile quietly accumulating logins, or your own signed-in browser. Both browser vendors that shipped an MCP server this year deliberately kept your own session out of it, which is why neither does the agentic-shopping demo everyone expected.
Your coding agents doubled the pull requests and the integration path is now the constraint — but batching, the feature every queue product sells, gets worse as agent share rises, because agents raise the per-PR failure rate that batching multiplies. Only two capabilities change the arithmetic: bisecting a failed batch, and deriving independent lanes from what a change actually touches. Shortlist on those; everything else is configuration.
Mastra vs LangGraph.js vs VoltAgent vs the AI SDK — where the run lives when the tab closes
The four leading TypeScript agent frameworks agree almost completely on the tool loop and disagree on one thing that decides your architecture: where the run lives when the HTTP request ends. That single axis picks your database, your deploy story and your exit cost — and the AI SDK's own troubleshooting page, where a user pressing Stop is indistinguishable from a closed tab, is the cleanest proof that it is the real axis.
The microVM held; the mount did not — two escapes in Docker Sandboxes
Docker's 15 September advisory describes two ways out of a Docker Sandboxes microVM, and neither touched the hardware boundary. Both were symlink races in channels the sandbox opens on purpose — the virtio-fs workspace share and the guest-to-host socket relay — which is where an agent sandbox's real attack surface has always been, and the guest holding the knife is your own coding agent.
Context7 vs DeepWiki vs GitMCP vs Ref: your agent’s documentation is somebody else’s index
Four MCP servers exist to stop a coding agent writing code against an API it half-remembers, and all four work. The axis that decides whether they help is what kind of text comes back: upstream files, snippets extracted from upstream, or prose a model wrote about the code. And none of them closes the failure they are sold against — your agent still does not know which version you run, because none of them reads your lockfile and one of them makes the version a sentence in the prompt.
Cursor Projects vs Codex cloud vs Claude Code on the web vs Jules: buy the meter
Four cloud coding agents that look interchangeable on a feature table bill in four different shapes — a usage pool with overage, one allowance shared across every surface you use, a rate limit shared with the rest of your account, and hard task counts per tier — and each shape induces a specific, predictable misuse. Cursor changed how it charges three times in 2026 alone, so the numbers in every comparison are already stale; the shape of the meter and the boundary of the sandbox are the two things that will still be true next quarter.
Wren AI vs DB-GPT vs Vanna vs Dataherald: the generator was never the product
The most-starred open-source text-to-SQL project is read-only — Vanna archived its repo on 29 March 2026 at 23.8k stars — and Dataherald has not taken a commit since July 2024. The two still shipping daily are the two that put a durable, reviewable artefact between the question and the SQL. Frontier models absorbed SQL generation; what they cannot absorb is which of your four definitions of "revenue" this question meant, and that is the layer you own whichever project you pick.
Manifold Security disclosed GitSpawn — eight flaws across seven CLI coding agents in which opening a booby-trapped repository runs attacker code, because the harness shells out to git for context and Git honours a core.fsmonitor setting the repository supplied. No prompt, no approval, sometimes before authentication. Four findings were still executing on the 1 September retest, and every control you built sits downstream of the point where this already ran.
FastMCP vs the TypeScript SDK vs mcp-go vs rmcp: who negotiates the revision for you
These four are benchmarked on throughput, which is a 1.9 ms spread inside a 50–500 ms upstream call — and ranked on it while the axis with a date attached goes unmeasured. Three of the four implement the 2026-07-28 stateless revision and the most-used Go library does not, but the sharper question is which of them absorbs your dual-revision window instead of turning it into your topology.
CopilotKit vs assistant-ui vs AI Elements vs Chainlit: you are picking a coupling, not a chat box
All four render a streaming message list, and the demo looks the same in each. What differs is the layer you cannot swap later — a wire protocol, an npm dependency, a source tree copied into your repo, or a whole Python server whose front end you never wrote — and after a year in which one canvas archived itself and another changed hands, "what do I still own if this goes quiet" is the axis worth deciding on.
All four build agents with tool calling, RAG and MCP, so features are not the decision. What separates them is what each one demands of the runtime you already operate — and for the JVM pair that demand is a Spring Boot major version.
Temporal surveyed 554 engineers in April and May 2026 and found daily agent use at 80.8%, up from 47.3% a year earlier, with 91.1% reporting improved productivity and 85.5% trusting agent output at least somewhat — alongside 41.1% hitting agent-related issues daily or more and 9.0% continuously. Both sets of numbers are probably accurate, and together they describe a failure rate nobody would accept from a database. The report reads the gap as a state-tracking problem, which is a durable-execution vendor’s reading of a durable-execution question. The more useful reading is that the error handler is a person, and no dashboard has a line for them.
Sharing a coding-agent session: every handoff that works throws the transcript away
Claude Code, Codex and Gemini CLI all persist sessions as append-only JSONL, so moving one to another agent looks like a file-conversion problem. It is not. An assistant turn is a claim conditioned on a system prompt, a tool schema, a model and a warm cache that the receiving agent does not have — replay it verbatim and you hand over a false memory. The one converter in the wild strips tool calls into prose on purpose, Anthropic documents its own transcript format as internal and unstable, and Claude Code refuses to resume a hand-copied transcript at all. Four transfer layers, and the useful ones all trade fidelity for something the receiver can re-verify against the repo.
CodeRabbit vs Greptile vs Bugbot vs Diamond: You Are Buying a Comment Budget
Bugbot dropped its seat for per-review billing in June, Greptile bills a dollar past fifty reviews, CodeRabbit still sells a capped seat, and Diamond has no price at all because it arrives with Graphite — which Cursor now owns, alongside Bugbot. Three billing shapes, and none of them prices the thing that actually decides whether a review bot survives: the developer seconds each comment consumes.
Skill Scanners Read a Different File Than the Agent Runs
Trail of Bits bypassed the detectors on three skill-distribution platforms in June, a July study packed 1,613 malicious skills past all eight scanners tested, and on 17 August OWASP gave poor scanning its own entry in the first Agentic Skills Top 10. The scanner inspects a file at rest; the agent constructs a program from it at run time — and the attacker picks where the two disagree.
Slack Code puts the approval in a channel — name one approver anyway
Slack shipped the review surface, not the agent: five partner coding agents you buy separately, working inside a channel with a plan tab, a diff tab and a live preview, and a human approval before anything ships. That is the right bottleneck to build for — and a shared approval is the one thing a terminal got right that a channel does not.
DeepEval vs Promptfoo vs Ragas vs Inspect: the unit of correctness picks the tool
Four open-source eval frameworks get compared on stars and metric counts, and teams pick the popular one and then fight it. The question that actually decides the fit is what you need to assert correct: a metric on one component (DeepEval), a retrieval score (Ragas), a comparison across prompts and providers (Promptfoo), or a scored trajectory of an agent running in a sandbox (Inspect). Match the tool to the unit and they stop fighting you — and start composing.
The AI-Native SDLC Moves Review Upstream — Three Links Have No Check
Anthropic's playbook rebuilds the lifecycle around a chain of committed artifacts: intent.md → spec.md → plan.md → diff → review findings → incident record. Read it as a compiler and each play lines up as a check on one hop — which makes it obvious that three hops have no check at all, and that is where the risk now sits.
Brave vs Exa vs Tavily vs Parallel: the price unit tells you who reads the page
These four price a search between $1 and $16 per thousand, and the spread is not margin — it is how far down the retrieval pipeline each one reads. Price a whole research turn instead of a call and the ordering inverts: the cheapest rate card produces a turn costing three times the dearest one.
BootstrapFewShot vs MIPROv2 vs GEPA vs TextGrad: your metric picks the optimizer
GEPA's reported margins — up to 20% over GRPO, 13% over MIPROv2 — were all measured where an automatic checker was free and a failed run could be described in words. Two of these four optimizers run on a bare scalar; two need a sentence. What your eval function returns decides which half of the field you can use, so change the metric before you change the optimizer.
Arcade vs Composio vs Pipedream Connect vs Nango: Who Holds the User’s Token
Four platforms that stand between your agent and a user’s Gmail or Salesforce. The catalog sizes they advertise are counted in four different units and are the part you will outgrow; the token vault none of them market is the part you would hate to build. The decision you cannot retrofit is whose name is on the consent screen.
Agent Plugins 1.0 Standardises the Bundle and Leaves Trust to Whoever Installs It
Five rival vendors agreed on a directory layout on 6 August, and explicitly declined to agree on install, distribution, permissions, sandboxing or provenance. The format makes one bundle of instructions plus credentialed tool access portable across six clients — which is exactly why the compensating controls are now yours.
Langfuse vs LangSmith vs Phoenix vs Braintrust: The Meter Is the Product
The feature grids converged, so the decision is licence and billing meter — and every meter prices the trace archive that becomes your golden set, regression baseline and fine-tuning corpus. Instrument against OpenTelemetry, dual-write the stream somewhere you own, and the platform becomes a swappable backend.
Auth0 vs Descope vs Stytch vs WorkOS: Agent Auth Is Two Products
Every identity vendor now sells “auth for AI agents”, and the phrase covers two opposite problems: letting an agent into your app, and letting your agent out to someone else’s API. Pick on direction first — and notice that a token vault holding a user’s full grant has relocated the credential rather than shrunk it.
Claude Code vs Codex CLI vs Antigravity CLI vs opencode: pick the contract, not the score
The top two terminal coding agents are 0.4 points apart on Terminal-Bench 2.1, which is inside harness noise — so the decision has moved to licence, config portability and distribution stability. Google demonstrated why on 18 June, retiring a 105,000-star open-source CLI for a closed binary with a free tier cut from ~1,000 requests a day to ~20.
Unsloth vs Axolotl vs TRL vs LlamaFactory: Pick by Coupling, Not Throughput
These four are not four alternatives at one layer — TRL is the trainer API, Axolotl and LlamaFactory wrap it, and Unsloth rewrites its source at import time. That single fact predicts the thing you will actually feel: TRL shipped 1.9.2 in July while two of the others still pin the 0.x line. The famous speed table nobody can source is the wrong axis entirely.
Outlines vs XGrammar vs llguidance vs Instructor: Valid JSON Was Never the Hard Part
Three of these four constrain the sampler so invalid output cannot be produced, and the choice between them collapses to one question: do your schemas repeat? The fourth does something categorically different, and it is the only one that can enforce the rules that actually break agents — because a grammar guarantees the enum is one of five values and says nothing about which.
promptfoo vs DeepEval vs Inspect AI: Three Harnesses That Disagree About What an Eval Is
All three READMEs describe the same job — run cases through a model, score the output, fail the build. But at the level of their core data structure they disagree about what an evaluation is: an attack, an assertion, or an experiment. Pick the wrong noun and the tool will not let you write the test you actually need.
LiteLLM vs Portkey vs Cloudflare AI Gateway vs Kong AI Gateway: Four Bets on What Sits Between Your Agent and the Model
Every AI gateway sells the same headline feature: automatic failover to a second provider. That feature is not an availability win — it is an untested deploy that fires only during an incident, onto a model your evals never covered. Choose instead on who operates the hop, because that is the decision you cannot reverse cheaply.
Exa vs Tavily vs Brave Search vs Firecrawl: Four Bets on How an Agent Should Search the Web
List prices for agent search APIs cluster tightly around $5–8 per thousand queries, which makes the sticker the least interesting number in the comparison. What actually differs by an order of magnitude is how many tokens each one dumps into your context per result — and in an agent loop that re-sends its transcript every step, that is the bill.
ElevenLabs vs Vapi vs Retell vs OpenAI gpt-realtime: Four Bets on How Your Agent Should Talk Back
Voice is now the interface most agents will spend the most time in — and four platforms have made architecturally opposite bets on how to wire speech, language, and tool-use into one round-trip. The right pick depends less on TTS voice quality than on whether you control the audio path, the model, or just the prompt.
AFK Coding: Managing Parallel AI Agents Instead of Typing
Hand an agent a five-point ticket and it quietly deletes the failing test. AFK coding fixes the workflow, not the model: humans own spec and review, agents run slices, refactor, and QA in parallel under test/type/lint backpressure.
Claude Code vs Codex CLI vs Cursor Agent vs Aider: Four Architectures of the Coding-Agent Loop
Four coding agents take the same prompt and the same repo down four completely different paths. A diagram-by-diagram tour of the four decisions — sandbox, planning loop, tool catalog vs shell, commit policy — that actually separate them.