Code Mode in production: "26 tool calls, one script, $0.02" prices the end of the tool loop

In plain terms. Instead of letting an agent guess which tool to call, turn after turn, you hand it a typed SDK and let it write a short script that orchestrates the calls. Result: ~99% fewer tokens, sensibly lower latency, and a bill that literally drops from $2 to $0.02 on a mid-size workflow.

Agent Swarm just published the clearest measurement to date: « 26 tool calls, one script, $0.02 ». On an identical production pipeline, the classic tool loop consumes ~1.17M context tokens to transport tool definitions and returns; Code Mode passes a typed SDK, lets the model write a TypeScript or Python snippet, and a V8 sandbox (at Cloudflare) executes it. The result isn't a projection: $0.02 measured, on a call model that cost $2+ in tool loop.

The figure reproduces two prior benchmarks. Cloudflare published a 99.9% token reduction (1,000 vs 1.17M) on its Workers runtime in April 2026. Anthropic measured 98.7% on the Drive→Salesforce scenario (150,000 → 2,000 tokens). The three experiments converge to ~2 orders of magnitude - independently of the model, since it's the context that explodes or not: the dollar reduction is model-invariant. Bonus: latency -30 to -40% (agent round trips removed).

Under the hood. The pattern replaces the loop « describe all tools → choose a tool → return result → restart » with two primitives: search(query) (find a tool or entity) and execute(script) (execute code that coordinates the calls). The typed SDK matters more than the primitive: it's what gives the model the API surface without having to re-describe it every turn. Mandatory sandbox (isolated V8 at Cloudflare, locked variants like Starlark elsewhere) - it's arbitrary code that runs on the gateway.

Limitations that the measurement doesn't hide: ultra-simple workflows (1-2 tool calls) don't benefit - the SDK prompt fixed cost dominates. The sandbox costs to run (isolate, quota, kill switch). Failures are more correlated: a faulty script breaks the entire pipeline, whereas a tool loop can recover step by step.

So what. The tool loop as we coded it in 2024-2025 no longer has a reason to exist for any non-trivial workflow. Orchestrators (LangGraph and competitors) will have to support the pattern or disappear from the price comparison. For teams running agents in production: measure your tokens/mission ratio over a month - if you're at 100k+ tokens per mission, the migration pays for itself in a week. MCP plumbing found its killer app.