Notifications
Clear all
Topic starter
18/08/2026 2:16 pm
TL;DR: Coding-agent spend can swing by as much as 30x on the same task, and HoneyHive argues that session totals hide the step, model, and outcome data needed to explain why. The real control problem is no longer seat licensing but tracing agent trajectories well enough to separate productive runs from wasteful ones.
NHIMG editorial — based on content published by HoneyHive: The Tokenomics Problem With Coding Agents
By the numbers:
- Run the same coding-agent task more than once and the cost can swing by as much as 30x.
- RBC's token usage is up 500% year over year.
Questions worth separating out
Q: What breaks when coding-agent spend is capped without trace-level visibility?
A: A hard cap stops runaway bills, but it also blocks productive sessions because it cannot tell whether spend came from a useful run or a looping failure.
Q: Why do coding agents complicate governance for software identities?
A: Coding agents are not fixed tools that run once and stop.
Q: How can teams tell whether agent spend is normal or wasteful?
A: They need to compare cost with outcome at the step level.
Practitioner guidance
- Implement step-level cost attribution Track token usage by session, step, model, and outcome so finance can see the exact source of waste instead of only a month-end total.
- Route low-risk tasks to cheaper models Apply policy-based model selection so routine coding work is steered away from expensive reasoning models unless task complexity justifies them.
- Score output quality alongside spend Attach an evaluator to each run so a low-cost failure and a high-value success are not treated as equivalent in reporting.
What's in the full article
HoneyHive's full analysis covers the operational detail this post intentionally leaves for the source:
- Step-by-step tracing of Claude Code sessions through hooks and daemon capture
- Devin exporter details for batch or daemon sync, including session metadata and billing fields
- Practical setup examples for turning session telemetry into spend attribution and model routing
- How evaluator scores can be tied to agent outputs for cost-versus-value review
👉 Read HoneyHive's analysis of coding agent tokenomics and session tracing →
Coding agent token spend is spiking, but what should teams control?
Explore further
18/08/2026 3:09 pm
Seat-based budgeting is now a weak control model for agentic work. When the same coding task can cost 30x more on a different run, the issue is not procurement variance but runtime behaviour that finance-only controls cannot explain. For identity and governance teams, that matters because software identities are no longer static consumers of licensed capacity. They are active decisioning entities whose tool use, model choice, and session length need policy. The practitioner conclusion is that cost governance has to move closer to execution.
A question worth separating out:
Q: Should organisations use cost caps or behaviour tracing for coding agents?
A: Behaviour tracing should come first because it explains why spend occurs. Cost caps are useful as a backstop, but they are blunt and can hide the very patterns teams need to fix. Once tracing is in place, caps can target true outliers while leaving productive sessions with enough room to complete their work.
👉 Read our full editorial: Coding agent tokenomics expose the limits of seat-based AI budgeting
