News for hackers. Stuff that matters.
Re:An update on recent Claude Code quality reports by artdigital on Thursday April 23, 2026 @07:37PM (#47883672)
I'm also a Claude Code user from day 1 here, back from when it wasn't included in the Pro/Max subscriptions yet, and I was absolutely not aware of this either. Your explanation makes sense, but I naively was also under the impression that re-using older existing conversations that I had open would just continue the conversation as is and not be a treated as a full cache miss.

My biggest learning here is the 1 hour cache window. I often have multiple Claudes open and it happens frequently that they're idle for 1+ hours.

This cache information should probably get displayed somewhere within Claude Code

Re:An update on recent Claude Code quality reports by bcherny on Thursday April 23, 2026 @07:45PM (#47883735)
Yep, agree. We added a little "/clear to save XXX tokens" notice in the bottom right, and will keep iterating on this. Thanks for being an early user!
Re:An update on recent Claude Code quality reports by Implicated on Thursday April 23, 2026 @08:06PM (#47883869)
But.. that doesn't solve the problem of having no indication in-session when it'll lose the cache. A nudge to /clear does nothing to indicate "or else face significant cost" nor does it indicate "your cache is stale".

Love the product. <3

Re:An update on recent Claude Code quality reports by troupo on Friday April 24, 2026 @01:41AM (#47886034)
Instead of showing actual usage, costs and cache status you spent two months denying the issue even exists, making the product silently worse, and now you're "iterating on this"
Re:An update on recent Claude Code quality reports by troupo on Friday April 24, 2026 @05:01AM (#47887568)
To add to this. The new indicator is "New task? /clear to save <X> tokens" even though it affects all tasks, not just new ones.

Mislead, gaslight, misdirect is the name of the game