Command Center · one page on my phone
One page for the whole estate
What’s waiting on me, what Claude is costing, what’s broken, and what moved — for every repo I run and both of my agents.
A single page on my phone. My PC builds a snapshot every half hour, my two headless agents publish their own status, and a small server folds the two together on every visit, so it answers with the laptop shut. It sends a summary each morning, and buzzes my phone for a new red fault, a new question from an agent, or a snoozed item due back; overnight it stays quiet except for red. Since late September it is also where I act on what is waiting: my own notes, the faults, and the agents’ questions.
Acts on my list, nothing else
A tap closes, snoozes or rewords one of my own notes, acknowledges a fault, or answers an agent. It never deletes an item, never approves an agent’s pull request, and never sends anything to another person.
Derived, not typed
Every number comes from a live source — git, the session transcripts, my notes list, the agents’ own status files. Nothing on the page is kept current by hand.
Honest before calm
A check that can’t run shows as a fault, never as all clear. Each half of the page says how old it is, and a half that stops reporting turns red instead of looking quiet.
Two locks
An email sign-in at the edge, then the server checks that sign-in again itself — on every request, the page’s own files included.
The four questions
What’s waiting on me
Open items from my action-notes list, plus each agent’s open questions, pull requests and approvals.
What Claude is costing
Spend today, this week and this month, by model, with the 5-hour and weekly limits — the agents’ spend counted in.
What’s broken
Failing guard tests, backups, the commit gate, the agents and their box — and any half of the page that stopped reporting.
What moved
Commits in the last 24 hours and the week, mine kept apart from automated ones, stalled focus projects, and commits not yet pushed.
How it ties in here
This public site never connects to it live — it’s gated and private by design. Instead, a reviewed public-safe snapshot is exported: the 7 running architectures you can browse here were published through an opt-in gate that strips anything sensitive before it ever reaches the web.
The safe-export pipeline — private infrastructure → reviewed public snapshot
Retired 25 Sep 2026
The console it replaced
From July to September this was a local-first operations console on my desktop: a modular Next.js app, a file watcher that streamed every change to the screen, an agent-assignment queue only I could close, and a phone app of its own. It retired when one read-only page did the part I used every day. Its architecture, as it ran.