getpaseo/paseo

What Paseo Does

Paseo is an agentic development environment for desktop, mobile, web, and CLI. Instead of juggling separate windows for Claude Code, Codex, Copilot, OpenCode, Pi, Antigravity, and Muse Code, it puts them behind one interface and a local server called the daemon. The daemon launches agent processes, exposes a WebSocket API, and can also act as an MCP server.

Core workflows include running many agents in parallel, each in its own Git worktree; editing files, reviewing diffs, opening pull requests, and running terminals in split panes; and starting work at a desk then checking in from a phone or scripting it from the terminal. Clients are native iOS/Android, Electron desktop, self-hosted web, and the paseo CLI. No telemetry, tracking, or forced login is claimed.

Quick Start

The recommended path is the desktop app: download it from the project download page or the GitHub releases, open it, and the daemon starts automatically. Before that, install and authenticate at least one supported agent CLI, such as Claude Code or Codex.

For a server or VM without the desktop app, install the CLI and start the daemon:

npm install -g @getpaseo/cli
paseo

The daemon asks whether to enable the end-to-end encrypted relay for device pairing; declining means connecting directly over TCP, Tailscale, or another VPN. Full setup, connectivity, and configuration are in the docs.

A Docker alternative starts the daemon and web UI on port 6767:

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

After it starts, open http://localhost:6767. The base image needs to be extended with the agent CLIs you use, and credentials supplied via environment variables or the persistent /home/paseo volume; see the Docker documentation.

From the terminal, agents can be launched and inspected directly:

paseo run --provider claude/opus-4.6 "implement user authentication"
paseo ls
paseo attach abc123
paseo send abc123 "also add tests"

The CLI reference covers remote daemons, worktrees, and the remaining flags.

Extending It

Plugins run on the daemon and appear in every connected client with the same UI. They can add screens, sidebar items, workspace panels, Command Center entries, slash commands, attachment sources, timeline items, and themes; they can also adjust agent configuration, environment, MCP servers, permissions, and provider registration. Install from the registry with paseo plugin add owner/slug, or from Git or a local directory. Plugins run with access to the daemon machine, so only trusted code should be installed; see the plugin docs.

Skills teach an agent to orchestrate other agents, installed with npx skills add getpaseo/paseo. The provided skills are /paseo-handoff for passing work between agents, /paseo-advisor for a second opinion, and /paseo-committee for a two-agent review and planning session.

A TypeScript SDK, @getpaseo/client, exposes the daemon over WebSocket for building issue integrations, dashboards, and orchestration services:

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 and API reference for the full surface.

Constraints

Paseo orchestrates agent CLIs; it does not supply model credentials itself. Each provider must be installed and authenticated separately, and model names in examples (such as claude/opus-4.6 or codex/gpt-5.5) depend on what the installed CLI exposes. Agents run on the daemon machine with the full local development environment, so host access and permissions follow that machine's configuration.

The server route needs Node.js and npm for the CLI; the Docker route needs a working container runtime and a password set via PASEO_PASSWORD. Mobile connectivity without the encrypted relay requires a reachable network path such as TCP or Tailscale. The README states Apache-2.0 licensing, though the repository metadata reports the license as unrecognized, so the license file is worth checking before redistribution.

HotRepo's Take

The project has drawn repeated Show HN posts. The June 2, 2026 thread reached 92 points and 54 comments (discussion), with comments covering both sides of mobile agent access: some users describe using it to keep an agent running while away from the desk, while another called shipping code from a phone a bad trend. The maintainer replied in that thread that the mobile side is about not losing access to work after leaving the desk (reply). A separate commenter said the mobile app ran on a 13-year-old Nexus 7 with 2GB RAM, which is an individual report rather than a benchmark. The thread also questioned the word "beautiful" in the submission title, with a reply noting that the project's own marketing did not use that term. Across the recorded threads, discussion centers on the multi-surface workflow and the tradeoffs of remote agent access rather than on the orchestration internals.