<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Arbiter Blog</title><description>Engineering notes from building Arbiter: orchestration, crash recovery, model routing, and the agnostic dispatch layer for your AI operation.</description><link>https://blog.arbitermcp.com/</link><language>en-us</language><item><title>Headless follow-ups into Claude and Codex</title><link>https://blog.arbitermcp.com/headless-followups-claude-and-codex/</link><guid isPermaLink="true">https://blog.arbitermcp.com/headless-followups-claude-and-codex/</guid><description>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.</description><pubDate>Wed, 01 Jul 2026 00:00:00 GMT</pubDate><category>orchestration</category><category>delegation</category><author>Arbiter</author></item><item><title>Remote control, locked down</title><link>https://blog.arbitermcp.com/remote-control-locked-down/</link><guid isPermaLink="true">https://blog.arbitermcp.com/remote-control-locked-down/</guid><description>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.</description><pubDate>Sun, 28 Jun 2026 00:00:00 GMT</pubDate><category>security</category><category>remote-control</category><category>2fa</category><author>Arbiter</author></item><item><title>Your standup, run by a local brain</title><link>https://blog.arbitermcp.com/your-standup-run-by-a-local-brain/</link><guid isPermaLink="true">https://blog.arbitermcp.com/your-standup-run-by-a-local-brain/</guid><description>Arbiter&apos;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.</description><pubDate>Wed, 24 Jun 2026 00:00:00 GMT</pubDate><category>orchestration</category><category>local-llm</category><category>supervision</category><author>Arbiter</author></item><item><title>Arbiter is alive: the orchestration layer, now running</title><link>https://blog.arbitermcp.com/arbiter-is-alive/</link><guid isPermaLink="true">https://blog.arbitermcp.com/arbiter-is-alive/</guid><description>The June update said Arbiter wasn&apos;t shipping yet. That&apos;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&apos;s real, and there&apos;s an 8-minute walkthrough.</description><pubDate>Tue, 16 Jun 2026 00:00:00 GMT</pubDate><category>orchestration</category><category>alpha</category><category>demo</category><author>Arbiter</author></item><item><title>Arbiter&apos;s brain runs on your GPU</title><link>https://blog.arbitermcp.com/the-brain-runs-on-your-gpu/</link><guid isPermaLink="true">https://blog.arbitermcp.com/the-brain-runs-on-your-gpu/</guid><description>Provider-agnostic shouldn&apos;t stop at the providers. Arbiter&apos;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.</description><pubDate>Thu, 11 Jun 2026 00:00:00 GMT</pubDate><category>orchestration</category><category>local-llm</category><category>privacy</category><author>Arbiter</author></item><item><title>You already have an AI fleet. You just don&apos;t have a commander.</title><link>https://blog.arbitermcp.com/the-ai-stack-arbiter-orchestrates/</link><guid isPermaLink="true">https://blog.arbitermcp.com/the-ai-stack-arbiter-orchestrates/</guid><description>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.</description><pubDate>Wed, 10 Jun 2026 00:00:00 GMT</pubDate><category>ecosystem</category><category>orchestration</category><author>Arbiter</author></item><item><title>Provider-agnostic orchestration: why we don&apos;t lock you in</title><link>https://blog.arbitermcp.com/provider-agnostic-orchestration/</link><guid isPermaLink="true">https://blog.arbitermcp.com/provider-agnostic-orchestration/</guid><description>Why an orchestration layer should stay neutral about the models, clients, and accounts you bring to it.</description><pubDate>Mon, 08 Jun 2026 00:00:00 GMT</pubDate><category>orchestration</category><category>positioning</category><author>Arbiter</author></item><item><title>Introducing Arbiter: the orchestration layer your AI stack is missing</title><link>https://blog.arbitermcp.com/introducing-arbiter/</link><guid isPermaLink="true">https://blog.arbitermcp.com/introducing-arbiter/</guid><description>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.</description><pubDate>Tue, 02 Jun 2026 00:00:00 GMT</pubDate><category>announcement</category><author>Arbiter</author></item></channel></rss>