* fix(app): restore a host's workspaces after its cached directory is evicted A host could keep a current directory checkpoint in the replica cache with none of the rows it described. The daemon then answered "no changes" since that cursor, and the sidebar had no projects to place cached workspaces under, so every workspace for that host vanished and stayed missing across restarts. The cache already refused mutations for an evicted host, but it checked at the moment a mutation was queued. Eviction happens later, inside the serialized write, so anything queued before the eviction ran was still written, checkpoint included. The check moves into materializePendingChanges so it runs in the same serialized step that evicts, which also covers an eviction that lands while an earlier persist is still indexing the store. Checking at queue time was also losing good data: once a host was invalidated, every mutation was dropped, including updates accepted between a reconnect's baseline replacement and its write. Those are kept now, because the baseline is in the same pending batch. Version 1 checkpoints could have been written by that path, so they are no longer trusted. A reader discards them and keeps the cached rows, so the sidebar still paints from cache and each host re-syncs its directory once. Later launches resume incrementally. Both the race and the recovery live in the shared cache, so this covers iOS, Android, web, and Electron. It does not address two tabs or windows sharing one IndexedDB database, where another connection evicts the host. * fix(app): hold workspace updates that arrive while the directory cache loads A project update received while the cached directory was being read went straight into the replica. It advanced the project cursor before any refresh had established a baseline, and saved that cursor to the cache. On an install damaged before the eviction fix, that write replaced the version 1 checkpoint with a version 2 one before the reader could reject it. The refresh then asked for project changes after the live update, the daemon had none, and projects missing from the cache stayed missing across restarts. Agents already open a transaction before the cache load, so their updates are recorded and applied over the refreshed snapshot. Workspaces now do the same. An update during the load also stops the cached cursors being adopted, so the refresh fetches full snapshots, which is the recovery a damaged cache needs. * fix(app): advance directory cursors from live updates only after a refresh A live update moved the directory cursor whenever no refresh was in flight, including when no refresh had ever completed on the current subscriptions. If the first sync after discarding a version 1 checkpoint failed, the next project update saved a cursor at its own sequence with only that project stored. The retry asked for changes after it, the daemon had none, and the other projects stayed missing across restarts. The previous commit closed this window during the cache load only; a failed refresh reopened it. A live event's sequence covers everything before it only when a refresh completed on the subscriptions that delivered it, which is what satisfiedDemandSource already records. Live events now update rows either way but move the cursor only in that state, so a cursor never skips changes the client did not receive. Once a refresh completes, live updates advance the cursor as before. The sidebar recovery e2e fixture unwrapped the checkpoint only when it was version 1, so the version 2 writer made it abort before damaging the cache. It now reads either envelope and stores the damage as version 1, the format this branch stops trusting, so the test fails against the previous cache module and passes here. * fix(app): apply the eviction rule to malformed-row repairs Repairing a malformed directory row reads the checkpoint, drops the affected cursor, and writes the rest back. That write went straight to the row store through queueOperation, outside the eviction check in the regular persist path. If a write evicted the same host while the repair was reading, the repair stored a checkpoint for a host with no directory rows, the state this branch exists to prevent. All three repair writes now go through one helper that runs in the serialized writer and drops the checkpoint upsert when the host has been evicted since. The deletes still apply. * fix(app): record a host eviction only after its delete commits Eviction marked the host as evicted before deleteHost ran. If storage aborted that delete, the rows stayed stored but the mark remained. A malformed-row repair running behind it trusted the mark: it skipped the checkpoint update yet still deleted the row, leaving a workspace cursor with no workspace. The next refresh then resumed past that workspace. The mark is now set after the delete commits, so it always matches storage. A failed eviction leaves no mark, and the repair updates the row and its cursor together.
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:
Paseo also runs Cursor, Gemini CLI, and many other agents. See Supported providers for the full list and setup steps.
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

