Paseo is a self-hosted control plane for coding agents. The site at paseo.sh calls it one interface for Claude Code, Codex, Copilot, OpenCode, and Pi. The GitHub repo getpaseo/paseo is Apache 2.0 (with third-party components keeping their own licenses). The API listed about 16,055 stars on 2026-09-05. Agents still run on your machine with your credentials; Paseo is the desktop, mobile, web, and CLI layer that starts, reviews, and resumes them.
Compare Orca ADE if you want a desktop ADE built around isolated worktrees, or Happy if you only need a mobile client for Claude Code.
Key Features
- Multi-provider, one UI: custom implementations for Claude Code, Codex, OpenCode, Pi, and OMP, plus more agents through ACP. Paseo does not replace the CLIs; it launches the ones already installed on the host.
- Desktop, mobile, web, CLI: native apps for Windows, macOS, Linux, iOS, and Android, plus a web client at app.paseo.sh. The site claims mobile feature parity with desktop.
- Self-hosted daemon: a local server owns the sessions. Clients attach to it. You can run the daemon headless and skip the desktop app.
- Remote access without giving Paseo your code: optional end-to-end encrypted relay, a local-network connection, or your own tunnel (Tailscale, Cloudflare Tunnel). The FAQ says Paseo does not send your repo to its servers.
- Worktrees, plugins, MCP, SDK: optional git worktrees per agent, plugins that reach mobile, plus MCP, CLI, and TypeScript SDK for automation.
- Voice, locally first: dictation runs on-device by default. Cloud speech is optional if you configure it.
Limitation: Paseo is an orchestrator, not a model. You still pay Claude, Codex, or whoever you already subscribe to. Long sessions can get heavy on mobile; public replies on X have reported crashes when a single session grows large.
Use Cases
- Leave the desk without dropping the agent: start a Claude Code or Codex job on a workstation, then review diffs and reply from a phone.
- Swap providers without swapping apps: keep one workspace when a task fits Codex one day and Claude Code the next.
- Fan out GitHub issues: the docs show MCP or the SDK creating separate worktree agents per ready issue.
Pricing
Paseo itself is free. You need at least one agent CLI installed with your own credentials. Sponsorship is optional via the site's sponsor page. There is no seat fee from Paseo.
Getting Started
- Install at least one agent CLI (Claude Code, Codex, Copilot, OpenCode, or Pi) and sign in there first.
- Download the desktop app from GitHub Releases or the download page. Current advertised Windows installer at research time was
Paseo-Setup-0.7.2-x64.exe. - Or install the iOS app (App Store: Paseo Pocket Engineer) or Android app (
sh.paseo) and point it at your daemon. - Create a workspace, pick a provider, and run a task. Use a worktree if you do not want the agent touching your main checkout.
First-party resource: paseo.sh/docs.
Frequently Asked Questions
Does using Paseo violate provider terms?
The FAQ says it uses each provider's official integration, does not extract tokens, and does not call inference APIs directly. Recheck the current terms for your own account.
Do I need GitHub?
No. Paseo works in any directory. Worktrees are optional and only apply if you already use git.
How does remote access stay private?
Use the hosted relay (end-to-end encrypted), your own tunnel, or LAN. Do not expose the daemon port on the public internet unless you know what you are doing.
Alternatives
- Orca ADE: desktop ADE with parallel agents in isolated worktrees.
- Happy: mobile and web client focused on Claude Code, with Signal-style encryption.
- OpenCode: open-source coding agent you can drive without a separate control plane.
Tips
- Install and test the agent CLI in a terminal before opening Paseo. If the CLI cannot auth, Paseo cannot save you.
- Prefer worktrees for unattended jobs so a runaway edit does not trash your working tree.
- Keep auto-unbookmark-style remote access off until you have reviewed the relay and tunnel setup.
Conclusion
Paseo is the control plane for people who already live in Claude Code, Codex, OpenCode, or Pi and want the same sessions on a phone and a desktop without switching products. Start at paseo.sh.
Comments
No comments yet. Be the first to comment!
Related Tools
T3 Code
t3.codes
Open-source agent harness control surface for Claude Code, Codex, Cursor, Grok Build, and OpenCode with desktop, web, and mobile apps.
Orca ADE
www.onorca.dev
Open-source Agent Development Environment (ADE) for running Claude Code, Codex, OpenCode and other coding agents side by side in isolated worktrees.
ccusage
github.com/ccusage/ccusage
Open-source CLI that analyzes token usage and costs from local coding agent logs across Claude Code, Codex, OpenCode, and more.
Related Insights
Skills + Hooks + Plugins: How Anthropic Redefined AI Coding Tool Extensibility
An in-depth analysis of Claude Code's trinity architecture of Skills, Hooks, and Plugins. Explore why this design is more advanced than GitHub Copilot and Cursor, and how it redefines AI coding tool extensibility through open standards.
Seven AI Coding CLIs, Six Months: No Matter How Strong the Model, Work Needs Supervision
Claude Code, Codex, opencode, pi, omp and DeepSeek Harness all have personalities. After six months of deep use I run a division of labor: pi for the fastest cheapest reviews, omp for complex PRs, DeepSeek Harness on V4 Flash for high-frequency low-cost review, and Claude Code, Qoder and Cursor for writing. No matter how strong the model, work needs supervision — ideally from an independent third party.
Claudesidian: Transform Obsidian into an AI-Powered Second Brain
Discover Claudesidian, an open-source project that perfectly integrates Obsidian with Claude Code. Built-in PARA method, custom commands, and automated workflows for a complete idea-to-implementation solution.