All orchestrators

dmux

A tmux pane and worktree for every task.

Visit website
Official product image · supplied by the project

Terminal tool that gives each task a tmux pane with its own worktree and agent, then merges the branch or opens a PR when the work is done.

GOOD FIT FOR

Running CLI agents in parallel tmux panes, then merging the branch or opening a PR.

Core features

  • Sandboxed runsNo

    README, docs site source and src/ were searched for sandbox, docker, container and VM. Agents run in plain tmux panes on the host and nothing sets up isolation beyond worktrees.

  • Diff review YesSource
  • Agent coordinationNo

    README, docs site source and src/ were searched for orchestrate, delegate, handoff and subagent. A/B pairs send one prompt to two separate panes and attached agents only share a worktree. No agent can start, message or hand work to another through dmux.

  • Scheduled tasksNo

    README, docs site source and src/ were searched for cron, schedule and recurring. Panes are only started by a person in the TUI.

  • Event triggersNo

    README, docs site source and src/ were searched for webhook, issue and pull request triggers. Hooks only run scripts on dmux's own lifecycle events such as worktree creation and merge.

  • Team collaborationNo

    README, docs site source and src/ were searched for team, share and multi-user. The only team feature is a repo-committed defaults file, .dmux.defaults.json. Sessions are local tmux sessions.

  • API / CLI controlNo

    The dmux command only opens the TUI. The repo's context/API.md describes an HTTP API, but the current code has no such server, so that file looks stale. The site docs list no command or API for starting panes.

Pricing

Free open source under MIT. No paid tier found.

Platforms

Terminal app inside tmux 3.0+, Node.js 18+, Git 2.20+. Native attention alerts on macOS. Supported OS list not stated in the README.

Research notes

dmux has two separate parts. Agent panes launch the installed CLIs, which is what use_codex_sub and use_claude_sub record. A separate inference provider powers only AI naming, summaries and pane analysis. The README's 'a Codex login backed by your ChatGPT subscription' and the CodexAppServerClient bridge belong to that inference provider, as does all the BYOK evidence (API keys, OpenAI-compatible endpoints). So byok=yes covers dmux's helper inference, not the agents; agent panes use each CLI's own auth. Codex own_subscription=yes rests on dmux reusing the Codex login and included plan usage for that inference, so a ChatGPT plan is demonstrably usable through the same CLI login; no doc states it for agent panes directly. Integration for agents is terminal-pty, not app-server. The repo is standardagents/dmux and formkit/dmux redirects to it, but the README still links formkit/dmux issues, the site footer says FormKit, Inc., and the LICENSE names Justin Schroeder. Status is a judgment call: nothing has been pushed since the v5.11.1 release on 2026-08-16, about 11 weeks, after roughly monthly releases. Those last releases added features rather than only fixes, so it stays active for now; recheck. dmux.ai is JS-rendered with almost no static text, so README evidence is used.

Still unknown

Own Claude plan. Full repo searched on 2026-11-05: dmux launches the claude CLI, but no doc or code addresses Claude plans or logins, and its own Anthropic inference option is API-key only (ANTHROPIC_API_KEY).

Agents & providers

Codex Claude Code OpenCode Cline CLI Gemini CLI Qwen CLI Amp CLI pi CLI Cursor CLI Copilot CLI Crush CLI