AI agent cost management fails when cost is treated as a monthly bill as opposed to a runtime signal.
A coding agent spends money differently than a bill. The agent could spend money by selecting a model for a specific task, using dragged-in context from past tasks, calling tools along the way from past tasks as well as other subagents that are passed work to complete. And the spending happens in a loop of retry and re-evaluation and passing of work until a harness or developer stops the agent from running more.
First, LangChain concisely outlined the problem with spend from coding agents in its June 15 post about making coding-agent spend predictable: a heavy user can spend thousands per week before anyone notices. Anthropic's 2026 coding-agent report gives the other side of the same pressure. Developers already use AI in roughly 60% of their work while fully delegating only 0 to 20% of tasks. So even if the behavior of an agent could be made predictable and therefore controllable, the agents are already active enough that they consume tokens, pay for tools, and pay for reviewer time.
The bill arrives after the behavior
The spend is treated as finance information and finance sees the spend after the system has already behaved. Engineering owns the behavior of the coding agent.
