Type is claude down _ and the _ becomes a direct answer (No — all systems operational) pulled from Anthropic's public status page. Built for the moment you actually ask that question: mid-prompt, when Claude seems slow.
What you type
Three trigger phrases: is claude down, claude status, and claude api status, leading the sentence your _ ends. The bare forms wipe the command and leave just the answer; a copula phrasing (the claude api is _) keeps your lead-in. And as with every keyword blank, the phrase has to lead the sentence your _ ends, so merely discussing Claude's status in prose never triggers a fetch.
Where the data comes from
The public Statuspage API at status.claude.com/api/v2/summary.json (the code goes straight to the final URL to skip a redirect round-trip). No API key. One fetch, and it works on every host that mounts the runtime with a fetch implementation, native and Chrome alike.
One fetch, four answers to cycle
The blank synthesises four cycling alternatives from the single payload, so Up-arrow surfaces progressively more detail:
- A literal
Yes/Noplus the reason (the default, answering the question you typed). - The one-word status indicator (
none/minor/major/ ...). - A per-component breakdown.
- The active or most recent incident with a relative timestamp.
A deliberately short cache
Results are cached for just 30 seconds. The shipped config explains why: status pivots quickly during incidents, so the 5-minute TTL the weather blank uses would be stale exactly when you care most. The blank is read-only (cycling changes detail level, never external state), dismissible, and clears on edit.
Related: What is a blank? · OpenCues in Claude Code · GitHub repo