dmux gives every coding agent its own git worktree, and ships its npm metadata pointing at a different repository
A dev agent multiplexer for git worktrees and coding agents.
At a glance
- What is it?
- standardagents/dmux is a tmux pane manager that pairs each pane with a git worktree and a branch so several coding agents can run in parallel. The mechanism is well built and the boundaries are clearly stated. The package metadata is the weak point: the clone URL points at standardagents/dmux while the homepage field, the bugs field and the README's own Issues link all point at formkit/dmux.
- Who is it for?
- dmux earns its place if you already run agents in parallel and keep losing work to shared working copies, because worktree isolation plus a durable pane that resumes a tracked conversation is the feature everything else hangs off. Three things to know before you install it.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 91 days ago.
- What is it written in?
- Mainly HTML, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- standardagents/dmux1,819 ★ · +50
| Repository | 2026-09-11 | 2026-11-15 |
|---|---|---|
| standardagents/dmux | 1.8k | 1.8k |
50 Stars in the last 65 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The clone URL and the issues URL point at different repositories
The package manifest disagrees with itself about where this project lives. The repository field points at git+https://github.com/standardagents/dmux.git, which matches the account that owns the tree. The homepage field points at https://github.com/formkit/dmux#readme and the bugs field points at https://github.com/formkit/dmux/issues. The README does not leave the ambiguity open either way: its Issues badge is also a link to formkit/dmux.
The practical effect lands on the first person who has a problem. Someone who ran npm install -g dmux and then followed the bugs field, or clicked the Issues badge in the README, arrives at a repository that is not the one the command installed. Meanwhile the README's Documentation and Getting Started links point somewhere else entirely, at the dmux.ai site, so the manifest also carries two different ideas of what a homepage is: a GitHub readme anchor and a separate documentation site.
Nothing here stops the tool working. The published tarball is name dmux regardless, and the CLI is invoked as dmux. But for a project that names an issues URL as its support channel, having that URL and the clone URL point at different accounts is the first thing a maintainer should reconcile.
HTML is the primary language of a tool that ships compiled JavaScript
The repository's language statistics report HTML, which is odd for a terminal multiplexer written in TypeScript and published as a Node package. The manifest explains the shape of the source: main is ./dist/index.js, the exported types come from ./dist/index.d.ts, and the build script runs a documentation generator, then a frontend build, then tsc. The workspace is a pnpm workspace with a filtered frontend package and a filtered docs package, and the tree carries tsconfig.json, vitest.config.ts and a __tests__/ directory.
So the picture is a TypeScript codebase whose compiled output is JavaScript, with a browser frontend of its own sitting beside it, and the frontend is what tips the byte count toward HTML. The install path itself is short. A global package install:
npm install -g dmuxand then the tool is launched from inside a project directory:
cd /path/to/your/project
dmuxThe requirements line up with that build rather than with the language statistic: tmux 3.0+, Node.js 18+, and Git 2.20+. The engines field repeats the Node floor as >=18.0.0, which is the only version constraint stated anywhere in the manifest. At least one supported agent CLI is required as well, and a working repository to put worktrees in. That last point is why dmux is a project tool and not a general tmux theme: it is not useful anywhere the worktree and branch pair has no meaning.
Coverage output, a tile cache and agent state share the repository root
The tree holds several directories that are working state rather than source. coverage/ is test coverage output. arnis-tile-cache/ is a cache directory whose name suggests image tiles. .playwright-mcp/, .claude/, .codex/ and .dmux-hooks/ are tool-specific state, three of them belonging to the coding agents this project integrates with, plus its own hooks directory. Alongside them sit six media files committed at the root: dmux.gif, dmux.mp4, dmux.png, dmux.svg, dmux.webp and screen.gif.
That mix has a consequence for the clean script, which removes dist, a generated module under src/utils, and a prebuilt macOS application. It tidies the build but not the working state, so a checkout can carry coverage from a previous test run and a populated cache that has nothing to do with the code. The hook directory is a different case and belongs there on purpose: dmux installs its own lifecycle hooks into the local profile, and the repository carries the templates those hooks are generated from.
The root media files are the other half of the story. dmux is a terminal tool whose README leans on screenshots and recordings to show what a pane layout looks like, and six of them sit in version control at the top level rather than in a docs directory.
The agent list is generated, not maintained by hand
Three scripts in the manifest explain how much of this repository is produced rather than written. The build runs generate:hooks-docs, which calls node scripts/generate-hooks-docs.js, before it builds the frontend and compiles the sources. The clean script deletes src/utils/generated-agents-doc.ts, a generated module that lives inside the source tree rather than in a build directory. And hooks:install-local runs bash scripts/install-local-hooks.sh, with dev:bootstrap chaining the generator and the hook installer together.
The effect on a contributor is specific. Building without the generator step produces a package missing a module the compiler expects, and the fix is to run the bootstrap rather than to write the file by hand, which the clean script would delete anyway. The same division shapes the agent list itself: eleven agent CLIs are named as supported, from Claude Code and Codex through Cline, Gemini, Qwen, Amp, pi, Cursor, Copilot and Crush, and the generated agents document is what keeps that list and the hooks that wrap it in step with the code.
This is a sensible arrangement for a project that tracks a dozen external binaries, since nobody has to remember to update prose when a new CLI is added. It also means the README is one of the few places the agent list appears without being generated.
A prebuilt macOS application ships inside the npm package
The published file list is short: dist, native, the dmux launcher, the README and the licence. Because the whole native directory is included, whatever lives there goes out with every install, including a prebuilt macOS helper application at native/macos/prebuilt/dmux-helper.app. The clean script names that path explicitly, which tells you it is a build product rather than checked-in source, and build:macos-helper runs node scripts/build-macos-helper-bundle.js to produce the bundle.
That is how the macOS notifications feature is delivered. Background panes can send native attention alerts when they settle and need attention, with a global off switch, and an alert that has to cross into the desktop is exactly the kind of thing a Node process will not do on its own, so it goes through a helper application instead.
The cost is that a package whose requirements read as tmux, Node and Git on any platform also carries a platform-shaped binary, and the manifest states no per-platform condition for it. Anyone installing on a machine that is not macOS gets those bytes anyway, and anyone on macOS should know the notification path has its own component to build and to clean.
A pane is either a worktree or a plain terminal, and the keys overlap
Pressing n creates a pane with a worktree and an agent; pressing t creates a terminal pane with no worktree. When you create a pane you type a prompt and then pick one or more agents, or none, and dmux handles the worktree, the branch and the agent launch. So the same object is either an isolated copy with an agent in it or a bare shell, and the pane menu and the visibility keys apply to both without saying which you have.
That overlap is where the two destructive-adjacent keys differ. x closes a pane and h only hides it, with H hiding every other pane in the session. Hiding is reversible and nothing stops working, which is why the feature list pairs it with the ability to isolate one project or restore everything later. Closing is the one that ends a worktree.
The durability claim is narrower than it first looks. Regular terminals restore in their last observed directory, and if Codex, Claude or another supported agent was running, dmux tracks it and resumes that conversation when the pane is recreated. Tracked means tracked, so the conversation resume applies to the agents dmux recognises rather than to every terminal that ever held something.
Branch names are automatic unless you make them explicit
There are three ways to get a branch, and the tool supports all three at once. The default flow picks the worktree and branch names itself, which is the fast path. You can instead choose a different base branch per pane, which is what you want when a task belongs on something other than the tip of main. Or you can supply an explicit branch and worktree name, which the documentation points at issue-tracker ticket naming.
Explicit naming interacts with multi-agent launches in one specific way: when you start several agents in a pane, they still share a naming scheme and get agent-specific suffixes rather than competing for one name. So the ticket number you typed survives, and the agent that owns it stays legible in the branch list.
Finishing the work is the mirror image. Opening the pane menu with m offers Merge to bring the branch back into your main branch, or Create GitHub PR to push the branch and file a pull request. Smart merging is the automatic version: auto-commit, merge and clean up in one step. Lifecycle hooks fire around the same territory, on worktree create, pre-merge and post-merge, so a team can put checks on both paths without touching either one.
Editorial conclusion
dmux earns its place if you already run agents in parallel and keep losing work to shared working copies, because worktree isolation plus a durable pane that resumes a tracked conversation is the feature everything else hangs off. Three things to know before you install it. The npm metadata points at formkit/dmux for issues and homepage while the clone URL points at standardagents/dmux, so check which repository you are filing against. The AI features are optional by design, since the inference provider is only used for naming, summaries and pane analysis, so you can use it with no provider at all. And the agent inventory is generated at build time rather than hand-maintained, which is why a contributor runs the bootstrap step before building instead of after.
Frequently asked questions
How do I install dmux and get it running?
Install it globally with npm install -g dmux, then run dmux inside a project directory. Press n to create a pane, type your prompt, and pick one or more agents, or none if you want a plain terminal, and dmux creates the worktree, the branch and the agent launch.
What does dmux need on the machine before it will run?
tmux 3.0 or newer, Node.js 18 or newer as the manifest requires, Git 2.20 or newer, and at least one supported agent CLI. An inference provider is optional and is only used for AI naming, summaries and pane analysis.
Which coding agents does dmux support?
Claude Code, Codex, OpenCode, Cline CLI, Gemini CLI, Qwen CLI, Amp CLI, pi CLI, Cursor CLI, Copilot CLI and Crush CLI. That list of eleven is generated at build time rather than hand-maintained, through a documentation generator that writes a module under src/utils.
Which inference providers can dmux use?
API-key providers, custom OpenAI-compatible endpoints, a Codex CLI login backed by your ChatGPT subscription, or a Grok Build CLI login backed by a SpaceXAI subscription. A primary provider and model plus an optional backup are configured on first run, and the flow reopens with s and then Inference Providers.
How do I finish a pane's work in dmux?
Press m to open the pane menu and choose Merge to bring the branch back into your main branch, or Create GitHub PR to push the branch and file a pull request. Smart merging does the auto-commit, the merge and the cleanup in one step, and lifecycle hooks can fire on worktree create, pre-merge and post-merge.
Which repository should I file a dmux issue against?
The manifest and the README point at two different answers. The repository field points at standardagents/dmux, while the homepage field, the bugs field and the README's Issues badge all point at formkit/dmux, so the URL the tool shows you decides where the report lands.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/standardagents-dmux)Star history chart for your README
[](https://hysenlabs.com/projects/standardagents-dmux)Was this useful?