* fix(app): leave providers that are not installed out of the model picker An agent's own provider stays in its selector, labelled Unavailable. * feat(app): open a provider's detail as a Settings page or a sheet Settings → Providers now pushes a provider page, like Projects and Plugins; the model picker gear and setup keep a sheet. Both frame one body, ordered error, Enabled, Installation, Models, Troubleshooting, Danger zone, so the old sheet's sticky footer and Retry button are gone. Refresh lives once, in the Troubleshooting status row. The page header (back link, icon, title) moves into the shared settings kit so projects, plugins and providers line up on the same rails. * feat(app): show each provider's version, updates and faults in the list Each row now says how its provider is: version and model count, Update available, a spinner while an update runs, a red dot with the error, or Not installed / Disabled. Only a broken provider gets a dot, and a provider that is not installed has no switch, since the model picker already leaves it out. The kebab is gone; Remove lives on the detail. Rows read the same installation and update queries as the detail, so opening a provider costs no new requests. Hosts without providerInstallation still get a correct list from the snapshot alone. Add provider is a "+ Provider" button in the header and a muted last row; both open one sheet with search and catalog rows, replacing the tile grid. After Add, the new provider's detail opens. The row is the settings kit's detail row, which gains a leading icon, a hint status (spinner, error dot, or a held line) and a control before the chevron. The Unistyles test stub now applies withUnistyles theme mappings, so browser tests render components that read colours through the theme. * feat(app): open setup's provider pages over the setup card The detail and Add provider sheets take the setup card's frame and a back arrow, so they read as pages of setup instead of a sheet over it. The step is renamed "Your providers" to match the list it shows. * docs: describe the provider list and pages as they are now * fix(app): keep settings rows one height and on one icon rail on phones On touch layouts a switch reserves a 44px control, so in the provider list rows with a switch stood 10px taller than "Not installed" rows without one. Card rows now reserve a default control's height, the rule nested rows already follow. A compact SettingsRow wrapped with a full `gap`, which added 12px on top of the leading slot's margin: catalog icons sat 24px from their labels instead of 12px. The wrap only needs space between lines, so it uses `rowGap`. * fix(app): keep a provider row's error to one line A long or multi-line error wrapped the hint to two lines with the dot centred between them. The row cuts it to one line; the provider's page shows it in full. * fix(app): title a provider's Settings page like a project's The page title and the detail header both named the provider. The screen now titles it "Providers" and the page names the provider once, the way a project's page does. * fix(app): keep a settings row's switch out of the row's button The provider row's switch rendered inside the row's <button>. That is invalid markup, and keys reached both: Enter on the switch toggled it and also opened the provider's page, and Space on it opened the page without toggling. SettingsRowHeader now lays its press target under the row's content as a sibling of the control. The content lets presses through to the button and stays out of the accessibility tree, where the button's label already names the row. Hover is tracked on the row, so it holds over the switch. * fix(app): reserve a control's height only on rows that open something The previous change gave every card row a control's minimum height and the design doc said so, but rows built directly on settingsStyles.row (66 uses) never got it: a single-line row was 48px or 64px depending on which code path built it. The minimum now belongs to SettingsRowHeader, the row with an optional control slot, so a list where only some rows carry a switch keeps one height. SettingsRow and hand-built rows take their content's height again, as on the base branch, and the doc states the narrower rule. * test(app): give the Unistyles stub the light theme's full colours Since the stub started applying withUnistyles theme mappings, a mapping reading a colour the stub's theme lacked crashed: the markdown styles read colors.terminal and failed the plan card disclosure tests. The stub's colours now start from the light theme, with its own values pinned on top. * test(app): find the provider page's buttons in the compact sheet On compact layouts AdaptiveModalSheet puts its testID on the header only, so buttons in the page body cannot be found inside it. The spec looks them up on the page, as it did before the page moved into the sheet. * fix(app): let screen readers read a settings row's state line The row's button carries the row's name as its label, so only the title is hidden from assistive tech now; the hint below it (a provider's version, error or Not installed) is read again. The Enter-on-switch test now dispatches its key events synchronously inside one act. An awaited keyboard call let the Switch's animation run a frame after the test, which Vitest reported as an unhandled error and failed the run. * fix(app): don't open a provider's page after its Add sheet was closed Adding a provider waits for the daemon to probe it. If the user closed the sheet during that wait, the completed add still navigated to the provider's page. The add now remembers which sheet session started it and only opens the page if that session is still current. * fix(app): say Not installed for a disabled provider that is not installed A disabled provider's snapshot status is unavailable, so the row said Disabled even when the binary was missing. The installation inspection is checked first, so Not installed wins over Disabled. * fix(app): keep a saved provider choice visible when it is not installed The provider picker drops unavailable providers. A schedule or metadata-generation setting saved against such a provider then showed Select model. The picker now keeps the saved provider, labelled Unavailable, so the user sees what is set and can change it. * test(app): wait for an added catalog provider's probe before continuing Adding a provider opens its page only after the daemon probes it, which can outlast the default expect timeout on CI. * refactor(app): name the provider picker's connection and saved-choice options Callers passed a bare true to reach the saved-choice argument. * fix(app): show a provider page's loading and not-found states A provider page opened from its URL (a reload, a cold start, a shared link) rendered its title over nothing until the host's providers arrived, and forever when the id named a provider the host doesn't have. The page body now says Loading..., that the host is offline, that the providers couldn't be read, or that the provider isn't on this host, in the same notice card the provider list uses when it is offline. The page and both sheet frames share the body. * fix(app): don't call a just-removed provider missing while its page closes The daemon can publish the provider list without the removed provider before it answers the config patch, so the page said "This provider isn't on this host" until the answer arrived and it navigated away; in a sheet, through the exit animation as well. A page that has shown its provider now shows nothing once it leaves the list. The not-found notice is for a page that never found its provider. The removal e2e holds the config answer so it always sees that order. * fix(app): show the not-found notice when a provider is removed elsewhere The page hid the notice for any provider it had shown before, to cover its own Remove. A removal from another client, the CLI or a plugin then left the page blank with no way to tell why. The page now owns its Remove: while that runs and once it succeeds the body shows nothing, and any other absence says the provider isn't on this host. The removal e2e routes only the e2e daemon's socket, so the fixture's port-6767 guard stays in force. * fix(app): show progress on the provider page's in-flight buttons Remove, Add model and the diagnostic re-run now show their work on the pressed control, like the page's Refresh and Update: a spinner, no further presses and, on a labelled button, "Removing..." or "Adding...". Remove kept its label and only disabled itself, and the page went blank mid-removal: the daemon publishes the provider list without the removed provider before it answers the config patch, so the body had nothing to show and each frame's title fell back to the raw id. The removal now keeps the entry the user confirmed, and one hook feeds the frame's title and the body, so both keep showing the provider until the page closes. The in-flight state also starts after confirmation, not while the dialog is open. The diagnostic sheet's header icon buttons had lost the base branch's spinner and dimming; SheetHeaderIconButton now takes loading and disabled, the way Button does. * fix(app): don't leave a re-added provider's sheet stuck on Removing... The setup step and the model picker's gear keep a provider's sheet mounted after it closes, keyed by provider. A finished removal stayed set in that sheet, so adding the same provider back reopened it with Remove spinning and disabled. A finished removal now ends when the host lists the provider again. * fix(app): keep the composer's remembered provider in its picker The picker leaves out providers that aren't installed, except the one holding the picker's current choice. The schedule form and metadata page passed that choice; the new-agent composer didn't, so a remembered provider not installed on this host vanished from the picker and the trigger read "Select model" with no reason given. The builder now requires every caller to say what its current choice is, or null. * fix(app): guide a missing catalog provider's install and keep custom models while one fails A provider added from the Add provider catalog runs through the generic ACP client, which reports no installation, so its page said nothing when the CLI was missing. The page now shows the Installation section's Not installed row with Install opening the catalog's guide. A link the host supplies still wins. Custom models live in config, so the page lists them and offers Add model whenever the provider is enabled and installed, including while it fails. The provider's own models, and the search over them, still show only while it runs. * fix(app): make settings rows pressable on iOS and Android React Native 0.86 no longer exports StyleSheet.absoluteFillObject, and Unistyles' native StyleSheet copies it from React Native, so the spread was empty there. The row's press target then had no size: on Android, tapping a provider row or a Voice row did nothing. Web was unaffected because Unistyles' web StyleSheet still defines the key. Use StyleSheet.absoluteFill, as the rest of the app does. * fix(app): let setup's provider sheets leave out the close button again The base's sheet header rewrite dropped SheetHeaderView's showCloseButton, which the provider page and Add provider sheets pass when setup's back arrow is the only way out. Restore it on the header. * test(app): prove a refresh clears a failed update from the provider's row The update-failure journey now also walks the provider list: after Refresh on the page the row reads its version and model count with no error dot, and a refresh from another client clears a row that is open in the list. Without the provider.installation.update.cleared handling both row checks fail. The helper's Refresh now uses the page's Troubleshooting button, since Settings opens the provider as a page, not a sheet. * fix(app): show a catalog provider's install guide on hosts that cannot report installations A host without providerInstallation returns an unsupported installation, which the page passed through, so a catalog provider whose CLI is missing showed no Installation section and no guide anywhere. The guide is the app's own catalog data, so the page builds the same Not installed row from it on those hosts.
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

