Multi-Agent Orchestrator

An Atrium workflow that opens a structured multi-agent workspace when a root Codex or Claude session starts. It keeps a decision agent, supporting roles, and a live task canvas coordinated through local state files.

What it does

• Creates one active orchestration run per Atrium workspace.
• Opens a persistent Canvas beside the root session.
• Launches a decision agent plus scout, builder, tester, reviewer, safety, evidence, and recovery roles only after Atrium confirms a dedicated wing exists and each role room has moved into it.
• Updates the Canvas from local role events immediately and refreshes its heartbeat every five seconds.
• Uses a root/child guard so launched role sessions do not recursively start additional runs.

No task content leaves the machine. The workflow does not push code, deploy, alter credentials, or make production data changes.

Install

Requirements: macOS, Python 3.10+, Atrium CLI, and at least one installed Codex or Claude adapter.

git clone https://github.com/Phat-Po/multi-agent-orchestrator.git
cd multi-agent-orchestrator
python3 scripts/install.py

The installer backs up an existing Claude-only task-dashboard skill before replacing it with a shared Codex/Claude copy. It adds, without replacing, one SessionStart and one SessionEnd entry in each supported hook configuration.

Start a new Atrium session. The root session opens the Canvas and roles wait for the first task. Workers report lifecycle events with:

python3 ~/.multi-agent-orchestrator/scripts/progress.py --role scout --state working --detail "Reading the task"

Privacy

The public repository excludes all local runs, logs, configuration, credentials, and Atrium data. Local runtime state is stored under ~/.multi-agent-orchestrator/ and is never read by Git.

Limits

• A workspace has one active root run at a time; a later session attaches until the root ends.
• If Atrium cannot persist the dedicated wing, the run aborts before launching roles instead of placing them in the main wing.
• Roles start in wait mode. They must still respect project governance and approval gates.
• Atrium must be running for wing and Canvas mutations.

License

MIT. See LICENSE.