Arbiter is alive: the orchestration layer, now running
The June update said Arbiter wasn't shipping yet. That's no longer true. The daemon runs: a local brain on your own GPU, multi-provider rerouting, work that survives a power cut, and remote control over the channels you already use. Still alpha, but it's real, and there's an 8-minute walkthrough.
A few weeks ago we wrote that Arbiter was in active development and not shipping yet. That was honest then. It isn’t accurate anymore. The orchestration layer is no longer a blueprint. It’s a daemon running on real hardware, and you can watch it work.
What actually runs now
- A brain on your own GPU. The model that decides how to route a task runs locally, on your machine. The decision layer makes no cloud call. It triages incoming work and answers what it can on-device.
- Provider-agnostic, by construction. Arbiter pools the LLM accounts you already have and reroutes around rate limits and exhausted quotas instead of failing. Add providers and it gets sharper, with nothing load-bearing.
- Work that survives a power cut. Long-running jobs are accounted and recoverable. Pull the plug mid-flight and the state isn’t gone. It’s preserved and picked back up, with the riskier kinds of work held for your explicit say-so rather than silently resumed.
- Remote control over channels you already use. Check status and approve or stop work from your phone. The conductor doesn’t require you to be at the keyboard.
- A real command center. A native desktop GUI and a terminal dashboard both show live status, with a kill switch always in reach. The daemon opens no inbound network port, so control is local, authenticated, and over a private channel.
A risk floor the optimizer can’t cross
Cost optimization is good right up until it routes something destructive to the cheapest, weakest model. Arbiter draws a hard line: irreversible and destructive operations are never sent to the bottom tier, and they’re flagged for approval. “Spend less” and “never route a destructive action carelessly” hold at the same time, by design rather than by good intentions.
Watch it run
Words only go so far for an orchestration layer. Here’s an unedited 8-minute walkthrough of the running daemon on a real machine: the routing, the live runs, and the approvals.
Prefer YouTube? Watch the walkthrough there instead.
Where it stands
Arbiter is in working alpha: live-proven on real hardware, not yet GA, and we’re hardening real-world use before any version promises. The agnostic-by-construction design, all the way down to a local decision brain, is the part we won’t compromise.
It’s the layer that dispatches Warden, orchestrates TheAuditor, and leans on Curator for memory and BenchProctor for proof. The full scope is in Introducing Arbiter, or follow the RSS feed.