At a glance
The open-source agent workspace formerly called Mux, for parallel coding tasks with custom agents, nested subagents, persistent scoped memory, compaction, MCP, local or container runtimes, policy files, editor integrations, and budgeted CLI goal runs.
Good choice if
- Parallel feature work in isolated child workspaces
- Teams that want agent definitions and tool policy committed with the repository
- Workflows spanning desktop, CLI, editors, Docker, and remote runtimes
Check before choosing
- The platform has more operational concepts than a single-session coding CLI
- The default local runtime has no filesystem or process isolation; worktrees separate files but still execute on the host
- Docker and dev-container runtimes provide optional container isolation, while SSH security depends on the remote machine and credentials
See 3 more considerations
- Tool hooks can block commands and run validation but are experimental; they are configurable policy rather than an OS isolation boundary
- Browser and remote server access uses a bearer token by default, but --no-auth deliberately removes that boundary and must be limited to trusted networks
- Browser automation is only an MCP example, not a built-in browser-control capability; anonymous usage telemetry is enabled unless disabled