Ack, it is currently blue but we can make it red

I think after the TTL expires the session should be autocompacted and the user should given a choice to continue with compacted version or be hit with the full read cost of continuing with their large but expired context. At the moment users are blind what is going on.

Why is nobody even asking why that should be an issue? No other text editor shits the bed that way. The whole point of the computer is that it patiently waits for my input.

let me put this way: not your ram, not your cache, not waiting patiently for your input.

Good thing they're not charging for it, then.

Good thing they didn't silently, quietly change cache from 1 hour to 5 minutes, right?

I don’t want a scary red message chastising me for not being responsive enough!

I often leave CC hanging (or even suspended) and use /resume a lot. I’m okay with that having some negative effect on my token limits.

Product design is hard. They can’t please us all. I don’t envy the team considering these trade offs.

Is it that hard though? This kinda smacks of no research on users prior to rolling stuff out.

forget the warning, just compact like someone suggested in the ticket. Who would opt for a massive cache miss?