paseo — What is it?

Paseo is a voice-controlled development environment that orchestrates multiple coding agents from desktop and mobile devices, enhancing developer productivity and collaboration.

⭐ 10,020 Stars 🍴 943 Forks TypeScript NOASSERTION Author: getpaseo
Source: Official README and linked documentation View on GitHub →

Why it matters

Paseo is being discussed because its unique approach of integrating various coding agents like Claude Code, Codex, Copilot, OpenCode, and Pi through a single interface. It addresses the pain points of managing multiple coding tools and enhances developer efficiency with features like voice control and cross-device compatibility. The project differs through its privacy-first stance and the flexibility of self-hosting agents on developers' own machines.

Source: Official README and linked documentation

Core Features

Multi-provider integration

Paseo integrates multiple coding agents like Claude Code, Codex, Copilot, OpenCode, and Pi, allowing developers to choose the right tool for each task.

Source: Official README and linked documentation
Voice control

Developers can dictate tasks or discuss problems using voice mode, enhancing hands-free productivity.

Source: Official README and linked documentation
Cross-device compatibility

Paseo supports iOS, Android, desktop, web, and CLI, enabling developers to start work on one device and continue on another.

Source: Official README and linked documentation
Privacy-first approach

Paseo does not collect any telemetry, tracking, or require forced log-ins, ensuring user privacy.

Source: Official README and linked documentation

Architecture

The architecture of Paseo is modular, with distinct packages for server, client, and CLI functionalities. It uses a monorepo structure with TypeScript as the primary language. Key components include the Paseo daemon for agent orchestration, an Expo client for mobile and web interfaces, and a CLI for command-line interactions. The project employs design patterns like the monorepo pattern for code organization and the use of WebSocket for real-time communication.

Source: Official repository tree and dependency files

Project Knowledge Graph

Knowledge graph: project (center) + core features (inner hexagons) + key dependencies (outer chips) @getpaseo/server@getpaseo/serv… @getpaseo/app @getpaseo/relay @getpaseo/website@getpaseo/webs… @getpaseo/cli Multi-provider integrationMulti-provider inte… Voice control Cross-device compatibilityCross-device compat… Privacy-first approachPrivacy-first appro… paseo Project Core feature Key dependency

Tech Stack

LanguageTypeScriptFrameworkExpo for mobile and web, Electron for desktop, and npm scripts for build and development processes
@getpaseo/server@getpaseo/app@getpaseo/relay@getpaseo/website@getpaseo/cli
Self-hosted on developers' machines, with potential for cloud deployment based on the server package
Source: Official repository tree and dependency files

Quick Start

Install the CLI globally using `npm install -g @getpaseo/cli` and start Paseo with `paseo`. For the desktop app, download it from [paseo.sh/download](https://paseo.sh/download) or the GitHub releases page. Open the app, and the daemon starts automatically. To connect from your phone, scan the QR code shown in Settings.
Source: Official README and linked documentation

Use Cases

Paseo is suitable for developers who need to manage multiple coding agents, such as those working on AI-assisted coding, collaborative development, or remote work scenarios. It is useful for tasks like code generation, debugging, and code review.

Source: Official README and linked documentation

Strengths & Limitations

Strengths

  • Enhanced productivity through integration of multiple coding agents
  • Privacy-focused development environment
  • Cross-device compatibility for configurable workstyles

Limitations

  • Limited documentation and community support for early-stage projects
  • Dependency on specific coding agents and their APIs
Source: Official README and linked documentation

Latest Release

v0.8.0 is the current stable version. v0.9.0-beta.2 is tracked separately as a preview.

Source: Official releases

Verification and evidence

status: docs-only  |  checked_at: 2026-09-22  |  environment: Docs only. Read the official repository, documentation, and v0.8.0 release. Platform installation was not completed in this workspace.  |  limitations: The complete installation flow was not tested on macOS, Windows, Linux, mobile devices, or Docker.  |  observed_output: The guide's commands, default ~/.paseo path, daemon pair flow, run, ls, attach, and send commands, and documentation links correspond to official materials. No command output is presented as a local test result.

Source: Official releases

Comparison

Paseo adds a host and daemon, device pairing, and multi-task orchestration around coding agents. Direct use of one agent CLI is simpler when there is only one agent and no remote-control requirement.

Source: Official releases

Verdict

Paseo is a project for developers seeking to simplify their coding workflow with a voice-controlled, multi-agent environment. Its privacy-first approach and cross-device compatibility make it a option for teams or individuals looking to enhance productivity and collaboration in their development processes.

Frequently Asked Questions

What did the documentation review verify for paseo on 2026-09-22?

The guide's commands, default ~/.paseo path, daemon pair flow, run, ls, attach, and send commands, and documentation links correspond to official materials. No command output is presented as a local test result. The complete installation flow was not tested on macOS, Windows, Linux, mobile devices, or Docker.

What evidence boundary applies to this paseo review?

The review environment was: Docs only. Read the official repository, documentation, and v0.8.0 release. Platform installation was not completed in this workspace. paseo behavior outside that scope still needs a local check.

Sources and review scope
This review is based on the project's public documentation. Versions, installation commands, and feature boundaries can change upstream; check the cited sources and current release before use. Sources checked on: 2026-09-23 13:55.

Reference materials: README, GitHub API, dependency files