Paseo

Paseo has a daemon-client design. The daemon runs on the machine that holds the code, starts each coding agent as a subprocess of an existing CLI and streams its output over a WebSocket API. Clients (Electron desktop, Expo mobile and web, and the paseo CLI) attach to the daemon directly, through Tailscale or another VPN, or through an optional relay.

Workspaces are the unit of isolation. A workspace can be a plain directory or a git worktree on its own branch. Agents inside the same workspace share files; agents in separate worktrees do not. The typical flow in the docs is: create a worktree workspace, launch agents in it, review the diff against the base branch, then merge or archive it.

Coordination is agent-driven. With Paseo tools enabled (off by default), an agent can create workspaces, spawn worker agents on any configured provider, send prompts to other agents by ID, stop them and collect results; the worker shows in a Subagents track. The CLI offers the same operations. The daemon keeps the agent and workspace records, and worktrees live under $PASEO_HOME/worktrees/ by default. The docs say Paseo does not proxy model calls.

Agents can ask permission for actions, and pending requests are handled by the user; from the CLI, paseo permit ls, allow and deny list and answer them. A person can attach to any agent, send follow-up prompts and review the diff before merging a worktree workspace. Paseo tools that let one agent spawn others are off by default and can be limited per provider. Access to the daemon is controlled by named permissions, and the relay is off until the user accepts a prompt.

npm install -g @getpaseo/cli

# Prerequisite: at least one agent CLI (claude, codex, opencode, ...) installed and logged in
npm install -g @getpaseo/cli
paseo                                # starts the daemon, asks about the encrypted relay

# Isolated workspace on a new branch, agent on Codex
paseo run --provider codex --new-workspace worktree --worktree-mode branch-off \
  --new-branch feature/x --base origin/main "implement feature X"

paseo ls                             # list running agents
paseo attach abc123                  # stream live output
paseo send abc123 "also add tests"   # follow-up prompt
paseo run --provider codex --background "Review this branch without changing files"
paseo permit ls                      # pending permission requests

• Paseo does not include an agent: install and authenticate at least one agent CLI first (Claude Code, Codex, GitHub Copilot, OpenCode or Pi are listed as prerequisites).
• The desktop app starts the daemon automatically; the CLI path is npm install -g @getpaseo/cli then paseo.
• Paseo tools (MCP) for agents are off by default; turn on Settings > your host > Agents > Enable Paseo tools, then start a new agent so it receives them.
• The relay is off on new installs; without it, connect over TCP, Tailscale or another VPN.
• The README shows --worktree feature-x while the CLI reference documents --new-workspace worktree --worktree-mode ...; the CLI reference form is used above.
• If Paseo cannot find an installed provider, the docs point to PATH and environment mismatches (Troubleshooting page).

Yes, as a server. The daemon runs an MCP server whose tools let an agent manage other agents, workspaces, terminals and schedules. Injecting those tools into agents is off by default.

The daemon, apps and CLI are open source and the README lists no account requirement. Paseo Hub, a separate managed service for triggering agents from GitHub, Slack and Discord, has Free and Pro plans, so the record is marked open-core.

GitHub reports no license because the LICENSE file starts with a custom header. The rest of the file is the Apache License 2.0, and the README says Apache-2.0. Third-party components keep their own licenses.

Native adapters cover Claude Code, Codex, OpenCode and Pi; an Agent Client Protocol catalog adds Hermes Agent and dozens of others. You install and log in to the CLI yourself.

Yes. A workspace can be backed by a git worktree on its own branch, created with paseo workspace create --isolation worktree or paseo run --new-workspace worktree.