Everyone who has not hit this bug thinks it’s user error… It’s not. It happened ...

dmd · 2026-03-31T15:30:29 1774971029

I'm on Max. This morning, just to test, before doing anything else whatsoever, I was at 0%, and I typed 'test one two three' into CC.

That put me at 12%.

I have no MCPs except the built in claude-in-chrome.

This is clearly a bug.

cyanydeez · 2026-03-31T23:32:51 1774999971

Readimg through this thread, it seems likely is a KV cache "bug". Theyre likely doing too many evictions of the LLM cache so the context is being reloaded to often.

Its a "bug" because its probably an intended effect of capturing the costs of compute but surfacing a fact that they oversold compute to a situations where they cant keep the KV cache hot and now its thrashing.

bensyverson · 2026-04-01T14:31:17 1775053877

Caching helps them too, so I hope they fix it

piva00 · 2026-03-31T13:18:14 1774963094

Don't they consume less of the token quota in case the subagents are running cheaper models like Sonnet and Haiku compared to Opus?

bensyverson · 2026-03-31T14:05:02 1774965902

Correct—I just wouldn't want folks to mistakenly think that the context fill % corresponds 1:1 with session token use.

master_crab · 2026-03-31T13:44:12 1774964652

Yes, sorry. I meant it more as a descriptor of how many tokens it consumes. You are still stuck burning money.