| ▲ | yumraj 4 hours ago | |
> Since Claude Code uses a 1 hour prompt cache window for the main agent, if you leave your computer for over an hour then continue a stale session, it's often a full cache miss. To improve this, we have shipped a few UX improvements (eg. to nudge you to /clear before continuing a long stale session), and are investigating defaulting to 400k context instead I don’t understand this. I frequently have long breaks. I never want to clear or even compact because I don’t want to lose the conversations that I’ve had and the context. Clearing etc causes other issues like I have to restate everything at times and it misses things. I do try to update the memory which helps. I wish there was a better solution than a time bound cache | ||
| ▲ | cowwoc2020 3 hours ago | parent [-] | |
Makes me wish that shortly before the server-side expiration, we could save the cache on the client-side, indefinitely. But my understanding is that we're talking about ~60GB of data per session, so it sounds unrealistic to do... | ||