Say you put the current time down to the second in the system prompt, which is the message that goes in front of the entire conversation, then basically nothing will be cached, every agent turn needs to ingest the entire session over and over. Contrast to not doing that, and the backend can leverage caching all the way up to the latest message, as nothing until then changed.
Yes, of course you can destroy it. But how far can you "improve", beyond decent "common sense" behaviour.
Surely other agent CLIs are not dumb enough to invalidate cache on every turn over something so obvious?