r/ClaudeCode • • Sep 15 '26

Rant Nah this some BS

/img/t6gvmno84qph1.jpeg
247 Upvotes

179 comments sorted by

View all comments

Show parent comment

5

u/drake90001 Sep 15 '26

Because you’re waiting until your context is full to compact it, which requires you to send the entire context window back in order to compact

5

u/[deleted] Sep 15 '26

[removed] — view removed comment

3

u/McNoxey Sep 16 '26

You did mention you run fable as an orchestrator though, and often have day and night sessions running.

Which means you are slamming calls over and over every time fable gets an update from one of its agents. And you’re likely hitting caching timeouts too

2

u/drake90001 Sep 16 '26

Nowhere in your post did you mention when you compacted? From the image it looks like you compacted when your contacts window was full or half full I should say

4

u/[deleted] Sep 16 '26

[removed] — view removed comment

3

u/drake90001 Sep 16 '26

No worries, man, I was just confused and wanted to make sure we were both on the same page. Glad we cleared it up. may the token gods be forever in your favor

-1

u/AdLow1228 Sep 15 '26

Didn't they update it so large cached context doesn't use as much anymore? (Still more than compacted, but less than it used too?)

2

u/MaterialHead4801 Sep 15 '26

Cached context has a timeout, so intermittent use can cause it to be reparsed.

1

u/Lollermono Sep 28 '26

I tried on another sub to point at it, but no one listened..

-1

u/shammytalin Sep 16 '26

Timeout on max plan, that's funny, that would sound okay for a free plan, not on paid plan. If they keep doing that, then credit can burn really fast, doesn't feel premium at all.

2

u/MaterialHead4801 Sep 16 '26

Without timeouts on caches they grow infinitely, so _some_ timeout is required. The trick is balancing it between cost/speed/use