Arbiter blog
Building in the open
Engineering notes from building the orchestration brain: crash recovery, model routing, scheduling around throttling, and what it takes to dispatch an entire AI operation from one agnostic command center.
Headless follow-ups into Claude and Codex
Send a running Claude or Codex session more work from your phone, without opening a window or losing its context. Arbiter reaches into the session it already has.
Read post →Remote control, locked down
Arbiter lets you drive your AI operation from your phone. That power needs a lock on it, so remote control sits behind a per-conversation code from your own authenticator.
Read post →Your standup, run by a local brain
Arbiter's local brain now runs the operations loop: a morning briefing across your projects, a tool-calling chat that knows your repos and recent runs, and dispatch of approved work to your coding agents, with an approval gate and a kill switch in front of anything that matters.
Read post →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.
Read post →Arbiter's brain runs on your GPU
Provider-agnostic shouldn't stop at the providers. Arbiter's routing decisions are made by a local model on your own hardware, with no cloud call in the decision layer and no vendor to depend on.
Read post →You already have an AI fleet. You just don't have a commander.
Arbiter is the OS-level brain above your agents, providers, and jobs: agnostic, survivable, and running on a local GPU. Alone it tames the chaos, and over the full stack it runs the whole operation.
Read post →Provider-agnostic orchestration: why we don't lock you in
Why an orchestration layer should stay neutral about the models, clients, and accounts you bring to it.
Read post →Introducing Arbiter: the orchestration layer your AI stack is missing
A provider-agnostic command center that dispatches and supervises your LLM clients, terminals, and long-running jobs. It routes each to the right model, schedules around throttling, and brings interrupted work back after a crash.
Read post →