News for hackers. Stuff that matters.
Re:An update on recent Claude Code quality reports by mpyne on Thursday April 23, 2026 @06:12PM (#47882827)
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.

Re:An update on recent Claude Code quality reports by charcircuit on Friday April 24, 2026 @02:55AM (#47886572)
>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.

Re:An update on recent Claude Code quality reports by pixl97 on Friday April 24, 2026 @03:04PM (#47894476)
No they can't, that's what you don't seem to get.

Reloading those tokens takes around the same effort as processing them in the first place.

It's ok to be ignorant of how the infrastructure for LLMs work, just don't be proud of it.

Re:An update on recent Claude Code quality reports by charcircuit on Friday April 24, 2026 @08:12PM (#47897352)
They literally can. They could make the API free to use if they wanted. There is no law that states that costs have to equal the cost it takes to process the request.