Claude Code burns ~15–20% of your tokens on a 3-word status line

Re:Claude Code burns ~15–20% of your tokens on a 3-word stat... by edwinarbus on Thursday October 29, 2026 @12:52AM (#50284699)

I work on Claude Code. You've got the basic mechanism right, but to be super clear, this only applies to background agents that are actively working. They get a summary call about every 30 seconds, and idle background agents don't. These summaries are used for both you and Claude Code to track what each background agent is working on, without reading transcripts.

Your 16.4% sounds like it was for a team running mostly background agents, and doesn't seem like a typical session. (Feel free to send me the session ID at [email protected] and we can dig further.)

Last week, across Claude Code users who send us telemetry, agent_summary was about 2% of cost at API list prices and just under 4% of requests. In the terminal, where nearly all of these calls happen, it was about 6% of cost.

That said, we agree that's a lot for a status line. We just rolled out a fix for the most expensive case, summaries that miss the prompt cache (2.1.311+), and right now we're working on a much cheaper mode that sends short notes to a smaller model instead of the full transcript.

[ Parent | on HN ]

Re:Claude Code burns ~15–20% of your tokens on a 3-word stat... by jawr on Thursday October 29, 2026 @02:41AM (#50285290)

Sorry to side swipe this, but it's related to token usage :peek:

Are you aware of any updates on the SDK using more session usage vs claude code (https://github.com/anthropics/claude-code/issues/97074)?

[ Parent | on HN ]

Re:Claude Code burns ~15–20% of your tokens on a 3-word stat... by rptx on Thursday October 29, 2026 @02:49AM (#50285327)

That helps put the 16 percent in context. I think it would be better to add a real setting to turn agent summaries off... in the current binary, both the sdk option and the env var can only switch them on

[ Parent | on HN ]

Re:Claude Code burns ~15–20% of your tokens on a 3-word stat... by esikich on Thursday October 29, 2026 @02:19AM (#50285152)

You're telling us there are frequent scheduled summary calls to agents that burns tokens like this is common knowledge. Is it? And is this documented somewhere?

[ Parent | on HN ]

Re:Claude Code burns ~15–20% of your tokens on a 3-word stat... by simoncion on Thursday October 29, 2026 @02:26AM (#50285189)

Perhaps this is terminology confusion, but the official docs explicitly state that status lines "[Run] locally and [do] not consume API tokens." [0] _If_ that documentation is talking about the same thing that TFA is talking about, then I'd say that this is very much not common knowledge.

I also wonder if the fix that they "just rolled out" is actually activating the 'short' mode that TFA mentions...

[0] <https://code.claude.com/docs/en/statusline#how-status-lines-...>

[ Parent | on HN ]

Re:Claude Code burns ~15–20% of your tokens on a 3-word stat... by xyzsparetimexyz on Thursday October 29, 2026 @03:05AM (#50285430)

Status lines should either be optional or the tokens used for them is free. Anything else is insane.

[ Parent | on HN ]

Re:Claude Code burns ~15–20% of your tokens on a 3-word stat... by abelw on Thursday October 29, 2026 @07:18AM (#50287280)

I'm also at 15+%. This feels like a lot when I think back on how often I've hit the weekly limit.

[ Parent | on HN ]

Re:Claude Code burns ~15–20% of your tokens on a 3-word stat... by eddyg on Thursday October 29, 2026 @08:24AM (#50287824)

Thank you for jumping in to the fray and providing additional context, data and updates!

[ Parent | on HN ]

Re:Claude Code burns ~15–20% of your tokens on a 3-word stat... by subscribed on Thursday October 29, 2026 @09:38AM (#50288850)

So are we just holding it wrong, or is the distinct absence of any mechanism to tune/turn it off for our own good?

Also why you're so dismissive with the 2/4% figure while completely ignoring the TFA analysis and the other examples in their linked github issue?

Seriously, you're adding a feature that silently burns 15-25% tokens (that is burning money for API clients while hiding that fact), take away everything that could be used to mitigate it, and your response is basically, "eh, your numbers are unimportant and ours say it's negligible but since you complain we'll make it a bit cheaper".

Seriously, that looks so intentionally customer-hostile and revenue-friendly, but reading the room no one is surprised.

[ Parent | on HN ]