We wrote this about our own competitors, so read it with that in mind. See something wrong? Want to add another tool? Let us know — every claim on this page is in one file you can edit.
vs cmux
We think you should be using either Dormouse or cmux, because:
- Running coding agents from a terminal beats running them from a GUI:
- you have more power to coordinate multi-agent flows, and
- you are less exposed to vendor lock-in.
- Browsers multiplexed next to your terminals are a huge unlock for watching agents and giving them feedback.
Some reasons you might prefer cmux:
- Its terminal is native Zig (Ghostty's), while Dormouse's is xterm.js, the one inside VS Code.
- Its browser is a private fork of Chromium (it used to be WebKit), which feels native and has an API agents can drive. Dormouse drives unmodified Playwright or agent-browser, which feels native to your agents but can lag slightly for you. You can open the system browser for no lag, but then Dormouse's layout does not manage it.
- It makes orchestrating a fleet of remote SSH boxes easy. Dormouse has not built that yet; it assumes most of your work happens on one or two machines.
Some reasons you might prefer Dormouse:
- It drives real, unmodified Playwright or agent-browser rather than a private browser fork.
- If you like VS Code (or one of its forks), Dormouse and all of its browser features run there.
- If you prefer lightweight standalone apps, the Dormouse download is about 60MB against about 320MB for cmux.
- You can try Dormouse in your browser without installing anything.
- Its alerts track your attention: which panes you have interacted with, so it only dings for something you have not seen. Walk across the room to stretch and it speaks aloud; go for a walk and it can push a notification to your phone.
vs Claude & Codex Desktop
Claude Desktop and the Codex app wrap one vendor's agent in a polished GUI. Dormouse runs the same agents' CLIs, Claude Code and Codex, in a terminal:
- A terminal coordinates multi-agent flows a chat window cannot, and any CLI agent can join.
- Your workflow is not tied to one vendor's app.
Some reasons you might prefer a desktop app:
- Nothing to set up: sign in and start.
- Built-in diff review, worktrees, and cloud tasks, designed around that one agent.
- You never have to touch a terminal.
Some reasons you might prefer Dormouse:
- Claude Code, Codex, and any other CLI agent run side by side in one layout.
- One alert model across all of them, which knows what you have already seen.
- Browser panes your agents drive, next to the terminals they run in.
- It runs inside VS Code, and on Linux.
vs herdr
herdr and Dormouse agree that coding agents belong in real terminal panes, with a multiplexer that knows which agents need you.
Some reasons you might prefer herdr:
- It runs inside the terminal you already use — Ghostty, kitty, WezTerm, even tmux — and over SSH.
- Its background server keeps agents running when your client disconnects.
- It is keyboard-first, for people who never want to reach for the mouse.
Some reasons you might prefer Dormouse:
- Mouse-friendly: split, drag, select, and copy as you would in any app.
- Browser panes next to your terminals, which your agents can drive.
- It runs inside VS Code, and on your phone.
vs tmux & zellij
Dormouse borrows tmux's model — panes, splits, and its keybinds — and adds the mouse, browsers, and agent alerts.
Some reasons you might prefer tmux or zellij:
- They run anywhere a shell does, including over SSH, and sessions survive a disconnect.
- Years of plugins, configuration, and muscle memory.
- No GUI at all.
Some reasons you might prefer Dormouse:
- Keep your tmux keybinds and use the mouse as well.
- Alerts when an agent in any pane needs you.
- Browser panes in the same layout as your terminals.
- You can still run tmux inside a Dormouse pane.
Table
| Dormouse Terminal for VS Code and desktop | cmux Native macOS terminal | herdr Multiplexer inside your terminal | Claude Desktop Anthropic's desktop app | Codex app OpenAI's desktop app | |
|---|---|---|---|---|---|
| Where it runs | |||||
| macOS | Yes | Yes | Yes | Yes | Yes |
| Windows | Yes | No | Partly Preview | Yes | Yes |
| Linux | Yes | No | Yes | No | No |
| Inside VS Code | Yes | No | Partly In the integrated terminal | No Separate extension | No Separate extension |
| Source available | Yes FSL, MIT after two years | Yes GPL-3.0 | Yes AGPL-3.0 | No | No |
| Terminals | |||||
| Runs any CLI agent, unmodified | Yes | Yes | Yes | No Claude only | No Codex only |
| Tiled panes | Yes | Yes | Yes | No | No |
| Mouse-first selection and copy | Yes | Partly | Partly | Unknown | Unknown |
| Sessions survive a restart | Yes | Yes | Yes Background server | Partly | Partly |
| A CLI the agent can script | Yes dor | Yes | Yes | No | No |
| Alerts | |||||
| Alerts when an agent needs you | Yes Zero configuration | Yes | Yes | Yes | Yes |
| Spoken alerts | Yes Opt-in; system voice is free | Unknown | Unknown | Unknown | Unknown |
| Push notifications | Yes To your phone, through Pocket | Partly Desktop only | Unknown | Unknown | Unknown |
| Tracks your attention to minimize interruptions | Yes Only alerts for what you haven't seen | Unknown | Unknown | Unknown | Unknown |
| Browsers | |||||
| Browser panes beside your terminals | Yes | Yes | No | No Uses your Chrome | Partly In-app browser |
| An agent can drive them | Yes | Yes | No | Partly Through Chrome | Yes |
| Unmodified browser automation | Yes Playwright, agent-browser | No Private Chromium fork | No | Partly Chrome extension | Unknown |
| Feels native, no lag | Partly Slight lag; the system browser has none | Yes | No | Yes Your own Chrome | Unknown |
| Remote | |||||
| Drive it from your phone | Yes Pocket | Unknown | Partly Over SSH | Partly | Partly Cloud tasks |
| Self-hostable relay | Yes | No | No | No | No |
| Price | |||||
| Free to use | Yes Hosted is paid | Yes | Yes | Partly Needs a Claude plan | Partly Needs a ChatGPT plan |
- Yes
- Partly
- No
- Unknown