We're open sourcing dmux. Our internal tool for running Codex and Claude Code swarms. - tmux + worktrees + claude/codex/opencode - hooks for worktree automation - a/b claude vs codex - manage worktrees - multi-project per session ...more. ➡️

One of my favorite features is to create a "coordinator". Just create a parent directory/repo that has lots of related projects under it. They are all excluded via .gitignore from the parent and each have their own git repo. These are not git submodules (🤮) Just simple directories, I generally have a root AGENTS/CLAUDE file to describe the structure. Dmux will detect these sub-repositories and when you create a worktree in the root, will also create worktrees of all those sub-directories in the parent directory worktree. When you merge it will let you merge each of the children's worktrees. For OSS maintainers like myself, with many related projects, this is a real game changer.

Something even more exciting is coming very soon...if you want early access for that bombshell join the waitlist here:

tmux + worktrees + claude code is basically how everyone should be running agents. open sourcing this is huge

This is sick, thanks for open sourcing!

deeznux

I’ve got a pair of agents

running claude vs codex head to head in tmux... who's winning so far?

Codex on everything except ui

@xMikeMickelson I noticed something similar as well in my experiments. Claude wins for product engineering, devops, sysadmin. Codex wins at all other engineering work.

@xMikeMickelson Interesting. I have codex above CC on devops right now, but I’ll have to do another a/b

Very interesting. I think everyone that uses tmux started feeling the same itch. I’ve built a much simpler version of this for myself:

lol I've been doing this manually, sick!

have been doing this manually w scripts thanks for this

running a claude vs codex thunderdome in a tmux session is genuinely the most chaotic good thing i've seen this week. downloading immediately

everyone's bookmarking this for the swarm management but the a/b testing is the sleeper feature. once you're running claude and codex on the same task in parallel, you're not just building faster. you're building a local eval suite for every model update. that data compounds.

why are you open sourcing this

add pi-coding-agent and im sold

you had me at tmux

This is so rad, trying immediately.

If you want to discuss, you can join the discord server here:

the a/b claude vs codex feature is interesting. running both on the same task and comparing output is something i do manually all the time, good to see it getting tooling around it

Running multiple agents in parallel is where you lose track of what each one called and with what scope. Tool call visibility at the orchestration layer matters as much as the task output.

That’s why ai names ours automatically

Legendary! I am literally listening to live stream of @mastra discussing their methods.

tmux + worktrees is the setup nobody talks about but everyone needs

This looks very useful

Claude just dropped built-in worktrees

Ok

> a/b claude vs codex sold! I've been doing this manually, just having both run at the same time in separate folders. Codex is destroying Claude so far!

Looks pretty amazing! Can the agents communicate interactively with one another while working in parallel?

This doesnt add any extra layers to the existing coding agents because each already has their own capacity for inter-agent and sub-agent communication.

for example, it would be cool if i could say to one agent, lets say codex, to go off and do a task, and delegate some UI tasks to Claude, and have them communicating back and forth on the UI aspect, returning a polished UI, then allowing codex to spin up agents or whatever from there. I do this through non interactive (print) mode now, but I've always wondered how this could look interactively.

This is pretty much how I use it, but the communication between them is just a merge.

Fair enough. Well it is open source so I suppose if I want more, i can just stfu and build it right? 😅 this is awesome brother. well done!

Going to play with this tomorrow 🔥

Gotta give this a try, my workflow is similar except I manually manage the tmux's.

sick

Super nice website and docs!

i guess we're building the same product

single core → multi core baby

Been writing my own harness too. I just queue tasks and it keeps on building!

Wow this looks crazy similar to my @taskyoudev - excited to try it out

Have been looking for a tmux alternative will try it out thanks!!!

@theo have you taken a look at this?

🤯