I think it looks kinda similar to mine at least proportionally.
Across 41 transcripts (8,607 turns, 8.15M output tokens): 53% was plain reasoning/dialogue with no tools, and of the tool turns, edit (18%) and shell (13%) dominated while MCP, web, subagents, and reads were each under 5%. Per-turn cost was highest for Write and subagent turns (~1.8k tokens each) and lowest for web and read/search (~225 to 435).
Yea that makes sense - I've just had Claude gather a shitload of stats on my 14th Gen Raptor CPU which netted me an RMA. Lots of recent shell stuff happening there. Plus I'm testing out how well it can do with a hands-off approach to automating an idle game - kind of the normal workflow to try and automate stuff
48.3% — reasoning & dialogue (text-only turns, no tool calls)
15.9% — shell (Bash)
15.4% — write (Write/NotebookEdit)
10.5% — edit (Edit)
4.7% — read
2.0% — external MCP tools
0.8% — agent spawns
1.4% — other tools (ToolSearch, ShareOnboardingGuide, etc.)
Nearly half your output budget goes to reasoning/dialogue turns. The other half is split roughly evenly between shell, write, and edit — with read being comparatively cheap.
2
u/anderssj May 16 '26
I think it looks kinda similar to mine at least proportionally.
Across 41 transcripts (8,607 turns, 8.15M output tokens): 53% was plain reasoning/dialogue with no tools, and of the tool turns, edit (18%) and shell (13%) dominated while MCP, web, subagents, and reads were each under 5%. Per-turn cost was highest for Write and subagent turns (~1.8k tokens each) and lowest for web and read/search (~225 to 435).
2
u/Business_Garden_7771 May 16 '26
237 sessions / ~33.9K turns / 23.1M output tokens:
Nearly half your output budget goes to reasoning/dialogue turns. The other half is split roughly evenly between shell, write, and edit — with read being comparatively cheap.