Cache Clock for Copilot CLI Diagram

Guard

Asks before a costly cold send, once per cold episode: Send anyway, or Don't send (hold, 0 AI credits)
No answer in 5 minutes holds the send. A host that cannot ask gets the old refuse-once message
Slash commands and ! shell escapes are never guarded; a running turn only gets the price note
refused.json lets the next send, even from a new process, through

Clock

TTL, expiry and prices come from assistant.usage; nothing is guessed
assistant.usage is not replayed on resume, so events.jsonl seeds the clock
Heads-up leads by the smaller of the setting and a fifth of the TTL, never mid-turn

VS Code, measured 11-12 Oct 2026

Extension loads only with chat.canvases.enabled, from a project install (.github/extensions)
Cards, help and settings show as a question with OK; the heads-up and sending-cold note reach only VS Code's log
Sessions keep usage checkpoints only, so the report counts them as totals

Limits

Reported expiry is an upper bound: Luna was served cold at 29 of 30 minutes
/cache-clock works typed in full in VS Code but is not in its / menu
No keep-warm pings yet