Quick Verdict
Paseo is a strong option for developers who already use several coding agents and want one local control plane across desktop, web, mobile, and CLI. It is not another model provider. A daemon on your laptop, server, VM, or container starts native provider harnesses such as Claude Code, Codex, and OpenCode. The repository is AGPL-3.0 and had an active release in July 2026.
The decisive issue is trust, not license price. Paseo itself is free, but provider subscriptions, API usage, compute, and review still cost money. Agents run with the permissions available to the daemon process. A worktree separates branches; it does not sandbox commands, credentials, or the wider filesystem.
Best For
- Developers switching among two or more local coding-agent providers.
- Users with a persistent workstation or VM who want to monitor and direct work from a phone.
- Technical teams able to manage credentials, ports, host allowlists, branches, and review gates.
- Not ideal for sensitive repositories without least privilege, secret isolation, backups, and controlled deployment.
Key Features
- Multi-provider orchestration: launches native agent CLIs while preserving their own subscriptions, skills, configuration, and MCP servers.
- Local daemon: manages agent processes and sessions on infrastructure you control.
- Cross-device clients: desktop, web, iOS, Android, and CLI can connect to the same host.
- Git workflow: optional worktrees, inline diffs, previews, commits, and pull-request steps.
- Automation: command-line run, list, attach, and send operations plus handoff, loop, advisor, and committee skills.
- Remote connectivity: direct connections or an end-to-end encrypted hosted relay.
Use Cases
Run separate agents in separate worktrees, compare their implementations, and review both diffs from one interface. Leave a daemon on a controlled development machine and check a long task from mobile. Script repetitive low-risk jobs through the CLI. For releases, database changes, billing, security policy, or destructive operations, keep Paseo upstream of the approval gate: let it prepare candidate changes, then require human review and the normal deployment pipeline.
Pricing
Paseo is free and open source under AGPL-3.0. It does not include inference. Budget for each provider, the daemon host, parallel usage, and review time. Parallel orchestration can increase model spend quickly, so configure provider-side limits and measure complete task cost rather than treating the free orchestrator as a free workflow.
Pros
- Inspectable, self-hostable AGPL-3.0 codebase with active development.
- Reuses native provider harnesses instead of replacing their configuration.
- Unusually complete mobile, desktop, web, and terminal coverage.
- Brings worktrees, diffs, terminals, browsers, and previews together.
- The hosted relay uses end-to-end encryption and avoids opening an inbound daemon port.
Cons
- Coding agents are high-trust processes with access to whatever the daemon user can reach.
- Relay E2E encryption and fresh session keys protect content and old-message replay, but not a compromised endpoint, provider, pairing offer, or daemon host; the relay still observes connection metadata.
- Worktrees isolate Git state, not operating-system permissions.
- Provider costs, account rules, availability, and output quality remain outside Paseo’s control.
- A fast-moving project maintained primarily by one person requires careful update and security monitoring.
Alternatives
| Tool | Best for | Main advantage | Main limitation |
|---|---|---|---|
| Claude Code | Anthropic-first terminal work | Direct native provider path | Does not orchestrate every provider |
| Codex | OpenAI coding workflows | Native OpenAI tooling | Less focused on cross-provider control |
| OpenCode | Open terminal-agent workflows | Flexible provider support | Cross-device control is not its main distinction |
| Pentagon | Persistent agent teams on Apple Silicon | Agent messaging and a spatial workspace | Proprietary and has no current sandbox |
FAQ
Is Paseo actually free?
The orchestrator is free under AGPL-3.0. Provider subscriptions, API tokens, infrastructure, and review are separate costs.
Does Paseo upload my code?
File operations happen on the daemon host. A provider may still receive prompts or code context under its own architecture and terms.
Does an E2E relay make the system zero-trust?
No. It protects message content from the relay and includes replay resistance, but endpoints, pairing material, provider services, and the executing agent remain trust boundaries.
Is a worktree a security sandbox?
No. It reduces branch conflicts but does not stop a process from reading credentials or accessing other paths allowed to the daemon user.
Should it perform production changes automatically?
Not without independent controls. Keep human approval, tests, backups, least privilege, and audited deployment for high-impact actions.
Bottom Line
Paseo is a capable, active local control plane for developers who understand the privileges they are handing to coding agents. Pilot one provider, one low-risk repository, one worktree, and one connection method. Expand only after verifying spend, pairing, logs, recovery, and review behavior.