Developer analyzes 400k Claude Code calls for context costs
11/11/2026 — 11/11, 21:15·1 sources (all)·1 reports (all)
Key takeaways
- A developer broke down roughly 9,600 Claude Code calls from November 7 by main sessions and subagents. Every call above 400k tokens came fro…
- five such sessions accounted for all 400k-plus usage, with three making up 94%, and most costs came from cache reads.
Background & analysis
On 2026-11-11 21:08, a developer posted an analysis on DEV Community after a reader, @junfengzhou01, asked under the author's previous post whether the 400k+ context calls came from long-lived main sessions or from sub-agents reading large files. The author had not known, and went back to the same local logs to find out. The sample covers 9,604 Claude Code calls made on 7 Nov, priced at list price, and the logs were split into main session calls and sub-agent calls, with token bands and costs tallied for each group.
AI-generated from 1 reports · updated 2 days ago
Related AI tools
- Heat index
- 25
- All sources
- 1
- All reports
- 1
- First seen
- 2 days ago
Reports on this story headlines open the original
A developer split roughly 9,600 Claude Code calls from Nov 7 into main-session and sub-agent calls, finding that every call above 400k tokens came from long-running main sessions; no sub-agent exceeded 365k. Five main sessions accounted for all of the 400k+ spend, three of them 94% of it, and most of that cost was cache reads.
DEV Community · AIAI score 58
Other stories people are talking about
- Heat index 98NewDeveloper shares Claude Code context control and subagent model routing1 sources
- Heat index 71Shared memory for Claude Code and Codex: pull it on demand, don't inject it1 sources
- Heat index 74Developer Builds 50-Floor Tower Defense Web Game with Claude1 sources
- Heat index 85Developers Discuss Boundaries and Challenges of Claude Opus 5.5 in Multi-Round Code Reviews1 sources
- Heat index 90NewDeveloper Shares Experience Using Claude to Structure 3D Configurator Rules from Catalogs1 sources
How is heat calculated?About the methodHide
Heat counts how many independent sources covered a story in the last 48 hours: one source counts once no matter how many posts it published, decaying with a 24-hour half-life. What ranks first is what many people are talking about.
This page aggregates public feeds. Headlines and summaries are machine-organized and remain the property of the original authors; verify important facts at the source. If you believe a headline or summary infringes your rights, email the contact address in the footer with the page URL and basis of your claim, and we will remove or replace it after review.
- Surge
- Discussion rising fast
- New
- First report within 6 hours
- Rising
- Still gathering discussion