News for hackers. Stuff that matters.
Re:An update on recent Claude Code quality reports by bavell on Friday April 24, 2026 @08:08AM (#47889115)
> As a user, I _expect_ the cost of resuming X hours/days later to be no different to resuming seconds or minutes later.

As an informed user who understands his tools, I of course expect large uncached conversations to massively eat into my token budget, since that's how all of the big LLM providers work. I also understand these providers are businesses trying to make money and they aren't going to hold every conversation in their caches indefinitely.

Re:An update on recent Claude Code quality reports by andrewingram on Friday April 24, 2026 @09:23AM (#47889880)
I'd hazard a guess that there's a large gulf between proportion of users who know as much as you, and the total number using these tools. The fact that a message can perform wildly differently (in either cost, or behaviour if using one of the mitigations) based on whether I send it at t vs t+1 seems like a major UX issue, especially given t is very likely not exposed in the UI.
Re:An update on recent Claude Code quality reports by bavell on Saturday April 25, 2026 @09:12AM (#47901327)
I definitely agree that it should be shown and obvious in the UI. They do show a warning now when resuming old sessions but still could be better.