Paseo is a self-hosted environment for running coding agents such as Claude Code, Codex, and OpenCode on your own machines. It helps developers start, monitor, and steer several agents at once, then check on them later from a phone, a second computer, or a terminal. It serves people who already pay for agent subscriptions and want those agents to keep working while they step away from their desk.[1][2]
Quick verdict
Teams of one to a few developers who live in CLI coding agents gain the most from Paseo. Its concrete advantage is that each provider runs as its own native process, so existing subscriptions, skills, configuration, and MCP servers keep working untouched. The material constraint is that Paseo ships no agent of its own: everything useful depends on provider CLIs you install and authenticate yourself. If you already run Claude Code, Codex, or OpenCode daily and want them supervised from anywhere, choose Paseo; if you want an agent included in the box, choose Emdash or another bundled alternative instead.[1][2][3]
Key features
Multi-provider orchestration Run Claude Code, Codex, OpenCode, Pi, OMP, Cursor, Muse Code, Antigravity, and more side by side, each as its own process with its native configuration intact.[1][2]
Four client surfaces Work from the desktop app, native mobile apps with documented full feature parity, a browser web UI served by your own daemon, or the terminal through the Paseo CLI.[1][2]
Parallel workspaces in Git worktrees Fan tasks out across separate worktrees so each run keeps its branch, terminal session, conversation, and review state together.[1]
Diff review and testing workflow Inspect changes, review diffs, and test work from the same surface that started the agents, instead of switching tools per provider.[1]
Schedules and triggers Recurring agent runs and event-driven starts are supported, including GitHub, Slack, and Discord triggers through Paseo Hub team sharing.[1][2]
Automation surfaces Drive Paseo from other agents over MCP, from scripts through the CLI, or from code with the TypeScript SDK, plus a plugin model for panels, slash commands, and themes.[1][2]
Local-first privacy posture Agents execute on your machines and Paseo states it sends your code nowhere; remote access goes over the local network, your own tunnel such as Tailscale, or an optional end-to-end encrypted relay.[1][2]
Free Apache-2.0 core The software is free and open source under the Apache License 2.0, with downloads for desktop, an npm CLI package, and an official Docker image.[1][2]
Who will love it
CLI-agent developers who leave their desk fit the central documented workflow of starting tasks at a workstation and reviewing them later from a phone.[1][2]
Small teams sharing agent infrastructure fit the shared daemon access plus GitHub, Slack, and Discord triggers that give one place to start and follow agent work.[1]
Automation builders fit the MCP, CLI, SDK, and plugin surfaces that let another agent or script fan GitHub issues out to separate worktree agents.[1][2]
Who should avoid it
Anyone expecting an agent in the box should avoid Paseo: it manages other agents and is not useful until at least one provider CLI with working credentials is installed.[1]
Non-technical users should avoid it: setup involves provider CLIs, authentication, daemon addresses, and optionally Docker or Tailscale, which assumes developer comfort.[1]
Buyers needing stated enterprise assurances should avoid it: no SSO statement, support SLA, or vendor data-location documentation was found on the observed official pages.[1][2]
Alternatives and compatibility
OpenCode complements Paseo: official Paseo pages document running OpenCode as one of several providers inside Paseo workspaces, extending an OpenCode workflow with orchestration and remote control.[1][2]
Emdash competes with Paseo as an editorial inference, not a vendor endorsement: both run multiple CLI coding agents in parallel in isolated Git worktrees with diff review, so a developer choosing a self-hosted parallel-agent environment would evaluate either.[1][2]
The underlying providers work standalone: Paseo requires user-installed provider CLIs, so staying with Claude Code, Codex, or OpenCode alone remains valid where orchestration is unnecessary.[1]
Questions worth asking
What is the best Paseo alternative for non-technical users?
Neither Paseo nor its closest self-hosted peers target non-technical users, since all assume provider CLIs and credentials. If someone technical handles setup, Emdash is the conditional pick for day-to-day use because its desktop app detects installed CLIs automatically and keeps tasks, review, and pull requests in one place.[1]
Is Paseo really no-code?
No. The clients are visual, but real tasks need provider CLI installation, credential setup, daemon addresses or pairing, and optionally Docker or VPN configuration. Developer work is required before any agent runs.[1]
How much does Paseo cost per month?
Paseo itself costs nothing: it is free and open source, as confirmed on the official site in October 2026. You still pay your agent providers' own subscriptions and any infrastructure you run the daemon on.[1]
Sources and editorial review
Source research. Reviewed on October 12, 2026. Written by Sanjib Sah. AI assisted; reviewed by a human editor.
We have not run or tested this product.
- Paseo official homepage
official · Observed October 12, 2026
Official site: multi-agent orchestration positioning, named providers, free Apache-2.0 FAQ, local-first handling, MCP/CLI/SDK automation surfaces.
- Paseo getting-started docs
official · Observed October 12, 2026
Getting-started docs: agent-on-operator-machines model, desktop/npm/Docker installs, provider-CLI prerequisites, workspaces, worktrees, review, orchestration, plugins, Hub, connectivity.
- getpaseo/paseo repository
official · Observed October 12, 2026
Repository page confirming getpaseo/paseo identity under the getpaseo organization.
- Paseo LICENSE
official · Observed October 12, 2026
License text granting Apache License 2.0 except incorporated third-party components, copyright Mohamed Boudra 2025-present.
- getpaseo/paseo repository metadata
official · Observed October 12, 2026
Repository metadata: TypeScript, 20,591 stars, platform topics, homepage https://paseo.sh, created 2025-10-13, pushed 2026-10-12, not archived.
- Emdash official homepage
official · Observed October 12, 2026
Competitor evidence: open-source parallel-agent environment with isolated workspaces, diff review, PRs, CI checks, and automations on macOS, Windows, and Linux.
Compared with these products
No explicit proprietary baseline is recorded.