Orchestrate multiple AI coding agents across devices
Self-hosted daemon running Claude Code, Codex, Copilot, OpenCode, and Pi agents in parallel, controllable from phone, desktop, or CLI.
Why it matters
Run and coordinate multiple AI coding agents (Claude Code, Codex, Copilot, OpenCode, Pi) in parallel from a unified interface across desktop, mobile, web, and CLI, enabling developers to delegate coding tasks, hand off work between agents, and ship code from any device while maintaining full control over their local development environment.
Outcomes
What it gets done
Run coding agents in parallel on your local machine with your existing dev environment and tools
Hand off tasks between different AI providers to match the right model to each job
Control and monitor agent workflows via voice, mobile app, desktop, or terminal commands
Loop agents against acceptance criteria, form agent committees, or spin up advisors for second opinions
Install
Add it to your toolbox
Run in your project directory:
curl -fsSL https://spark.entire.vc/get/getpaseo-paseo | bash Overview
Paseo MCP
Self-hosted daemon that runs Claude Code, Codex, GitHub Copilot, OpenCode, and Pi coding agents in parallel on your own machine, with desktop, mobile, web, and CLI clients plus voice control, no telemetry or forced login. Use it to run, monitor, or hand off coding agent work across multiple agent providers from any device - starting a task at your desk and checking in from your phone, or scripting runs from a remote server via the CLI or Docker.
What it does
Paseo is a self-hosted daemon that runs coding agents - Claude Code, Codex, GitHub Copilot, OpenCode, and Pi - on your own machine with your full dev environment, tools, and configs, and exposes one unified interface to control them from desktop, mobile, web, or CLI clients. Its server package includes agent process orchestration, a WebSocket API, and an MCP server, so agent runs can be started, monitored, and directed from wherever is convenient, including voice control for hands-free dictation.
When to use - and when NOT to
Use it when you want to run multiple coding agents - potentially different providers for different jobs - in parallel on your own hardware, and check on or steer them from any device rather than being tied to one terminal. It particularly suits workflows that hand work between agents (planning with one model, implementing with another), long-running agent loops against acceptance criteria, or getting a second opinion from an advisor agent without delegating the actual work. It requires at least one agent CLI already installed and configured with its own credentials (Claude Code, Codex, Copilot, OpenCode, or Pi) - Paseo orchestrates existing agent CLIs rather than replacing them.
Capabilities
The CLI covers the core workflow: paseo run --provider claude/opus-4.6 "implement user authentication" starts a run on a chosen provider/model (optionally in its own git worktree via --worktree), paseo ls lists running agents, paseo attach <id> streams live output, and paseo send <id> "..." delivers a follow-up instruction to a running agent - all of which also work against a remote daemon via --host. A companion skills package (npx skills add getpaseo/paseo) adds four commands usable inside any agent conversation: /paseo-handoff to hand work from one agent to another, /paseo-loop to loop an agent against clear acceptance criteria with an optional verifier, /paseo-advisor to consult a second agent for an opinion without delegating the task, and /paseo-committee to form two contrasting agents into a root-cause-analysis committee.
How to install
The desktop app (download from paseo.sh/download or GitHub releases) starts the daemon automatically and shows a QR code to pair a phone. For headless or server use, npm install -g @getpaseo/cli then paseo shows a terminal QR code for pairing. A Docker image (ghcr.io/getpaseo/paseo:latest) runs the daemon plus a self-hosted web UI, configured via a PASEO_PASSWORD environment variable and persistent volumes for the home directory and workspace.
Who it's for
Developers who want to run several coding agents in parallel on their own machine - across providers - and manage, monitor, or hand off between them from whichever device is at hand, without sending code or credentials to a third-party hosted service.
Source README
Paseo
One interface for Claude Code, Codex, Copilot, OpenCode, and Pi agents.
Run agents in parallel on your own machines. Ship from your phone or your desk.
- Self-hosted: Agents run on your machine with your full dev environment. Use your tools, your configs, and your skills.
- Multi-provider: Claude Code, Codex, Copilot, OpenCode, and Pi through the same interface. Pick the right model for each job.
- Voice control: Dictate tasks or talk through problems in voice mode. Hands-free when you need it.
- Cross-device: iOS, Android, desktop, web, and CLI. Start work at your desk, check in from your phone, script it from the terminal.
- Privacy-first: Paseo doesn't have any telemetry, tracking, or forced log-ins.
Getting Started
Paseo runs a local server called the daemon that manages your coding agents. Clients like the desktop app, mobile app, web app, and CLI connect to it.
Prerequisites
You need at least one agent CLI installed and configured with your credentials:
Desktop app (recommended)
Download it from paseo.sh/download or the GitHub releases page. Open the app and the daemon starts automatically. Nothing else to install.
To connect from your phone, scan the QR code shown in Settings.
CLI / headless
Install the CLI and start Paseo:
npm install -g @getpaseo/cli
paseo
This shows a QR code in the terminal. Connect from any client. This path is useful for servers and remote machines.
For full setup and configuration, see:
Docker
Run the Paseo daemon and self-hosted web UI in Docker:
docker run -d --name paseo \
-p 6767:6767 \
-e PASEO_PASSWORD=change-me \
-v "$PWD/paseo-home:/home/paseo" \
-v "$PWD:/workspace" \
ghcr.io/getpaseo/paseo:latest
Open http://localhost:6767 after it starts. Extend the base image with the agent CLIs you use, then provide credentials through environment variables or the persistent /home/paseo volume. See the Docker documentation for full setup details.
CLI
Everything you can do in the app, you can do from the terminal.
paseo run --provider claude/opus-4.6 "implement user authentication"
paseo run --provider codex/gpt-5.4 --worktree feature-x "implement feature X"
paseo ls # list running agents
paseo attach abc123 # stream live output
paseo send abc123 "also add tests" # follow-up task
# run on a remote daemon
paseo --host workstation.local:6767 run "run the full test suite"
See the full CLI reference for more.
Skills
Skills teach your agent to use Paseo to orchestrate other agents.
npx skills add getpaseo/paseo
Then use them in any agent conversation:
/paseo-handoff- hand off work between agents. I use this to plan with Claude and then handoff to Codex to implement./paseo-loop- loop an agent against clear acceptance criteria (aka Ralph loops), optionally with a verifier./paseo-advisor- spin up a single agent as an advisor for a second opinion, without delegating the work itself./paseo-committee- form a committee of two contrasting agents to step back, do root cause analysis, and produce a plan.
Development
Quick monorepo package map:
packages/server: Paseo daemon (agent process orchestration, WebSocket API, MCP server)packages/app: Expo client (iOS, Android, web)packages/cli:paseoCLI for daemon and agent workflowspackages/desktop: Electron desktop apppackages/relay: Relay package for remote connectivitypackages/website: Marketing site and documentation (paseo.sh)
Common commands:
# run all local dev services
npm run dev
# run individual surfaces
npm run dev:server
npm run dev:app
npm run dev:desktop
npm run dev:website
# build the server stack
npm run build:server
# repo-wide checks
npm run typecheck
Community
- paseo-relay - self-hosted relay in Go
FAQ
Common questions
Discussion
Questions & comments · 0
Sign In Sign in to leave a comment.