Paseo

English · 简体中文 · 日本語 · 한국어

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.

Plugins

Add themes, workspace panels, commands, settings screens, and coding-agent providers with trusted TypeScript plugins. Install from a local directory or Git repository with paseo plugin add <source>.

See the plugin docs for your Paseo version, or start with the 0.8 beta quickstart. Plugins run with access to your daemon machine and inside connected clients; install only code you trust.

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:

• Claude Code
• Codex
• GitHub Copilot
• OpenCode
• Pi

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, open Settings → your host → Pair Device.

CLI / headless

Install the CLI and start Paseo:

npm install -g @getpaseo/cli
paseo

Paseo starts locally, then asks whether to enable the end-to-end encrypted relay for device pairing. If you decline, connect directly over TCP, Tailscale, or another VPN. This path is useful for servers and remote machines.

For full setup and configuration, see:

• Docs
• Connectivity guide
• Configuration reference

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.5 --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; --cwd is a path on that host
paseo run --host workstation.local:6767 --cwd /workspace "run the full test suite"

See the full CLI reference for more.

TypeScript SDK

Build issue integrations, dashboards, and orchestration services with @getpaseo/client:

import { createPaseoClient } from "@getpaseo/client";

const client = createPaseoClient({ url: "ws://127.0.0.1:6767/ws" });
await client.connect();

const agent = await client.agents.create({
  config: { provider: "codex/gpt-5.5" },
  cwd: "/Users/me/dev/storefront",
  prompt: "Review the current diff and name the riskiest change.",
});

const result = await agent.waitForFinish();
console.log(result.lastMessage);

await client.close();

See the SDK quickstart, recipes, and API reference.

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-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: paseo CLI for daemon and agent workflows
• packages/desktop: Electron desktop app
• packages/relay: Relay transport and encryption used by the daemon and clients
• packages/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

Related projects

• getpaseo/paseo-relay — official distributed relay, written in Elixir
• paseo-vscode — VS Code extension

License

Apache-2.0