Earlier quoted context omitted.
While we are all speculating, Boris kindly provided some guidance in https://news.ycombinator.com/item?id=47880089 > The challenge is: when you let a session idle for >1 hour, when you come back to it and send a prompt, it will be a full cache miss, all N messages. We noticed that this corner case led to outsized token costs for users. In an extreme case, if you had 900k tokens in your context window, then idled for…
Recently I started getting messages from Clause Code (on a plan). "You're restoring an old session are you sure you don't want to compress the context? This will use a substantial amount of your usage quota" So it seems they do care.
Meanwhile, they don't really care if you use hundreds of millions of cached input tokens, which doesn't consume any FLOP.