* feat(website): show orchestration and remote in an animated hero mockup The homepage hero now has five scenes: Orchestration, Remote, Code review, Pull requests, and Plugins. Orchestration and Remote were missing before, and they are what separates Paseo from a single-machine agent app. Orchestration, Code review, and Plugins play a script once the mockup is 60% on screen, and again on every pill click. Each script is a list of beats (wait, click, type, user, agent, tools, turnEnd, mark) laid end to end. A non-React clock owns the time and components read one fact at a time, so only the part that changed renders. A pointer clicks the composer, the subagents pill, and the review controls. Reduced motion shows each finished scene. The right panel is 300px for the file tree and grows to 424px for the pull request and the plugin. Picking a pill scrolls the pills and the mockup into view. * fix(website): keep a picked hero scene playing and scroll it into view the same in every browser A pill click before the mockup was 60% on screen played its scene, and then the visibility start played the same scene again from zero. The player now starts the opening scene only when no scene has played, and the hero stops the clock when it unmounts. Picking a pill used scrollIntoView with `nearest`. For an element taller than the window, each engine picks its own edge, and WebKit left the pill 25% visible in a 1280x600 window. The hero now computes the scroll itself: the least that shows the pills and the mockup, never past the pills at the top. * fix(website): scroll a picked hero scene by where the hero settles, not where it slides The hero slides up 40px as it enters. A pill clicked during the slide measured the frame 40px low, so the scroll stopped with the pills 24px above the window once the slide ended. This was the cause of the WebKit failure in CI. The earlier explanation, that engines differ on scrollIntoView, was wrong. The scroll now measures the frame from layout offsets, which ignore the slide. The test holds the page clock so the slide stays at its first frame. * test(website): hold the hero's slide-in still when a pill is picked during it The test stopped the page timers but let time run, so it caught the bug only when the click landed in the first second after load. It now pauses the clock before the page loads and checks that the slide is still in progress at the click. * test(website): put the hero's 40px slide-in back by hand in the slide-in test The test held the page clock to freeze the slide, but WebKit did not hold it, so the test failed on its own precondition. It now waits for the slide to end, puts the 40px offset on the container, picks a scene, and removes the offset. Reduced motion makes the scroll instant, so the test asserts the result without waiting for a scroll to settle. * fix(website): start the opening hero scene in a window shorter than most of the mockup The scene waited for 60% of the mockup to be on screen. A window shorter than 60% of the mockup, such as a wide browser with devtools docked at the bottom, never reaches that, so the scene never started. It now starts when a line 60% of the way down the mockup is on screen. That is the same moment in an ordinary window, and a short window reaches it as the page scrolls past.
Paseo
One interface for Claude Code, Codex, Copilot, OpenCode, Pi, Antigravity, and Muse Code agents.
Paseo is an open source agentic development environment for desktop, mobile, web, and CLI. Open the desktop app and work: agents, editor, terminals, diffs, pull requests, and a browser in one window. Run many agents at once, each in its own worktree, on one machine or several. The mobile app is the full app, native on iOS and Android.
- Parallel agents: Run many agents at once, each in its own worktree.
- Built-in orchestration: Agents in Paseo can create worktrees, launch other agents, and talk to them, across providers.
- Complete development workflow: Edit files, review diffs, open pull requests, and run terminals, in split panes you arrange how you want.
- 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, Pi, Antigravity, and Muse Code through the same interface. Pick the right model for each job.
- Voice control: Dictate tasks or talk through problems in voice mode. Hands-free when you need it.
- 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: Paseo doesn't have any telemetry, tracking, or forced log-ins.
Run parallel tasks in Paseo: start agents in separate worktrees, review their diffs, run each app, and check it in the built-in browser.
Sponsors
Cloud coding agents |
Become a sponsor | Become a sponsor |
Plugins
Plugins run on the daemon and show up in every client you connect, with the same UI on desktop, web, iOS, and Android. Write a plugin once and it is on your phone.
- UI: screens, sidebar items, workspace panels, Command Center items, slash commands, composer pills, attachment sources, timeline items, themes.
- Agent lifecycle: change configuration, environment, and MCP servers, answer permissions, follow up when a turn ends.
- Providers: add a coding agent as a provider.
Install from the registry with paseo plugin add owner/slug, or from Git or a local directory.
Plugins run with access to your daemon machine and inside connected clients; install only code you trust.
Getting Started
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.
Prerequisites
You need at least one agent CLI installed and configured with your credentials:
Desktop app (recommended)
Download it from paseo.sh/download or the GitHub releases page. Open the app and the daemon starts automatically. Nothing else to install.
To connect from your phone, open Settings → your host → Pair Device.
Server
For a server, a VM, or any machine without the desktop app. Install the CLI and start the daemon:
npm install -g @getpaseo/cli
paseo
Paseo starts, then asks whether to enable the end-to-end encrypted relay for device pairing. If you decline, connect directly over TCP, Tailscale, or another VPN. The desktop, mobile, and web apps connect to this daemon like any other host.
For full setup and configuration, see:
Docker
Run the Paseo daemon and self-hosted web UI in Docker:
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
Open http://localhost:6767 after it starts. Extend the base image with the agent CLIs you use, then provide credentials through environment variables or the persistent /home/paseo volume. See the Docker documentation for full setup details.
CLI
Everything you can do in the app, you can do from the terminal.
paseo run --provider claude/opus-4.6 "implement user authentication"
paseo run --provider codex/gpt-5.5 --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; --cwd is a path on that host
paseo run --host workstation.local:6767 --cwd /workspace "run the full test suite"
See the full CLI reference for more.
TypeScript SDK
Build issue integrations, dashboards, and orchestration services with @getpaseo/client:
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, recipes, and API reference.
Skills
Skills teach your agent to use Paseo to orchestrate other agents.
npx skills add getpaseo/paseo
Then use them in any agent conversation:
/paseo-handoff— hand off work between agents. I use this to plan with Claude and then handoff to Codex to implement./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.
Development
Quick monorepo package map:
packages/server: Paseo daemon (agent process orchestration, WebSocket API, MCP server)packages/app: Expo client (iOS, Android, web)packages/cli:paseoCLI for daemon and agent workflowspackages/desktop: Electron desktop apppackages/relay: Relay transport and encryption used by the daemon and clientspackages/website: Marketing site and documentation (paseo.sh)
Common commands:
# run all local dev services
npm run dev
# run individual surfaces
npm run dev:server
npm run dev:app
npm run dev:desktop
npm run dev:website
# build the server stack
npm run build:server
# repo-wide checks
npm run typecheck
Support Paseo
Paseo is an independent project used by tens of thousands of developers daily, built by one person and funded by the people who use it. Support the work on GitHub Sponsors. Companies can sponsor Paseo monthly and have their logo shown at the top of this README and on the paseo.sh homepage and docs.
Related projects
- getpaseo/paseo-relay — official distributed relay, written in Elixir
- paseo-vscode — VS Code extension
License
Apache-2.0

