wmux · comparison
wmux vs Orca
Choose wmux if you want to pick individual hunks across several agents' diffs, hand jobs to bots in chat that start workers on their own branches, have agents talk in shared channels, or be asked before one agent launches another with permissions bypassed.
Choose Orca if you need Linux, an Android app, SSH or remote workspaces, or the widest roster of preconfigured agents.
Orca (onorca.dev) is one of the strongest projects in this category — an MIT-licensed agent development environment for Windows, macOS and Linux, with iOS and Android companion apps, 30+ preconfigured CLI agents, and near-daily releases (v1.4.229 shipped on October 17, 2026). If you are evaluating it, you should also know exactly where wmux differs, including the places Orca is ahead.
The short version: on the fundamentals the two now match — both run agents as real terminal sessions owned by a background daemon, give each task its own git worktree, and ship a browser agents can drive. The differences are in what happens around the agents: wmux lets you harvest individual hunks across task diffs, gives agents Slack-style channels and bots you direct from chat, and asks you before one agent launches another with permissions bypassed; Orca goes wider on platforms, devices, remote machines and integrations.
| wmux | Orca | |
|---|---|---|
| Open source (MIT) | ✓ | ✓ |
| Windows & macOS | ✓ | ✓ |
| Linux desktop app | ✕ | ✓ |
| Parallel agents in git worktrees | ✓ | ✓ |
| Any CLI agent runs as a real terminal session | ✓ | ✓ |
| Wide roster of preconfigured CLI agents | partial | ✓ |
| Native iOS / Android companion apps * | partial | ✓ |
| Remote / SSH workspaces | ✕ | ✓ |
| Keep agents running on app quit; restore after reboot * | ✓ | ✓ |
| Built-in browser agents can drive * | ✓ | ✓ |
| Per-hunk adoption of task diffs * | ✓ | partial |
| Agent-to-agent task delegation * | ✓ | ✓ |
| Shared channels with @-mentions * | ✓ | partial |
| Approval gate when one agent launches another * | ✓ | partial |
* Native iOS / Android companion apps: Orca's companion (beta) runs on iOS and Android and can reply to waiting agents and answer their permission and question cards. wmux has an iPhone companion that answers agents, paired with wmux on your Windows PC or Mac; it does not provide an Android app.
* Keep agents running on app quit; restore after reboot: Both use a background daemon that owns the PTYs, so agents survive quitting the app; neither keeps processes through an OS reboot. Afterwards Orca restores layout and can resume past sessions from its session history; wmux restores saved workspaces and resumes Claude Code conversations when their session IDs are known.
* Built-in browser agents can drive: Orca gives every worktree its own Chromium browser that agents script through the Orca CLI; wmux's built-in browser is driven by agents over CDP.
* Per-hunk adoption of task diffs: Orca's diff viewer supports annotations and stages per file from the Source Control panel; wmux lets you tick individual hunks across task diffs and applies the selection to your working tree in one step (you commit).
* Agent-to-agent task delegation: Orca's orchestration layer (runs, tasks, worker dispatch, inboxes and decision gates) is experimental and enabled under Settings → Experimental.
* Shared channels with @-mentions: Orca agents exchange messages through orchestration inboxes; wmux channels are shared rooms agents and you post to, with @-mentions.
* Approval gate when one agent launches another: Orca relays each agent's own permission prompts, and by default launches agents with their permission-bypass flag unless you choose Manual. wmux asks you before an agent starts another agent with permissions bypassed and declines unanswered requests after 30 seconds unless auto-approve is on.
Where Orca is ahead
- Platforms and devices: Linux as well as Windows and macOS, and a companion app on both iOS and Android.
- Remote work: SSH worktrees and paired remote Orca servers, with auto-reconnect and port forwarding.
- Breadth: 30+ preconfigured CLI agents, account switching with usage tracking, and a session history that can resume past sessions across many agents.
- Integrations and automation: GitHub and Linear in-app, scheduled automations from the CLI, Design Mode in the browser, and computer use.
- Release velocity and a large community (~95k GitHub stars).
Where wmux is ahead
- The harvest workflow: fan one prompt out to up to 8 tasks, then tick individual hunks across their diffs and apply the selection to your working tree in one step — you make the commit.
- Slack-style channels agents actually use — shared rooms with @-mentions — plus A2A task delegation between agents.
- Bots: name a bot and tell it what to do in chat; it starts Claude Code workers on their own branches, runs tests and reports back, and public acts like merging a PR wait for your approval.
- An approval gate for cross-agent execution: an agent cannot start another agent with permissions bypassed until you say yes, and unanswered requests are declined after 30 seconds unless auto-approve is on.
- Fleet view across every agent, on a Windows build that is ConPTY-native with no WSL.
Questions
Does wmux run on Linux?
No. As of October 2026 wmux ships for Windows 10/11 (x64) and macOS (Apple Silicon). Orca also runs on Linux.
Do both have phone apps?
wmux has an iPhone companion that answers agents. Orca has iOS and Android companions (beta).
Are both open source?
Yes. Both are MIT-licensed.
What does wmux do differently?
As of October 2026, Orca's diff viewer stages per file, while wmux applies hunks you pick across several task diffs in one step. wmux bots take jobs in chat; Orca's automations run on a schedule.
Last checked against Orca's docs and changelog on .
Both projects are open source and moving fast, so treat any comparison — including this one — as a snapshot as of October 2026. Corrections are welcome as issues or PRs.