Multi-agent orchestration using dmux (tmux pane manager for AI agents). Patterns for parallel agent workflows across Claude Code, Codex, OpenCode, and other harnesses. Use when running multiple agent sessions in parallel or coordinating multi-agent development workflows.

dmux Workflows Orchestrate parallel AI agent sessions using dmux, a tmux pane manager for agent harnesses. When to Activate Running multiple agent sessions in parallel Coordinating work across Claude Code, Codex, and other harnesses Complex tasks that benefit from divide and conquer parallelism User says "run in parallel", "split this work", "use dmux", or "multi agent" What is dmux dmux is a tmux based orchestration tool that manages AI agent panes: Press n to create a new pane with a prompt Press m to merge pane output back to the main session Supports: Claude Code, Codex, OpenCode, Cline, Gemini, Qwen Install: Install dmux from its repository after reviewing the package. See [github.com/standardagents/dmux](https://github.com/standardagents/dmux) Quick Start Workflow Patterns Pattern 1: Research + Implement Split research and implementation into parallel tracks: Pattern 2: Multi File Feature Parallelize work across independent files: Pattern 3: Test + Fix Loop Run tests in one pane, fix in another: Pattern 4: Cross Harness Use different AI tools for different tasks: Pattern 5: Code Review Pipeline Parallel review perspectives: Best Practices 1. Independent tasks only. Don't parallelize tasks that depend on each other's output. 2. Clear boundaries. Each pane should work on distinct files or concerns. 3. Merge strategically. Review pane output before merging to avoid conflicts. 4. Use git worktrees. For file conflict prone work, use separate worktrees per pane. 5. Resource awareness. Each pane uses API tokens — keep total panes under 5 6. Git Worktree Integration For tasks that touch overlapping files: Complementary Tools Tool What It Does When to Use dmux tmux pane management for agents Parallel agent sessions Superset Terminal IDE for 10+ parallel agents Large scale orchestration Claude Code Task tool In process subagent spawning Programmatic parallelism within a session Codex multi agent Built in agent roles Codex specific parallel work ECC Helper ECC now includes a helper for external tmux pane orchestration with separate git worktrees: Example plan.json : The helper: Creates one branch backed git worktree per worker Optionally overlays selected seedPaths from the main checkout into each worker worktree Writes per worker task.md , handoff.md , and status.md files under .orchestration/<session / Starts a tmux session with one pane per worker Launches each worker command in its own pane Leaves the main pane free for the orchestrator Use seedPaths when workers need access to dirty or untracked local files that are not yet part of HEAD , such as local orchestration scripts, draft plans, or docs: Troubleshooting Pane not responding: Switch to the pane directly or inspect it with tmux capture pane pt <session :0.<pane index . Merge conflicts: Use git worktrees to isolate file changes per pane. High token usage: Reduce number of parallel panes. Each pane is a full agent session. tmux not found: Install with brew install tmux (macOS) or apt install tmux (Linux).

dmux-workflows