Main
Use worktree isolation to prevent agent conflicts: each pane is a full working copy with its own branch as described in README.
Adopt the built-in merge/PR flow: finish a task, then merge back or open a PR from the pane menu (README documents shortcuts).
Keep it lightweight: start with plain terminal panes, then progressively enable agent CLIs once your team’s auth and policies are set.
Source-backed notes
- README says each pane gets its own git worktree + branch so multiple agents can run in parallel safely.
- README lists supported agents including Claude Code, Codex, OpenCode, Cline CLI, Gemini CLI, Cursor CLI, and Copilot CLI.
- README documents install via
npm install -g dmuxand a quick start withdmuxinside a repo.
FAQ
- Do I need an agent CLI to use dmux?: No — README says you can create plain terminal panes; agents are optional.
- What are the minimum requirements?: README lists tmux 3.0+, Git 2.20+, and Node.js 18+.
- How does it avoid merge conflicts?: By isolating work per pane into separate worktrees/branches, as described in README.