Hey, last time I’ve reported the issues on reddit and github and there was a lot of oncoming commotion and people trying to help with the situation. There’s been a lot of good things happening, like community coming together trying to find the real culprit. I’m very grateful for all of the reactions, emotional comments you’ve all had. Every piece of comment that you’ve had is a statement of your disagreement that is valuable in this context. It all brings us closer to resolving all of the issues. Now, to summarize the fixes that has been applied: Sentinel cch=00000 is still dangerous (even though some people report it being fixed) –resume or /resume still resets cache somehow (although some people report it had fixed some of their problems) - it may be false negative due to testing methodology Some users theorize that resume bug is somehow session related, me included. However that doesn’t explain the fact, that we’re running in stateless http context. My theory is that it is all server related . It explains some of my findings: running multiple requests from the same pc (like spawning a lot of agents at the same time) causes the cache to sometimes get invalidated in some requests; resume cache bug still not resolved (even though requests look the same). So there is no way for us to fix anything, even if we go deeper. Some versions are more stable than others, of course (sending less requests than others). I’ve been recommending everyone to downgrade to 2.1.68 since some time and many people have reported it fixed the issues. But some have came back saying, that it did not. My only hypothesis is - because none of them returned to me with a reply - that they still had auto update channel set to “latest” and no version pinning set up. I’m not sure how you can do it on your own machine, but I had to do it in ~/.bashrc. As a sidenote, before this whole issue arose, I created a plugin that was going to help you create plugins, I called it hooker . However as I was preparing myself to show it to you guys my cache broke, so I wanted to add a hook to check if cache is currently broken. It grew enough for me to warrant creating another plugin: Cache catcher (it’s in the same marketplace, so repo above still applies). It autodetects if last turn had increased token usage and can warn or block further execution. Easily configurable. Try it and report me how were your findings. There are other community tools that might help you. User @kyzzen mentioned he worked on similar setup, @ArkNill has created a helpful analysis and is active in most issues I’ll mention, @weilhalt created budmon a utility for monitoring your budget. Feel free to use them to mitigate those problems. Also make sure to visit those issues to find out more about how people mitigate them: https://github.com/anthropics/claude-code/issues/38335 https://github.com/anthropics/claude-code/issues/40652 https://github.com/anthropics/claude-code/issues/42260 https://github.com/anthropics/claude-code/issues/40524 https://github.com/anthropics/claude-code/issues/42052 https://github.com/anthropics/claude-code/issues/34629 Please contribute to the discussion however you can. Install proxies for yourself, monitor your usage as thoroughly as possible. Make it as visible to anthropic as possible, that it is THEIR FAULT, not yours. submitted by /u/skibidi-toaleta-2137
Originally posted by u/skibidi-toaleta-2137 on r/ClaudeCode
You must log in or # to comment.