wmux · comparison
wmux vs T3 Code
Choose wmux if you want any CLI agent running as a real terminal pane, per-hunk adoption across task diffs, bots you hand jobs in chat, and a daemon that keeps terminals running when the app closes on Windows as well as macOS.
Choose T3 Code if you want a chat-first client for your providers on desktop, web, iOS and Android, with conversation checkpoints, and you are comfortable with a very early (v0.1) release.
T3 Code (t3.codes) is an open-source (MIT) "agent harness control surface" from Ping (ping.gg). It drives the agents already set up on your machine — Codex, Claude, Cursor, Grok Build, OpenCode and Antigravity, plus agents from the ACP Registry — through desktop apps for Windows, macOS and Linux, a web app, and iOS and Android apps. v0.1.0 shipped on October 15, 2026, and the README is candid: "We are very very early in this project. Expect bugs."
The two tools take different shapes. T3 Code is a chat-first client: each thread talks to a provider, optionally in its own new worktree, with approvals and checkpoints handled in the conversation. wmux is an ADE built on a workspace multiplexer: every agent is a real terminal pane, panes coordinate over channels, and a daemon keeps them running when the app closes.
| wmux | T3 Code | |
|---|---|---|
| Open source (MIT) | ✓ | ✓ |
| Windows & macOS desktop apps | ✓ | ✓ |
| Linux desktop app | ✕ | ✓ |
| Mobile apps (iOS / Android) * | partial | ✓ |
| Parallel tasks in isolated git worktrees * | ✓ | ✓ |
| Any CLI agent as a real terminal pane * | ✓ | partial |
| Per-hunk adoption of task diffs | ✓ | partial |
| Agent-to-agent channels & task delegation * | ✓ | partial |
| Approval gate when one agent launches another * | ✓ | partial |
| Keep agents running when the app closes * | ✓ | partial |
| Built-in browser agents can drive | ✓ | ✓ |
| Checkpoints in the agent conversation | ✕ | ✓ |
* Mobile apps (iOS / Android): T3 Code ships iOS and Android apps plus a web app. wmux has an iPhone companion that answers agents, and no Android app.
* Parallel tasks in isolated git worktrees: T3 Code threads can start in a new worktree (configurable as the default); wmux fans one prompt out to up to 8 tasks, each in its own worktree.
* Any CLI agent as a real terminal pane: T3 Code integrates a set of providers plus ACP-compatible agents and has its own terminals; wmux runs any CLI agent as a real PTY pane.
* Agent-to-agent channels & task delegation: T3 Code tracks work agents delegate to subagents and exposes an MCP server that lets outside agents start and message threads; wmux adds shared channels with @-mentions plus A2A task delegation.
* Approval gate when one agent launches another: T3 Code's Supervised mode asks before commands and file changes (new threads default to Full access), and subagent approvals surface in the parent thread. wmux asks you before an agent starts another agent with permissions bypassed.
* Keep agents running when the app closes: T3 Code can run its server as a background service on Linux and macOS; Windows background services are not supported. wmux's daemon keeps terminal processes running when the app closes on both Windows and macOS.
Where T3 Code is ahead
- Everywhere you are: desktop apps for Windows, macOS and Linux, a web app, and native iOS and Android apps, plus remote access to an environment on another machine.
- Provider depth: per-thread permission modes (Supervised, Auto-accept edits, Auto, Full access), multiple Codex and Claude accounts, and any agent from the ACP Registry.
- Checkpoints and subagent delegation built into threads, and agents can answer with rendered HTML pages — charts, tables, mockups.
- Open source with ~28k GitHub stars as of its v0.1.0 release.
Where wmux is ahead
- Any CLI agent, not a provider list: if it has a CLI, it runs as a real PTY pane you can watch and type into.
- Fan-out and harvest: one prompt to up to 8 tasks in their own worktrees, then tick hunks across task diffs and apply the selection to your working tree in one step.
- Windows parity: a ConPTY-native app (no WSL) whose daemon keeps terminal processes running when the app closes — on Windows too.
- 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.
- Channels with @-mentions, A2A task delegation, and an approval gate before any agent starts another with permissions bypassed.
Questions
Is T3 Code open source?
Yes, under the MIT license, like wmux.
Does T3 Code run on Windows?
Yes, it has Windows desktop builds. Its background service is documented for Linux and macOS only; wmux's daemon keeps terminals running when the app closes on Windows too.
How mature is T3 Code?
v0.1.0 shipped on October 15, 2026, and its README calls the project very early.
Last checked against T3 Code's docs and changelog on .
T3 Code is very early and moving quickly, so treat this as a snapshot as of October 2026. If you want one chat-style client for your providers across desktop, web and phone, T3 Code is worth watching. If you want many agents of any kind running as real terminals on Windows or macOS, coordinating with each other and landing reviewed hunks, that is what wmux is for. Corrections are welcome as issues or PRs.