Topic starter
02/09/2026 1:29 pm
TL;DR: AI coding agents in large repositories can burn 156 million context tokens and peak at 459k tokens on a single ~800-line pull request, according to Sonar’s analysis, because every blind read is re-billed across hundreds of turns. The key implication is that graph-based code navigation, not grep, becomes the control that limits cost and missed call sites.
Editorial analysis by NHI Mgmt Group, based on content published by Sonar: “The context tax: why your coding agent reads the same 600 lines 400 times”.
By the numbers:
- The same session peaked at 459k context tokens, close to the window limit Sonar described.
- The analysis says 152.8 million of the billed tokens were cache reads.
Key questions
Q: What breaks when coding agents rely on grep in multi-language codebases?
A: They miss semantic relationships that text search cannot express, such as owner types, return types, cross-language equivalents, and indirect callers.
Q: Why do AI coding agents become expensive in long-running sessions?
A: Because each new turn re-sends prior conversation state, so earlier file reads are paid for again and again.
Q: How can security and engineering teams tell whether agent navigation is failing?
A: Look for broad searches, repeated widening of file slices, high cache-read volume, and builds that fail because the agent missed an indirect reference.
Practitioner guidance
- Instrument context-token usage per task Track fresh input, cache-read, and total billed tokens for each agent session so you can see when navigation overhead is driving cost.
- Replace blind grep with semantic code lookup Route symbol, ownership, and call-site questions through a graph or dependency index instead of broad text searches that widen the context window.
- Set navigation budgets for agent workflows Define a maximum acceptable context footprint for routine changes and flag sessions that keep re-reading the same files across many turns.
Bottom line: Large-repository coding agents can accumulate massive token bills because every exploratory read survives across later turns and gets re-billed.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 2 days ago by NHI Mgmt Group
02/09/2026 1:30 pm
Navigation, not model intelligence, is the limiting factor in large-codebase coding agents. The article shows that the expensive part of the workflow is not generating code, but repeatedly rediscovering code. Once context has to persist across hundreds of turns, every unnecessary read becomes a compounding cost and a compounding failure surface. Practitioners should treat retrieval quality as an agent governance issue, not a convenience feature.
A question worth separating out:
Q: Should teams prefer semantic code graphs over text search for AI coding agents?
A: Yes, when correctness depends on knowing the owner type, the bound definition, or the return path of a symbol. Semantic graphs reduce context bloat and lower the risk of missing call sites that grep cannot express. Text search still has a role for rough discovery, but it is not a reliable control for agentic code navigation.
👉 Read our full editorial: AI coding agents pay a navigation tax when context windows break
This post was modified 2 days ago by NHI Mgmt Group