cmux-orchestration

Multi-agent orchestration coordinates terminal workers across cmux panes to delegate bounded tasks, monitor status, and consolidate results. A controller agent launches Claude Opus and Codex GPT-5.5 TUIs, tracks their state, and verifies reported changes.

Yes, cmux manages Claude Opus and Codex GPT-5.5 workers simultaneously by applying explicit workspace, pane, and surface targeting. It enforces strict worker state tracking and non-disruptive focus rules to prevent terminal conflicts.

Evidence-based verification requires workers to report cited files, commands, and diffs. The controller agent validates these reported changes and failures before accepting and integrating the results into the local development workflow.

You delegate bounded refactoring tasks by using a controller agent to launch, direct, and monitor terminal workers in cmux. The controller surfaces workers, assigns bounded scopes, collects evidence, and consolidates the verified results.

Yes, explicit workspace, pane, and surface targeting is required. This strict targeting keeps actions inside the caller workspace and enforces non-disruptive focus rules to avoid unwanted terminal focus changes during agent execution.

You should avoid cmux orchestration for unbounded or loosely defined tasks, as the protocol requires strict worker state tracking and bounded task delegation. The controller needs specific scopes to properly launch, monitor, and verify workers.