dmux CLI
dmux is a terminal agent manager for tasks across repositories in one session, keeping hidden panes running in the background.
- 1,816 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The CLI launches agents and hooks, creates worktrees and can commit, merge and push selected branches.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/dmuxDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The CLI launches agents and hooks, creates worktrees and can commit, merge and push selected branches.
This is third-party code. Review the repository files before installing.
What it does
dmux is a CLI tool that creates a terminal pane, branch and Git worktree for each task. Users select installed agents and inspect files or diffs through the shared interface. When work is ready, a menu offers merging or GitHub pull-request creation. Multiple repositories and hidden-but-running panes are supported. Optional inference helps with naming and summaries; selected agent CLIs perform the coding.
Who it is for. Technical leads running parallel coding agents and reviewing their changes in separate branches.
Good fit when
- A lead assigns independent tasks to agents in separate worktrees.
- A developer reviews branches and integrates results through the terminal menu.
- The team maintains several repositories in one long session.
- After recreating a pane, a user resumes the earlier agent conversation.
Not a fit when
- You need OS-level filesystem and network isolation.
- The chosen agent CLIs are not installed.
- You expect separate branches to eliminate semantic merge conflicts automatically.
Example request
Prepare separate dmux tasks for docs and tests. Merge only after both branches are reviewed.Limitations
Execution requires tmux 3.0, Node.js 18 and Git 2.20 or later, plus the chosen agent CLIs. Worktrees separate Git changes while processes retain access to shared files and networks under their own permissions. Automatic naming and pane analysis use a separately configured provider or supported login. Merging can create a commit and remove the worktree. Review the diff and retain any work still needed outside the merged branch first.
How to disable. Stop agent processes and close panes. Inspect uncommitted work before removing worktrees; hiding a pane does not stop it.
FAQ
How do I create a task?
Press `n`, enter the task and select an agent. dmux creates a pane, branch and worktree for that task.
Can I open a plain terminal?
Yes. Create a pane without an agent for manual inspection.
Does hiding a pane stop it?
No. Stop its process explicitly when needed.
Can I choose a base branch?
Yes. When creating a task, override its base branch and worktree name. These determine where the agent starts and how its checkout is named.
How do I review task changes?
Use the pane file browser or task menu and inspect the diff before merging.
Discussion
No questions or reviews yet.
Related
CLI toolsA tmux-based TUI that runs Claude Code, Codex and other agents in one list: status, quick prompts, worktrees and diff review
A local control panel for coding agents: it runs Claude Code and Codex, keeps a task queue and merges verified work into main.
ccmux tracks every coding agent in tmux: who is working, who waits for you, worktree spawning and answer hand-off.
A Rust terminal task board: every task runs in its own git worktree and tmux window while Claude Code, Codex, Gemini CLI and other agents work in parallel
A CLI and terminal app that show which coding agents in your tmux sessions are working, waiting on you or done
A tuned tmux setup and the tmux-bridge CLI that lets agents read neighbouring panes, type into them and hand each other tasks.
README in short
Lifecycle hooks run configured scripts when worktrees are created or merged. Background-pane notifications can be disabled on macOS.