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.
You kick off a long piece of work with a coding agent, step away, and then think of the one more thing it should do. The usual options are bad: start a fresh session that knows none of the context you just built, or get back to the machine and type into the window. Arbiter gives you a third one. From a chat message, you can hand more work to a session that is already running.
Into the session it already has
The follow-up goes to the existing session, not a new one, so everything that session already understands about the task stays intact. It runs headless, with no window to open and nothing to sit in front of, and the reply comes back to you tracked, so you can see what happened from wherever you sent it. You add to the work in flight instead of restarting it.
Claude and Codex, both first-class
This works the same way whether the session is Claude or Codex. Codex is a first-class citizen alongside Claude, tracked and driven through the same path, so you pick the right agent for the job and reach either one identically. Nothing about the follow-up changes when you switch.
On the accounts you already pay for
The follow-ups run against your existing subscriptions, not a metered API key you have to babysit, which is the reliable path when you are working from a phone and can’t be nursing rate limits. And because a follow-up can act, it goes through the same approval gate as any other remote action, so handing a running agent more work is something you authorize, not something that just happens.
Why it matters
The promise of an orchestration layer is that your work does not live in one terminal window you have to guard. Being able to top up a running session from a message, on either major agent, on the plan you already have, is a concrete piece of that. The operation follows you, instead of you having to sit with it.
Arbiter is in active development, the command layer for Code Reality Labs. It runs Warden across providers and brings work back when a machine or an account gives out. Follow the RSS feed for more.