mmux vs Paseo

What is Paseo?

Paseo describes itself as "an open source agentic development environment for desktop, mobile, web, and CLI" [1]. It does not ship its own model: it runs the agent CLIs you already have installed and signed in. Claude Code, Codex, OpenCode, Pi, Antigravity and Muse Code have bundled adapters, and any agent that speaks the Agent Client Protocol works through a generic adapter, with a catalog of more than 25 one-click installs including Cursor, Gemini and GitHub Copilot [3]. Claude Code runs through the official claude CLI using the Claude Agent SDK and counts against your normal Claude plan [4].

The core is a daemon that owns the agents and workspaces. The Electron desktop app for macOS, Windows and Linux starts it automatically; on a server you install it with npm install -g @getpaseo/cli or run the Docker image [1][2]. The native iOS and Android apps, the web app and the CLI connect to the same daemon over SSH, Tailscale or an optional end-to-end encrypted relay that is off until you enable it [6][7]. Each task can get its own git worktree with setup and teardown hooks and supervised services [5].

On top of that come a file editor, diff and pull request review, a built-in browser on desktop, local voice input, plugins, a TypeScript SDK and MCP tools [1][2]. Paseo Hub, a separate service, starts agents on your daemons from GitHub, Slack and Discord events; you can self-host it or use the managed one [8][9]. It has been licensed Apache-2.0 since version 0.7.0 [10][11].

Where Paseo is better

• Phones and other devices. Paseo has native iOS and Android apps that show agents, files, terminals and diffs, and a web app. mmux can only be reached from a phone through an SSH client.
• A graphical workspace. Conversation, editor, terminals, diffs, pull requests and a browser sit in split panes in one window. mmux has a git panel and opens files in your $EDITOR, but no editor, PR view or browser of its own.
• Windows. Paseo publishes Windows installers for x64 and arm64. mmux ships prebuilt binaries for macOS on Apple Silicon and for Linux only.
• Remote access without network setup. The relay lets your phone reach a daemon behind NAT with no open ports, and the relay cannot read the traffic. With mmux you bring your own SSH access.
• Extension and triggers. Plugins add screens, panels, slash commands and providers on every client; a TypeScript SDK and MCP tools cover automation; Hub starts agents from GitHub, Slack and Discord. mmux has none of these.
• Voice. Paseo transcribes speech on-device and sends it to the agent as text. mmux has no voice input.

Where mmux is better

• The agent's own interface. Every agent, Claude Code or anything else, runs as itself in a terminal pane. You see its prompts, menus and status exactly as the CLI draws them, and any command works as an agent without an adapter.
• Terminal and SSH first. mmux is a TUI, so it runs wherever a terminal does: a local tab, an SSH session, a tmux client. Closing the terminal or dropping SSH only detaches. Run mmux again, or mmux attach from anywhere, to rejoin.
• Notifications that cross SSH. When an agent rings the bell or emits a notification escape, mmux writes the notification as a terminal escape sequence, so the popup appears on the machine your terminal runs on, not on the remote host.
• Small footprint. A single Rust binary plus tmux, with no daemon port, no account and no Electron app. A script install keeps itself up to date and restores your session after the restart.
• One sidebar for agents, shells and dev processes. Processes from mmux.yaml start, stop and stream next to the agents, and only one checkout of a repository runs a given process at a time, so worktrees reuse the same ports. A workspace manifest puts several repositories in one sidebar.
• Keyboard-driven git. The git panel stages, commits and pushes with keys, can write the commit message with an installed Claude or Codex CLI, and can schedule a commit for later.

When to use which

Moving from Paseo to mmux

1. Install mmux on the machine where your agents run (the Paseo daemon host), and make sure your agent CLIs are signed in there, as they already are for Paseo.
2. List the agents you use in ~/.mmux/config.yaml. Any command works, not only the ones Paseo has adapters for.
3. Move the scripts and services from paseo.json into processes in the project's mmux.yaml, and the worktree setup line into worktrees.setup. mmux copies .env files into new worktrees by default.
4. Run mmux in the project. Press w for a worktree, and use mmux ask or mmux worktree new where agents used Paseo's orchestration tools.

# ~/.mmux/config.yaml
agents:
  - name: Claude
    cmd: claude
  - name: Codex
    cmd: codex

# ./mmux.yaml
name: my-app
processes:
  - name: Dev server
    cmd: npm
    args: ["run", "dev"]
worktrees:
  setup: npm ci

mmux does not import Paseo's chat history. For some agents, such as OpenCode and Pi, Paseo can copy a resume command so you can continue a session in a terminal [11].