dmux-workflows

Install dmux with npm install -g dmux, start a session by running dmux, then press n to create a new pane and type a prompt for each agent. Press m to merge a pane's output back into the main session when it finishes.

Parallelize only independent tasks with clear boundaries, such as separate files, research versus implementation, or distinct review perspectives. Avoid splitting tasks that depend on each other's output, and keep total panes under five or six to control token usage.

dmux supports Claude Code, Codex, OpenCode, Cline, Gemini, and Qwen. Each pane runs its own full agent session, so you can mix harnesses in a cross-harness workflow for different task types.

Use git worktrees to isolate file changes per pane by running git worktree add for each branch, then launch agents inside their own worktree directories. Merge the branches together after all panes complete their work.

A pane may be waiting for input from its agent session rather than being stuck. Use the m key to read the pane's output and check its state before assuming it has failed.

Each pane consumes API tokens as a full agent session, so costs scale with pane count. Parallelism also fails for dependent tasks, and overlapping file edits cause merge conflicts unless worktrees are used.