upvote

points

by jetbalsa18 hours ago |
comments
upvoteby 383629364818 hours ago|
next
[-]
No? It's not because it's a cache, it's because they're scared of letting you see the thinking trace. If you got the trace you could just send it back in full when it got evicted from the cache. This is how open weight models work.
reply
upvoteby mpyne15 hours ago|
parent|
next
[-]
The trace goes back fine, that's not the issue.

The issue is that if they send the full trace back, it will have to be processed from the start if the cache expired, and doing that will cause a huge one-time hit against your token limit if the session has grown large.

So what Boris talked about is stripping things out of the trace that goes back to regenerate the session if the cache expires. Doing this would help avert burning up the token limit, but it is technically a different conversation, so if CC chooses poorly on stripping parts of the context then it would lead to Claude getting all scatter-brained.

reply
upvoteby charcircuit7 hours ago|
parent|
[-]
>and doing that will cause a huge one-time hit against your token limit if the session has grown large.

Anthropic already profited from generating those tokens. They can afford subsidize reloading context.

reply
upvoteby reactordev17 hours ago|
parent|
prev|
next
[-]
They are sending it back to the cache, the part you are missing is they were charging you for it.
reply
upvoteby eknkc17 hours ago|
parent|
[-]
The blog post says they prune them now not to charge you. That’s the change they implemented.
reply
upvoteby reactordev17 hours ago|
parent|
[-]
right. they were charging you for it, now they aren't because they are just dropping your conversation history.
reply
upvoteby eknkc17 hours ago|
parent|
prev|
[-]
I’m not familiar with the Claude API but OpenAI has an encrypted thking messages option. You get something that you can send back but it is encrypted. Not available on Anthropic?
reply
upvoteby rsfern17 hours ago|
prev|
next
[-]
It seems like an opportunity for a hierarchical cache. Instead of just nuking all context on eviction, couldn’t there be an L2 cache with a longer eviction time so task switching for an hour doesn’t require a full session replay?
reply
upvoteby CjHuber17 hours ago|
prev|
next
[-]
No of course it’s unrealistic for them to hold the cache indefinitely and that’s not the point. You are keeping the session data yourself so you can continue even after cache expiry. The point I‘m making is that it made me very angry that without any announcement they changed behavior to strip the old thinking even when you have it in your session file. There is absolutely no reason to not ask the user about if they want this

And it’s part of a larger problem of unannounced changes it‘s just like when they introduced adaptive thinking to 4.6 a few weeks ago without notice.

Also they seem to be completely unaware that some users might only use Claude code because they are used to it not stripping thinking in contrast to codex.

Anyway I‘m happy that they saw it as a valid refund reason

reply
upvoteby cyanydeez16 hours ago|
prev|
next
[-]
what matters isn't that it's a cache; what matter is it's cached _in the GPU/NPU_ memory and taking up space from another user's active session; to keep that cache in the GPU is a nonstarter for an oversold product. Even putting into cold storage means they still have to load it at the cost of the compute, generally speaking because it again, takes up space from an oversold product.
reply
upvoteby 17 hours ago|
prev|
[-]
deleted
reply