Paseo

An open-source project by Mohamed Boudra (getpaseo/paseo).

Why it matters

Hand a coding agent a long task and it can be tens of minutes before there’s anything to look at. You either stay at the desk, or you leave and lose track of whether the run finished or stalled. With several agents going at once, checking on them means cycling through terminal windows.

Paseo puts the agents behind a daemon running on your own machine — a laptop, a VM, a dev server — and has the desktop, mobile, web, and CLI clients connect to it. The work stays in your environment; checking in and giving the next instruction can happen from any device. The site notes the native mobile app has “full feature parity with desktop.”

What you can do

Representative tasks from the site and the README:

• Check in and steer from away from your desk — start work at your desk, check progress from your phone, send a follow-up task
• Branch to merge in one place — “Create branches, preview the app in the browser, review the diff inline, then commit, open a PR, and merge without leaving Paseo”
• Hand work between agents — plan with Claude Code, then hand off to Codex to implement, picking the right model for each job
• Dictate tasks by voice — “Dictate tasks or talk through problems in voice mode. Hands-free when you need it.”
• Script it from the terminal — “Everything you can do in the app, you can do from the terminal,” including loops and schedules

Grounded in paseo.sh and the getpaseo/paseo README.

Key features

• Daemon and clients

  “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.” The desktop app just bundles the daemon with a UI, so on a server you can run the daemon headless and attach from anywhere else.

• Each provider’s native harness

  “Paseo uses each provider’s native harness, so your subscriptions, skills, config, and MCP servers keep working.” Agents are launched as their own processes rather than wrapped.

• Connectivity options

  Use the end-to-end encrypted relay, connect directly over TCP or your local network, or bring your own tunnel such as Tailscale or Cloudflare Tunnel. Starting the daemon from the CLI asks whether to enable the relay; decline and you connect directly instead.

• Orchestration skills

  npx skills add getpaseo/paseo installs slash commands you can use inside any agent conversation: /paseo-handoff (hand off work between agents), /paseo-loop (loop an agent against clear acceptance criteria, aka Ralph loops, optionally with a verifier), /paseo-advisor (a single agent as an advisor for a second opinion, without delegating the work), and /paseo-committee (two contrasting agents doing root cause analysis and producing a plan).

• Voice

  “Voice runs locally on your device by default. You talk, the app transcribes and sends it to your agent as text.” OpenAI speech providers can be configured for higher-quality transcription and text-to-speech.

• No telemetry

  “Paseo doesn’t have any telemetry, tracking, or forced log-ins.”

Setup

The desktop app is the recommended path — open it and the daemon starts automatically, with nothing else to install.

brew install --cask paseo

Builds for macOS (Apple Silicon, Intel), Windows (x64, ARM64), and Linux (AppImage, DEB, RPM) are at paseo.sh/download; the mobile apps are on the App Store and Google Play.

For servers and remote machines, run the daemon headless:

npm install -g @getpaseo/cli && paseo

Docker runs the daemon and the self-hosted web UI together — open http://localhost:6767 after it starts, then extend the base image with the agent CLIs you use.

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

Driving agents from the terminal:

paseo run --provider claude/opus-4.6 "implement user authentication"
paseo ls                            # list running agents
paseo attach abc123                 # stream live output
paseo send abc123 "also add tests"  # follow-up task
paseo --host workstation.local:6767 run "run the full test suite"

To connect from your phone, open Settings → your host → Pair Device in the desktop app.

Notes

• Bring your own agent CLI — you need at least one of Claude Code, Codex, Copilot, OpenCode, or Pi installed and configured with your credentials. Paseo runs them; it isn’t an agent itself
• Phone access needs a network decision — enable the relay, set up a tunnel, or expose the daemon port. It isn’t automatic after install
• Still on 0.x — the stable download is v0.2.5 with v0.3.0-beta.2 in pre-release, and roughly 690 open issues. Releases ship weekly
• Paseo Hub is separate and in private beta — the optional layer that triggers agents from GitHub, Slack, and Discord activity is marked “Private beta. Self-hosted first,” with design partners recruited through Discord. No pricing is published
• git is optional — “Paseo works in any directory. Worktrees are optional and only relevant if you use git.”
• License — AGPL-3.0. Paseo itself is free; agent usage bills to your own accounts