AgentReceipt

How much does Claude Code cost per bug fix?

Reproduce, find the cause, patch, and prove it with a test. Short sessions, but retry loops are common. Here is what that costs at list prices, how much of it is usually avoidable, and real numbers from itemized receipts as they come in.

Short answer

A tidy Claude Code bug fix of about 26 model calls costs around $0.75 on Claude Sonnet 4.6 and $1.26 on Claude Opus 4.8. One coffee break that expires the cache plus one fix-and-test loop takes that to $1.04 and $1.73.

Billed per token on the Anthropic API, Bedrock or Vertex, or included in a Pro/Max subscription.

Real medians from receipts

Not enough receipts yet to publish a real median (4 of the 30 we wait for). Until then, the numbers below are worked examples, clearly modelled. Save a receipt to contribute; only aggregate medians are ever shown.

Worked example: one bug fix

Worked example · modelled, not measured
ModelTidy session+1 idle miss, +1 loopCache hit
Claude Haiku 4.5$0.25$0.3595%
Claude Sonnet 4.6$0.75$1.0495%
Claude Opus 4.8$1.26$1.7395%

26 model calls, 20k tokens of starting context growing about 1.4k per call, 420 output tokens per call, list prices. The second column adds a 9-minute pause that expires the cache and a 3-attempt fix-and-test loop.

Where the money goes

In the Claude Sonnet 4.6 example, cache reads are $0.35, cache writes $0.23 and output $0.16. Because the whole context is re-sent on every call, the bill grows with the square of the session length: a bug fix that takes twice as many calls costs roughly three to four times as much.

In the messy version, the expired cache alone adds $0.20 for one turn, and AgentReceipt marks $0.27 of the session as avoidable.

How to make a bug fix cheaper

  • Keep one bug fix per session and /clear between tasks, so the context stays small.
  • Do not leave a session idle for more than 5 minutes in the middle of the work; the cache expires.
  • Stop retry loops after two failed attempts and give the agent the exact error.
  • Trim tool output (head, grep, line ranges): every token stays in context for the rest of the session.
  • Use a smaller model or a subagent for exploration; save Claude Opus 4.8 for the hard edits.

Itemize your own session

Drop a Claude Code or Codex log. It is parsed in your browser, and you get your real numbers instead of a model.

Drop a session log here

Claude Code ~/.claude/projects/…/*.jsonl, a Codex rollout ~/.codex/sessions/…/rollout-*.jsonl, or the claude-code-action execution file.

Parsed in your browser. Your prompts and code never leave this tab.