How much does Cursor agent 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 Cursor agent bug fix of about 26 model calls costs around $0.34 on GPT-5.1 Codex and $1.26 on Claude Opus 4.8. One coffee break that expires the cache plus one fix-and-test loop takes that to $0.44 and $1.73.
Billed by Cursor from your plan’s usage; the figures here are the equivalent at the labs’ API list prices.
Real medians from receipts
Cursor agent does not write a session log we can read yet, so there are no measured receipts for it. The numbers below are worked examples at the equivalent API list prices.
Worked example: one bug fix
Worked example · modelled, not measured| Model | Tidy session | +1 idle miss, +1 loop | Cache hit |
|---|---|---|---|
| Claude Sonnet 4.6 | $0.75 | $1.04 | 95% |
| GPT-5.1 Codex | $0.34 | $0.44 | 95% |
| Claude Opus 4.8 | $1.26 | $1.73 | 95% |
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 GPT-5.1 Codex example, cache reads are $0.15, cache writes $0.08 and output $0.11. 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.07 for one turn, and AgentReceipt marks $0.09 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.