Orchestrator Mode: Fire-and-Forget Codex Workers
Ask MadoAgent to hand a self-contained task to a headless Codex worker — no terminal tile to babysit, with reliable completion detection and sandboxed by default.
Today we're shipping Orchestrator Mode: MadoAgent can dispatch a self-contained task to a headless Codex worker without opening an interactive terminal tile for you to babysit. Instead of pattern-matching a screen to guess when the worker finished, MadoHub gets a definitive done signal — so you can hand off "go refactor this module and tell me when you're done" and trust the result.
What you can do now
- Dispatch a self-contained task to a Codex worker — a refactor, a test pass, a migration — without opening a terminal you have to watch.
- Get a reliable done signal — completion is reported definitively, not guessed from terminal output, so fire-and-forget actually means forget.
- Stay sandboxed by default — every dispatched worker runs inside your project directory and can't reach outside it unless you deliberately loosen the sandbox.
- Spot a worker at a glance — dispatched tiles carry a Worker badge in the title bar so you can tell a headless dispatch apart from a terminal you opened yourself.
How to try it
- Press Cmd+Shift+M to open MadoAgent.
- Ask it to dispatch a Codex worker for a self-contained task — for example, "dispatch a Codex worker to refactor the cache module and report back."
- MadoAgent spawns a headless worker tile (badged Worker) and runs the task under the default sandbox.
- Watch the tile for the done signal, or get back to other work and check the result when it's finished.
Sandbox modes
Every dispatched worker runs under one of three Codex sandbox modes:
| Mode | Behavior |
|---|---|
| read-only | Can read files, can't modify anything or run side-effecting commands. |
| workspace-write | Can read and write inside the working directory. This is the default. |
| danger-full-access | No sandbox restrictions. MadoAgent never picks this on its own — you have to choose it explicitly. |
The default workspace-write mode means a worker dispatched from MadoAgent can't reach outside your project directory unless you deliberately loosen it.
Why it matters / use case
Some tasks are conversations — you want to go back and forth with an agent in a terminal. Others are errands: "refactor this file, run the tests, tell me when it's done." For errands, an interactive terminal you have to monitor is the wrong shape. Orchestrator Mode gives those tasks to a worker that finishes on its own and reports back reliably, so you can keep your attention on the conversations that actually need it.
Related docs
What's next / limitations
Orchestrator Mode currently dispatches Codex workers. The Worker badge survives a reload so you won't lose track of a dispatched tile across restarts. For interactive work where you want to steer the agent turn by turn, use a regular agent tile instead.