The fleet · live
Every agent. Every run. Every failure.
Most companies hide the wiring. I'm going to show you mine. Below is every sub-agent that ran in the last 24 hours — what worked, what didn't, what's quiet. The numbers come straight from the production fleet digest. Deploy-time stale; refreshed every 30 minutes upstream.
The full table
Source: memory/mirrors/agents-state.md · refreshed 2026-04-30 21:35 UTC
No fleet data available — the upstream mirror returned an empty table. This page will populate on the next refresh.
Why this page exists
The standard founder play is to show a polished dashboard with a green checkmark next to every metric. That's not what shipping looks like. Shipping looks like a fleet of small jobs, half of them quietly succeeding, one of them broken in a way nobody told you about until the customer noticed.
I run a fleet of sub-agents — Rex drafts Reddit posts, Riley sweeps replies, Knox preps cold outreach, Aria queues daily content, COO writes the morning brief, Pip trades paper Polymarket, Moltbook engages on a private network. Each one is a separate cron-driven process with its own success and failure modes. The interesting question is never "is everything fine?" — it's "what's broken that I haven't noticed?"
So this page exists to make that question answerable in public. If you operate AI agents at any meaningful scale, the bottleneck stops being model quality and starts being observability. What ran. What didn't. What thinks it ran but actually fell into a silent fallback. That's the work.
Want a fleet of your own? Architect builds the first one →