Mohamed BoudraandGitHub
16120ebff1
* feat(plugins): expose Paseo API to local plugins Plugin surfaces borrow the selected host connection while subprocess handlers receive an exclusively owned IPC session, so plugins can use normal workspace and agent operations without inventing another transport. * feat(plugins): reload global enablement safely Treat the global plugin switch as a live daemon setting and teach plugin automation to inspect it before acting. Enabling remains permission-gated because plugin backend code can access the daemon machine and client contributions execute inside the app. * feat(plugins): expose plugin logs Capture plugin stdout and stderr separately from IPC so authors can debug initialization, RPC, cleanup, and crash behavior from the app or CLI. Keep a bounded tail across lifecycle recovery while preserving structured output in the daemon log. * fix(build): order plugin dependency builds * test(plugins): align startup and CLI expectations
3.1 KiB
title, description, nav, order, category
| title | description | nav | order | category |
|---|---|---|---|---|
| Getting started | Install Paseo and start running coding agents from anywhere. | Getting started | 1 | Getting started |
Getting started
Paseo runs your coding agents on your machine and gives you a mobile, desktop, web, and CLI client to drive them from anywhere. Three common ways to install.
Desktop app (recommended)
Download from paseo.sh/download or the GitHub releases page. Open it and you're done.
The desktop app bundles its own daemon and starts it automatically, no separate install required. On first launch you'll see a brief startup screen, then connect from your phone using Settings → your host → Pair Device.
Server / CLI
For headless machines, dev boxes, or any setup where you want the daemon running without the desktop UI:
npm install -g @getpaseo/cli
paseo
Paseo starts the daemon locally, then asks whether to enable the end-to-end encrypted relay and print a pairing QR code. If you decline, enter the daemon address manually over TCP, Tailscale, or another VPN.
The daemon can also serve the browser web app itself, so you can use the full UI without the hosted app. See Self-hosting the web UI.
Configuration and local state live under PASEO_HOME (defaults to ~/.paseo).
Docker
For servers, dev boxes, NAS devices, or homelab hosts, run the official image:
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
Then open http://localhost:6767.
The image runs the daemon and serves the bundled web UI. It does not bundle agent CLIs, so extend it with the agents you use. See Docker for Compose, reverse proxy, agent install, and security examples.
Where next
- Connectivity, connect through the relay or Tailscale.
- Docker, run the daemon and bundled web UI in a container.
- Workspaces, the project, workspace, and session model Paseo is built around.
- Providers, what a provider is and how Paseo wraps existing CLIs.
- Orchestration, let one agent delegate work to other providers and models.
- Plugins, add trusted local surfaces, sidebar actions, daemon behavior, and composer attachments.
- CLI reference, every command.
- Self-hosting the web UI, serve the browser app from your own daemon.
- GitHub repo
- Report an issue
Prerequisites
Paseo manages other agents, it doesn't ship one. Before it's useful, install at least one provider CLI yourself and make sure it works with your credentials. See Supported providers for the full list.
You'll also want the GitHub CLI (gh) installed and authenticated, Paseo uses it for PR-aware worktrees and a few orchestration features.