logoalt Hacker News

JumpCrisscrossyesterday at 7:39 PM4 repliesview on HN

> I was never under the impression that gaps in conversations would increase costs

The UI could indicate this by showing a timer before context is dumped.


Replies

vyryesterday at 11:42 PM

a countdown clock telling you that you should talk to the model again before your streak expires? that's the kind of UX i'd expect from an F2P mobile game or an abandoned shopping cart nag notification

show 2 replies
karsinkkyesterday at 7:43 PM

Yes!! A UI widget that shows how far along on the prompt cache eviction timelines we are would be great.

vanviegentoday at 8:47 AM

That sounds stressful.

But perhaps Claude Code could detect that you're actively working on this stuff (like typing a prompt or accessing the files modified by the session), and send keep-cache-alive pings based on that? Presumably these pings could be pretty cheap, as the kv-cache wouldn't need to be loaded back into VRAM for this. If that would work reliably, cache expiry timeouts could be more aggressive (5 min instead of an hour).

jimkleibertoday at 12:44 AM

I tried to hack the statusline to show this but when i tried, i don't think the api gave that info. I'd love if they let us have more variables to access in the statusline.