Paseo
Paseo is a self-hosted control plane that runs Claude Code, Codex, Copilot and 30+ other coding agents from your phone, desktop, browser or CLI.
If you run more than one coding agent, Paseo is the orchestration layer to beat right now — the mobile parity is real, an anonymous reviewer on the homepage calls it "the most slept on orchestrator right now," and the 0.7.0 Apache-2.0 switch removes the licensing question entirely. The 0.11 betas add a Usage screen that discovers your ChatGPT and Claude logins automatically and shows spend per subscription account, which matters once you're paying for three agents at once. Expect to install and authenticate your own agent CLIs, and think about networking once. People who only use one agent in one IDE won't feel the payoff — that's the same gap between Paseo and a single assistant that keeps
Verified 6d ago · liveness 74/100 · cite: rightaichoice.com/tools/paseo
- Developers running several coding agents who want one orchestration layer instead of five terminals
- Anyone who needs to prompt, monitor, and ship agent work from a phone while away from the desk
- Self-hosters and privacy-conscious teams who want agents running on their own machines
- Teams automating agent work via MCP, the CLI, TypeScript SDK, or recurring schedules
- Developers who use a single agent in a single IDE and see no orchestration problem to solve
- Anyone wanting a hosted AI code assistant that works without installing agent CLIs
- Beginners who don't want to run a daemon or configure network access
We scan live Reddit threads, YouTube comments, X posts, G2 reviews and other communities — and hand you an honest verdict in under a minute.
- Honest verdict, not marketing
- Real pros & cons from real users
- Attributed quotes with receipts
3 free scans · no card needed
Skip Paseo if you run a single agent inside one IDE and see no orchestration problem to solve, or if you want a hosted assistant that works without installing any agent CLI or running a daemon.
Paseo itself is open source and doesn't charge for the control plane — your real recurring cost is the agent subscriptions it drives (Claude Code, Codex, Copilot, and so on), which you keep paying per provider.
Paseo's control plane is open source under Apache-2.0 and free to self-host, so the cost that scales with your team is the stack of agent CLIs it drives. That puts it in a different budget conversation than a per-seat cloud IDE: a solo dev running Codex and Claude Code pays only for those subscriptions, while a team of ten needs to budget for ten sets of provider seats plus a machine to run the daemon.
In short
Paseo — Paseo is a self-hosted control plane that runs Claude Code, Codex, Copilot and 30+ other coding agents from your phone, desktop, browser or CLI. Best for Developers running several coding agents who want one orchestration layer instead of five terminals, Anyone who needs to prompt, monitor, and ship agent work from a phone while away from the desk, Self-hosters and privacy-conscious teams who want agents running on their own machines. Free to use.
What's new in Paseo
Checked 6 days agoAcross the latest 3 updates: 3 changelog entries.
Paseo 0.11.0-beta.3 adds pinning to Usage window rows
Usage rows can now be pinned via a hover button. Usage source plugins now implement discover() and fetch() instead of identify(), and fixed Usage cards disappearing on expired or rejected logins.
Paseo 0.11.0-beta.2 expands Usage login discovery
Usage now discovers ChatGPT logins from Codex CLI, OpenCode, Pi and OMP, and Claude logins from the Claude Code credential file, macOS keychain, Pi and OMP, showing one card per subscription account.
Paseo 0.11.0-beta.1 adds Muse Code and Antigravity providers
New providers: Muse Code (model, approval mode, reasoning effort) and Antigravity (drives the agy CLI in Full access). Also adds a Usage screen in the sidebar footer and mid-turn steering for OMP agents.
What people actually say about Paseo — is it worth it?
We ran a structured research pass across product reviews, community discussions, and post-purchase forum threads to surface the patterns vendors won't publish themselves. Below: the recurring strengths, the hidden costs people mention most, and the cohort that consistently regrets adopting this tool.
86 mentions across 6 sources (Hacker News, Product Hunt, App Store, Bluesky, GitHub, Lemmy) · researched Jul 3, 2026.
Average across the 6 sources that answered — each source counts once, not each post.
- +Native mobile app with full desktop feature parity.
- +Orchestrates 34+ coding agents from one interface.
- +Multi-agent workflows: plan, implement, review in sequence.
- +Completely free and open source with no hidden costs.
- +Self-hosted daemon runs on desktop, server, or Docker.
- −Mobile setup process lacks any documentation or instructions.
- −UI bug on mobile: keyboard covers the accept button.
- −Screen freezes reported during use.
- −Text selection in copy is poorly implemented.
- −Custom prompts sometimes silently ignored in some agents.
- • No hidden costs – it's completely free and open source. You pay only for server/hosting if you self-host on a cloud VM.
Viability Score
How well maintained and how widely used is Paseo? Built from what the vendor actually publishes (docs, changelog, tutorials, integrations, pricing), whether the site is live, and how much real users discuss it. How we calculate this
Last calculated: October 2026
How we score →Key Features
- Multi-agent orchestration across Claude Code, Codex, Copilot, OpenCode, Pi, Cursor, Muse Code, Antigravity and 30+ more providers
- Native iOS and Android apps with full feature parity to desktop
- Desktop app (macOS, Linux .deb/.rpm/AppImage) that bundles and auto-starts its own daemon
- Browser web UI served by the daemon itself
- Scriptable CLI via npm install -g @getpaseo/cli
- Self-hosted daemon on desktop, headless machine, Docker (ghcr.io/getpaseo/paseo), NAS, or cloud VM
- SSH connections to remote daemons
- Plugin installs from Git repositories, with a plugin SDK for sidebar items, screens, daemon behavior and composer attachments
- Timeline transformations in the agent timeline
- End-to-end encrypted relay, or direct / local-network / Tailscale / Cloudflare Tunnel connection
- Isolated git worktree per agent task, with origin/main fetch on branch
- In-app browser preview with branch-based URLs
- Inline diff review with commit, PR, and merge actions
- PR/MR support for GitHub, GitLab, Gitea, Forgejo, and Codeberg
- Voice control with local-first speech and TTS
About Paseo
Paseo is an open-source control plane for coding agents. It wraps the agent CLIs you already pay for — Claude Code, Codex, Copilot, OpenCode, Muse Code, Antigravity and roughly 33 more — so your existing subscriptions, skills, config and MCP servers keep working. Instead of learning another assistant, you get one interface across desktop, web, iOS/Android and a scriptable CLI, and you run the daemon on a laptop, a home lab box, Docker, or a cloud VM and attach from anywhere. The mobile app is the part people talk about. Prompting, monitoring and reviewing agent work from a phone works at full parity with desktop. Connection is direct over your local network, through Tailscale or Cloudflare Tunnel, or via an optional end-to-end encrypted relay, so code stays on your machines by default. For build-review-ship loops, Paseo spins up isolated git worktrees per agent, previews apps in-browser with branch-based URLs, and handles inline diffs, commits, PRs and merges without leaving the app, with PR/MR actions for GitHub, GitLab, Gitea, Forgejo and Codeberg. Schedules handle recurring agent tasks, and MCP, the CLI and the TypeScript SDK are there when you'd rather automate Paseo itself. Recent releases moved fast: 0.7.0 added plugin installs from Git, timeline transformations and SSH connections to remote daemons and switched the project to Apache-2.0; 0.11.0-beta.1 added Muse Code and Antigravity providers, mid-turn steering for OMP agents, and a Usage screen that tracks what each subscription account has spent; 0.11.0-beta.2 expanded Usage login discovery to ChatGPT logins from Codex CLI, OpenCode, Pi and OMP and Claude logins from the Claude Code credential file, the macOS keychain, Pi and OMP; 0.11.0-beta.3 added pinning to Usage rows. It suits developers who already live in several agents and want a self-hosted cockpit rather than another cloud IDE.
Behind the Verdict
Paseo solves a problem that appears the moment you start paying for more than one agent CLI. Claude Code is good at planning, Codex at long implementation runs, OpenCode and Pi at cheap bulk work — and you end up with five terminals, five sets of history, five ways of watching a diff. Paseo wraps all of them behind one control plane with a shared workspace model: project → workspace → session, with an isolated git worktree per agent task. The reasons to pick it over alternatives: Mobile parity is genuinely the headline. The iOS/Android apps aren't a read-only monitor; you can start a workspace, steer a running agent, review an inline diff, commit, open a PR and merge from the phone. One homepage reviewer: "control agents from anywhere - mac, phone, web." Another: "Being able to check and manage agent progress from my phone while I'm out is so convenient." A third: "Can interchange between Codex, Claude Code, Opencode, Pi. Stable mobile and desktop apps connected through a secure relay from your VMs." No new model subscriptions. Paseo doesn't ship models; it drives the CLIs you already authenticated. Your skills, dotfiles, MCP servers and config keep working. Self-hosted by default. The daemon lives on your machine, on a Raspberry Pi, in Docker (ghcr.io/getpaseo/paseo:latest, port 6767), or on a cloud VM. Reach it over LAN, Tailscale, Cloudflare Tunnel, or the optional E2E-encrypted relay. Your code doesn't leave your network unless you choose the relay. Real shipping workflow. Worktrees, in-browser preview with branch-based URLs, inline diff review, commits, PRs and merges for GitHub, GitLab, Gitea, Forgejo and Codeberg — all in-app. Automation surface. Schedules for recurring agent tasks, an MCP server, a CLI (npm install -g @getpaseo/cli), a TypeScript SDK, and plugins you can install from Git. A fast, active release cadence. The 0.11.0 betas added Muse Code and Antigravity providers, a Usage screen with per-account spend tracking that discovers your ChatGPT and Claude logins automatically, mid-turn steering for OMP agents, Fast mode and Auto thinking level for OMP, Codex Fast and Ultrafast speeds, and tablet terminal key bars. Where it doesn't fit: Paseo manages other agents, it doesn't ship one — you must install and authenticate at least one provider CLI before it does anything. It's self-hosted, so remote access means thinking about networking once. It ships frequently, including betas (0.11.0-beta.3 as of October 2, 2026), which is not what you want if your team needs a slow, conservative release train. And if you run exactly one agent in exactly one IDE, there is no orchestration problem to solve. Compared with a fully managed cloud IDE, you are trading vendor-run compute for control of your own machines.
Researching Paseo? Get your full AI stack in 60 seconds.
Free, no signup — tell us your goal and get tools matched to your budget & existing stack.
Real-world workflow fit
Concrete scenarios for the personas Paseo actually fits — and what changes day-one when you adopt it.
Starts a Claude Code planning workspace on the laptop, then leaves for a commute and steers the same agent from the Paseo iOS app over an E2E-encrypted relay.
Outcome: Returns to an inline diff, commits the change, opens the PR, and merges it from the phone without touching a terminal.
Runs ghcr.io/getpaseo/paseo:latest on a NAS on port 6767, extends the image with their agent CLIs, and connects via Tailscale from the desktop app and an Android tablet.
Outcome: Every agent session lives on the NAS with code never leaving the home network, reachable at full desktop parity from any device.
Sets up a schedule that runs a Codex agent against the main repo nightly, with MCP servers attached to the schedule and output routed into Hub runs.
Outcome: Wakes up to a reviewed queue of PRs in the Workspaces → Ready to review list instead of an empty backlog.
Use Cases
- Run a Claude Code planning agent from your phone while commuting, then trigger Codex implementation when you're back at the desk.
- Set up a daily recurring agent to scan your repo for TODO comments and generate PRs.
- Fork a chat into a new worktree to experiment without affecting your main branch.
- Use the in-app browser to let an agent fill out a form or scrape data automatically.
- Monitor and control multiple agent sessions across projects from a single desktop or mobile app.
- Self-host the daemon on a Raspberry Pi or in Docker and access the web UI from any device on your network.
- Check a running agent's diff, commit, and merge a PR from an iPad or Android tablet using the terminal key bar.
- Track what each ChatGPT or Claude subscription is spending through the Usage screen before a coding session runs long.
Models Under the Hood
as of 2026-09-22
Limitations
- Paseo is an orchestrator that runs third-party coding agents; it does not ship its own models, and you must install and configure provider CLIs (Claude Code, Codex, Copilot, OpenCode, Muse Code, Antigravity, etc.) yourself with working credentials before it's useful.
- The GitHub CLI (gh) is also recommended and needs to be authenticated for PR-aware worktrees.
- The daemon is self-hosted, so remote access requires network setup — relay, Tailscale, Cloudflare Tunnel, or exposing the daemon port.
- The Docker image does not bundle agent CLIs, so you extend it with the agents you use.
- On Linux, AppImage and extracted tar archives run with Chromium's sandbox disabled on hosts that restrict user namespaces; the installed .deb/.rpm packages are the way to keep OS process isolation.
- The changelog shows active development with frequent updates, and the current beta is 0.11.0-beta.3 as of October 2, 2026.
as of 2026-10-03
Verification history
We have re-verified Paseo 8 times since . Each pass re-reads the vendor's own pages and re-checks every listed field against that evidence; passes where nothing had changed are marked as such.
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
Showing the 6 most recent of 8 verification passes.
Free to cite with attribution — this page re-verifies continuously.
12-month cost
Project the real annual outlay, including the implied monthly cost when only an annual tier is published.
Vendor list price only. Add-on usage, seat overages, and contract minimums are surfaced under Hidden costs & gotchas.
Plans compared
For each published Paseo tier: who it actually fits, and what it adds vs. the previous tier. Cross-reference the cost calculator above for projected annual outlay.
Free
$0/mo
Ideal for
Individual developers and self-hosters who already pay for one or more agent CLIs and want a cockpit for them without adding another subscription.
What this tier adds
Starting tier — the whole control plane: self-hosted daemon, desktop/web/mobile/CLI clients, multi-provider orchestration, worktrees, PR/MR shipping, schedules, MCP, plugins, the TypeScript SDK, and the optional E2E relay, under Apache-2.0.
Where the pricing makes sense
The company stage and team size where Paseo's pricing actually pencils out — and where peers do it cheaper.
Paseo's control plane is open source under Apache-2.0 and free to self-host, so the cost that scales with your team is the stack of agent CLIs it drives. That puts it in a different budget conversation than a per-seat cloud IDE: a solo dev running Codex and Claude Code pays only for those subscriptions, while a team of ten needs to budget for ten sets of provider seats plus a machine to run the daemon.
Setup time & first value
How long it actually takes to get something useful out of Paseo — broken out by persona, not the marketing-page minute.
Desktop app: download, open, and the bundled daemon starts automatically — pair your phone from Settings in a couple of minutes, then add at least one provider CLI. Server/CLI: npm install -g @getpaseo/cli and run paseo to start the daemon and answer the relay/pairing prompt, roughly five minutes plus agent install. Docker: one docker run against ghcr.io/getpaseo/paseo:latest, plus extending the
Switching to or from Paseo
How to bring data in from common predecessors and how to get it back out — written for the switcher, not the buyer.
- →From five separate terminal windows: install @getpaseo/cli, point Paseo at the same repo, and let each agent run in its own git worktree under the same workspace list.
- →From a single-provider desktop app (e.g. Claude Code alone): install Paseo's desktop app, keep the same CLI and credentials, and add the other providers as you need them.
- →From a hosted cloud IDE: run the daemon on your own machine or VM, install your agent CLIs, and connect over Tailscale or the encrypted relay instead of a vendor-hosted workspace.
- →From a headless SSH workflow: start the daemon on the remote box and attach with SSH connections to remote daemons, keeping the terminal workflow while gaining the mobile and web clients.
- ↗To a single-agent IDE (Cursor, Copilot Chat): stop the daemon and go back to running one CLI or editor assistant directly — you lose multi-provider orchestration and mobile parity.
- ↗To a hosted cloud IDE: move the repo into the vendor's managed environment and re-authenticate agents there; you trade self-hosting control for vendor-run compute.
- ↗To raw terminals: uninstall the CLI and desktop app; your git worktrees, skills, config, MCP servers and provider credentials all carry over unchanged since Paseo wraps, not replaces, the CLIs.
Integrations
Resources & Guides
- Documentationpaseo.sh
Docs · Paseo
Full product docs from paseo.sh
- Documentationpaseo.sh
Workspaces · Paseo
Full product docs from paseo.sh
- Documentationpaseo.sh
Providers · Paseo
Full product docs from paseo.sh
- Documentationpaseo.sh
Schedules · Paseo
Full product docs from paseo.sh
- Documentationpaseo.sh
Plugins · Paseo
Full product docs from paseo.sh
- Documentationpaseo.sh
Docker · Paseo
Full product docs from paseo.sh
Tutorials & Learning
YouTube returned 6 videos for “Paseo”, and we withheld 6: 6 could not be judged, because “Paseo” is a single word that other videos use for other things. We are showing none, because we could not prove any of them are about Paseo.
Official links
Tools that pair well with Paseo
Common stack mates teams adopt alongside Paseo, with the specific reason each pairing earns its keep.
Ellipsis
Ellipsis Agent Cloud runs Claude Code and Codex coding agents in managed cloud sandboxes defined by environment.yaml.
Claude Code
Claude Code is Anthropic's agentic coding assistant that plans, edits, and runs commands across your repo from the terminal, IDE, or browser.
Cline
Open-source coding agent that reads your repo, edits files, and runs terminal commands across VS Code, JetBrains, CLI, and a desktop app.
Featured Head-to-Head Comparisons
Paseo vs Truleo
These tools serve entirely different markets: Truleo is a paid law enforcement intelligence platform, while Paseo is a free open-source orchestrator for coding AI agents. Your choice depends solely on your domain—if you're in law enforcement, Truleo's automated leads and report writing are invaluable; if you're a developer juggling multiple coding agents, Paseo's mobile control and multi-agent workflows are a game-changer. There is no overlap.
Paseo vs Locus Robotics
If you run a warehouse needing flexible AMR automation to boost picking productivity by 2-3x, Locus Robotics is the proven choice with its new Locus Array. If you're a developer wanting to orchestrate multiple AI coding agents from your phone or desktop without paying a dime, Paseo offers cutting-edge features like multi-agent workflows and in-app browser control. They serve completely different domains, so pick based on your operational need.
Paseo vs Presto Voice
If you run a QSR chain with drive-thrus, Presto Voice delivers proven revenue lift and up to 95% automation, but requires contacting sales. If you're a developer juggling multiple AI coding agents, Paseo is free, open source, and lets you orchestrate them from anywhere—even your phone. Choose based on your problem domain: restaurant operations vs. software development.
Alternatives to Paseo
View all
Ellipsis
Ellipsis Agent Cloud runs Claude Code and Codex coding agents in managed cloud sandboxes defined by environment.yaml.
Claude Code
Claude Code is Anthropic's agentic coding assistant that plans, edits, and runs commands across your repo from the terminal, IDE, or browser.
Frequently Asked Questions
Used Paseo? Help shape our editorial sentiment research.