Skip to content
/

Paseo

paseo · getpaseo/paseo · ★ 6.8k · last commit 2026-05-26

Multi-provider AI coding agent orchestration daemon with cross-device access (phone/desktop/CLI) and git worktree isolation.

Best whenAI coding agents should be manageable from any device, including mobile with voice control, without giving up your local dev environment.
Skip ifForced logins or cloud telemetry, Single-provider lock-in
vs seeds
superpowers(skills pack), Paseo ships a full daemon + Electron + iOS/Android app. The /paseo-loop pattern is a packaged Ralph loop …
Primitive shape 8 total
Skills 7 MCP tools 1
00

Summary

Paseo — Summary

Paseo is a TypeScript monorepo that provides a unified management layer for multiple AI coding agent CLIs (Claude Code, Codex, Copilot, OpenCode, Pi) running on the user's own machines. A persistent local daemon orchestrates agent processes, exposes a WebSocket API, and relays connections from mobile (iOS/Android), desktop (Electron), web, and CLI clients. Users can run multiple agents in parallel on different worktrees, send tasks from their phone, and use voice dictation. Paseo's four skills (/paseo-handoff, /paseo-loop, /paseo-advisor, /paseo-committee) are Claude Code skills that teach agents to orchestrate other agents through the Paseo daemon — enabling multi-provider handoff, Ralph-style acceptance-criteria loops, advisory second opinions, and two-agent committee analysis. The project is self-hosted and privacy-first: no telemetry, no forced logins.

Differs from seeds: Closest to taskmaster-ai in providing a cross-tool management layer, but Paseo focuses on agent process orchestration (spinning up/monitoring concurrent CLI processes) rather than task breakdown. Unlike claude-conductor (markdown scaffold) or superpowers (skills pack), Paseo ships a full Expo mobile app, Electron desktop app, and CLI daemon. The skill system (/paseo-loop = Ralph loop, /paseo-committee = consensus advisory) borrows BMAD's committee pattern but implements it as runtime agent calls rather than persona markdown.

01

Overview

Paseo — Overview

Origin

Paseo is developed by Mouheb Boudra (@moboudra). The project's tagline: "Coding agents from your phone, desktop and CLI." It solves the problem of monitoring and controlling multiple AI coding agents across devices without giving up the dev environment setup you already have.

Philosophy

From README:

  • 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.
  • 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: No telemetry, no tracking, no forced log-ins.

Positioning

Paseo sits between the user and their existing AI agent CLIs. It does NOT replace Claude Code or Codex — it orchestrates them. The daemon manages the process lifecycle; clients (phone, desktop, web) are view layers.

Repo Facts

02

Architecture

Paseo — Architecture

Distribution

  • Desktop app: Download from paseo.sh/download or GitHub releases (Electron)
  • CLI/headless: npm install -g @getpaseo/cli && paseo
  • Mobile: iOS/Android app via paseo.sh

Monorepo Packages

packages/
├── server/    # Paseo daemon (agent process orchestration, WebSocket API, MCP server)
├── app/       # Expo client (iOS, Android, web)
├── cli/       # `paseo` CLI for daemon and agent workflows
├── desktop/   # Electron desktop app
├── relay/     # Relay package for remote connectivity
└── website/   # Marketing site + documentation (paseo.sh)

Architecture Diagram

User Clients (phone / desktop / web / CLI)
       ↕  WebSocket / QR-code relay
    Paseo Daemon (packages/server)
       ├── Agent Process 1 (Claude Code --worktree feature-x)
       ├── Agent Process 2 (Codex gpt-5.4)
       └── Agent Process N (OpenCode ...)

Daemon Features

  • Agent process orchestration (spawn, monitor, kill, resume)
  • WebSocket API for all client types
  • MCP server built into daemon (packages/server)
  • QR code for mobile pairing
  • Remote connectivity via relay

Supported Agent Providers

  • Claude Code
  • Codex (OpenAI)
  • GitHub Copilot CLI
  • OpenCode
  • Pi

Required Runtime

  • Node.js (for daemon + CLI)
  • At least one agent CLI installed and configured
  • npm for @getpaseo/cli

Config Files

  • paseo.json — project-level Paseo configuration
  • .mise.toml / .tool-versions — runtime version pinning
  • CLAUDE.md / AGENTS.md — present in repo root for agent guidance
03

Components

Paseo — Components

Skills (6, in skills/)

  • paseo-handoff — Hand off work between agents (e.g., plan with Claude, implement with Codex)
  • paseo-loop — Loop an agent against clear acceptance criteria (Ralph loop), optionally with a verifier
  • paseo-advisor — Spin up a single agent as advisor for a second opinion without delegating work
  • paseo-committee — Form a committee of two contrasting agents for root cause analysis + plan
  • paseo-epic — Unknown (epic-level work breakdown)
  • paseo-orchestrate — Orchestration coordination skill
  • paseo — Core Paseo skill (base integration)

CLI (packages/cli)

Binary: paseo

Key subcommands:

  • paseo run --provider <provider/model> "<task>" — Start an agent run
  • paseo run --provider codex/gpt-5.4 --worktree feature-x "<task>" — Run with worktree
  • paseo ls — List running agents
  • paseo attach <id> — Stream live output
  • paseo send <id> "<message>" — Follow-up to running agent
  • paseo --host <remote>:<port> run "<task>" — Run on remote daemon

Desktop App (packages/desktop)

  • Electron application
  • Daemon starts automatically on open
  • Shows running agents, output streams

Mobile App (packages/app)

  • Expo (React Native) — iOS, Android, web
  • Connect to daemon via QR code scan
  • Voice control support

Daemon (packages/server)

  • WebSocket API server
  • Agent process lifecycle management
  • MCP server integration
  • Relay client for remote connections

Relay (packages/relay)

  • Remote connectivity package
  • Community Go implementation: paseo-relay by zenghongtu

Install Skill

npx skills add getpaseo/paseo

Installs all 7 skills into the project.

05

Prompts

Paseo — Prompts

Skill System

Skills are installed via npx skills add getpaseo/paseo. Source is in skills/ directory. Full verbatim content not accessible via public GitHub API (files may be gated or uses a different skill format), but the README provides functional descriptions.

Verbatim Skill Descriptions (from README)

Skills teach your agent to use Paseo to orchestrate other agents.

- /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.

Technique: Meta-orchestration skills — each skill teaches an agent to use the Paseo daemon to spawn and coordinate other agents. This is a "skills that spawn agents" pattern, distinct from pure LLM-role coordination.

CLI Usage Examples (from README)

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"

Technique: CLI-first design with explicit provider/model selection. The --worktree flag is a first-class parameter for isolation. Remote execution via --host flag enables cloud/VM delegation.

09

Uniqueness

Paseo — Uniqueness & Positioning

differs_from_seeds

Paseo is closest to taskmaster-ai in providing a cross-tool management layer, but the comparison diverges quickly: taskmaster-ai manages a task decomposition tree with JSON state, while Paseo manages OS-level agent processes with real-time streaming. Paseo is also similar to claude-conductor in being multi-agent coordinator, but claude-conductor is zero primitives (markdown templates only), whereas Paseo ships a full daemon, Electron desktop, iOS/Android app, and CLI. The skill patterns (/paseo-loop = Ralph loop, /paseo-committee = two-agent advisory) borrow from the superpowers multi-agent pattern but implement them as daemon-driven subprocess orchestration rather than Claude Task tool calls.

Distinctive Positioning

  1. Cross-provider skill orchestration: The only framework where skills explicitly cross provider boundaries — /paseo-handoff lets Claude plan and Codex implement within the same workflow. No other framework does this as a skill.

  2. Mobile + voice as first-class: iOS/Android app with voice dictation for task input is unique in this corpus. The mental model is "manage your coding agents from anywhere."

  3. Git worktree as isolation primitive: Explicit --worktree flag per run, multiple agents on separate worktrees, enabling true parallel execution without conflict.

  4. Ralph loop as skill: /paseo-loop formalizes the acceptance-criteria loop pattern (popularized by smart-ralph/ralph-claude-code) as a reusable skill installable via npx skills add.

  5. Remote daemon delegation: --host workstation.local:6767 enables treating a remote machine's agent environment as a compute target.

Observable Failure Modes

  • License is NOASSERTION — unclear terms, may limit commercial use
  • Requires all agent CLIs to be pre-installed and configured (prerequisite burden)
  • Daemon is a dependency — if it crashes, all running agents are affected
  • No container isolation — agents run natively; malicious code in project can affect host
  • Mobile app requires relay for non-local access (additional infrastructure)
  • Skill content not publicly readable in depth (skill source may be proprietary)
04

Workflow

Paseo — Workflow

Setup Phase

Step Artifact Gate
Install one+ agent CLIs Configured CLI (claude, codex, etc.) Manual
Install Paseo desktop or CLI paseo binary / Electron app One-liner
Start daemon WebSocket server on port 6767 Auto (desktop) / paseo (CLI)
Pair mobile (optional) QR code scan Manual

Per-Task Flow

Step Artifact
User runs paseo run --provider <p> "<task>" Agent process spawned
Daemon tracks process, exposes via WebSocket Session ID assigned
Client streams output (paseo attach <id>) Live output
User sends follow-up (paseo send <id> "...") Message injected
Agent completes or user stops Session closed

Multi-Agent Handoff Flow (/paseo-handoff)

Step Artifact
Agent 1 (planner) completes planning Plan artifact
Skill triggers paseo run --provider <p2> Agent 2 (implementer) spawned
Agent 2 reads plan, implements Code changes

Ralph Loop Flow (/paseo-loop)

Step Artifact
Define acceptance criteria Criteria string
Skill spawns agent loop Agent run
Agent attempts, evaluator checks Pass/fail
Loop continues until criteria met Working implementation

Committee Flow (/paseo-committee)

Step Artifact
Problem described Problem statement
Two contrasting agents spawned Agent A + Agent B
Each analyzes independently Independent analyses
Committee produces unified plan Plan document

Approval Gates

  • Worktree selection (manual choice via --worktree flag)
  • Provider selection (explicit --provider flag)
  • No automatic gates in daemon mode
06

Memory Context

Paseo — Memory & Context

State Storage

Paseo itself does not implement agent memory — it delegates to the agent CLIs it manages. Memory is handled by the underlying agent (Claude Code's context, Codex's context, etc.).

Daemon State

  • Agent process registry (session IDs, provider, status, worktree)
  • Message queue for paseo send follow-ups
  • Relay connection state

Persistence

  • Session history: unknown (likely in-memory or SQLite in packages/server)
  • Agent-side memory: depends on the agent CLI being managed
  • No explicit cross-session memory system in Paseo itself

Cross-Session Handoff

  • paseo resume <id> can resume a stopped agent
  • Session IDs persist while daemon is running
  • No mechanism for cross-daemon session transfer (relay is for real-time, not state)

Context Compaction

  • Paseo does not manage context windows — each agent CLI handles its own
  • /paseo-loop acceptance criteria pattern implicitly handles "start fresh" per loop iteration

Worktree-Based Isolation

  • --worktree <name> flag creates/uses a git worktree for the session
  • Multiple agents can work on different worktrees simultaneously without conflicts
  • Worktree state persists in the git repo
07

Orchestration

Paseo — Orchestration

Multi-Agent

Yes — Paseo is explicitly designed for running multiple agents concurrently. Each agent is a separate process managed by the daemon.

Orchestration Patterns

  • Parallel-fan-out: Multiple agents run simultaneously on different worktrees
  • Sequential handoff: /paseo-handoff passes work from Agent 1 (planner) to Agent 2 (implementer)
  • Consensus advisory: /paseo-committee runs two contrasting agents and synthesizes their analyses
  • Loop with verifier: /paseo-loop runs an agent in a Ralph loop with optional separate verifier agent

Isolation Mechanism

Git worktree per agent (primary isolation):

  • --worktree <name> creates a dedicated git worktree for each agent session
  • Agents work on separate branches without stepping on each other
  • Isolation is at the filesystem/git level, not container level

No container isolation — agents run as native OS processes on the host machine.

Execution Mode

On-demand with persistent daemon:

  • Daemon is always-on
  • Agent processes are spawned per task
  • Background operation with attach/detach support

Multi-Model

Yes — explicit provider selection per run:

  • --provider claude/opus-4.6
  • --provider codex/gpt-5.4
  • --provider opencode/...

Different agents in the same workflow can use different models.

Remote Execution

  • --host workstation.local:6767 delegates task to a remote Paseo daemon
  • Relay package enables cross-network connectivity

Consensus Mechanism

/paseo-committee: Two contrasting agents produce independent analyses, then synthesize a unified plan. Not algorithmic consensus — LLM-to-LLM advisory.

08

Ui Cli Surface

Paseo — UI & CLI Surface

CLI Binary

  • paseo — installed via npm install -g @getpaseo/cli
  • Full CLI reference at paseo.sh/docs/cli
  • Subcommands: run, ls, attach, send, --host

Desktop App

  • Electron (packages/desktop)
  • Available at paseo.sh/download
  • Daemon starts automatically on app open
  • Shows running agents, task management

Mobile App

  • Expo (React Native) — iOS, Android, web (packages/app)
  • Connect to daemon via QR code scan
  • Voice control / dictation support
  • Check on agents from phone, send follow-up tasks
  • Screenshot shown in README: modern mobile UI with task list

Web App

  • Browser-based client (part of Expo web build)
  • Connects to local daemon

Local UI

  • The desktop Electron app is the primary local UI
  • Daemon also exposes WebSocket API for custom client integration
  • MCP server built into daemon for agent-side integration

Observability

  • paseo attach <id> — live output streaming
  • paseo ls — list all running agents with status
  • paseo --host — remote daemon access

Voice Control

Voice dictation supported in mobile app. Users can speak tasks rather than type them.

IDE Integration

None native. Claude Code and other agent CLIs are invoked as subprocesses, not via IDE extensions.

Related frameworks

same archetype · same primary tool · same memory type

CodeMachine CLI ★ 2.5k

JavaScript-DSL workflow orchestration engine that captures repeatable AI coding agent workflows with tracks, condition groups,…

Codexia ★ 690

Tauri desktop app providing visual control plane, task scheduler, git worktree manager, and headless REST API for Codex CLI +…

Kagan ★ 88

Kanban TUI for AI coding agents with a structurally enforced human review gate (REVIEW → DONE cannot be automated) — one git…

oh-my-claudecode (Yeachan-Heo) ★ 35k

Zero-learning-curve teams-first multi-agent orchestration for Claude Code with autopilot (6-phase lifecycle), ralph (PRD-driven…

CCG Workflow ★ 5.4k

Routes Claude + Codex + Gemini to task-appropriate collaboration strategies (direct-fix through full-collaborate) with hook-based…

CCS (Claude Code Switch) ★ 2.4k

Routes Claude Code tasks to the optimal AI agent (Codex, Factory Droid, Ollama, Claude) based on configurable cost/capability…