DEV Community

Dmitriy Solodukha
Dmitriy Solodukha

Posted on

My coding agents would have cost $8,360 in 30 days. Here's where it went.

I build a developer tool alone, with Claude Code and Codex running most of the day. For the last 30 days (8 October to 6 November 2026) I priced every call they made at API list rates.

The total: $8,360. Claude: $8,056. Codex: $304.

That isn't my bill. I'm on a flat plan, so what I actually paid is the plan fee. The $8,360 is what the same work would have cost through the API. I watch it because it tells me whether the plan is paying for itself, and which work is expensive.

The days are uneven

  • Busiest day: 14 October, $670.
  • Quietest day: 19 October, $92.

A sevenfold spread between two days of the same person on the same projects. A monthly average hides that, and the busiest day is what a plan's limits have to hold.

One model takes nearly all of it

About nine dollars in every ten went to Claude Opus. Everything else together — Fable, Sonnet, Haiku and OpenAI's GPT models through Codex — is the remaining tenth. If I want the number lower, choosing a model per task does more than anything else.

Per pull request, it's small

In one October week, 45 pull requests merged on my main project. The agents' work on them came to $343.78, or $7.64 per pull request at list price. The most expensive single one cost $71.13. Seen that way, the useful question isn't the monthly total but which changes cost nine times the average, and why.

How I measured it

Claude Code and Codex both keep their own session logs on disk, and neither adds its sessions up with the other's. I read both into one local table and price every turn by model at list price. Nothing leaves the machine.

The tool I use for this is the one I'm building: Caprock, a free, open-source (Apache-2.0) desktop app for macOS, Windows and Linux. You don't need it to do this, though. The logs are in ~/.claude/projects/ and ~/.codex/sessions/, and the prices are on Anthropic's and OpenAI's pricing pages. A script can do the same sum.

What I'd tell someone starting

  1. Look at one week of your own numbers before choosing a plan. Mine would be a terrible fit for pay-as-you-go and a good one for a flat plan. Yours may be the opposite.
  2. Watch the busiest day, not the average. It's what your plan's limits have to hold.
  3. Price the pull request, not the month. A monthly total says little; cost per merged change says whether the agents are worth it.

The full numbers, with the method, are on caprock.dev/numbers.

Top comments (0)