puter/paseo
1
0
Fork 0
mirror of https://github.com/getpaseo/paseo.git synced 2026-07-29 12:01:31 +00:00
Code Issues Packages Projects Releases Wiki Activity

Rework docs navigation and move alternatives to top-level pages (#1487)

Browse Source 
* Rework docs navigation and move alternatives to top-level pages

- Add nested docs nav with categories, collapsible groups, breadcrumbs,
  and a right-hand page outline with heading slugs.
- Move alternatives out of /docs/alternatives into /alternatives/*
  marketing pages with 301 redirects.
- Add github-slugger for heading IDs and require explicit width on
  SiteShell so new pages can't accidentally pick the narrow prose layout.
- Remove the best-practices doc from public-docs.

* Make docs content column prose-width
This commit is contained in:
Mohamed Boudra
2026-06-12 20:53:30 +08:00
committed by GitHub
parent fb0c5b27f3
commit 7e46f6a647
54 changed files with 934 additions and 200 deletions
Download Patch File Download Diff File Expand all files Collapse all files

118
public-docs/alternatives/claude-desktop.md
View File

@@ -1,118 +0,0 @@
---
title: Open Source Claude Desktop Alternative With Linux, Mobile, and Multi-Provider Support
description: Paseo is an open source Claude Desktop alternative for developers who want Linux, self-hosting, native mobile apps, and Claude Code alongside Codex, OpenCode, Copilot, and more.
nav: Claude Desktop
order: 106
---
# Paseo vs Claude Desktop
Claude Desktop is Anthropic's desktop app for Claude. It includes Chat, Cowork, and Claude Code in one app. Claude Code runs in the desktop app on macOS and Windows.
Paseo is an app for orchestrating coding agents, with native clients on desktop, mobile, web, and the CLI. Open source (AGPL-3.0).
![Paseo desktop and mobile app](/hero-mockup.png)
## When to pick what
Pick Claude Desktop if you want Anthropic's first-party app for Claude, Claude Cowork, and Claude Code, with Anthropic-managed cloud sessions and the tightest Claude account integration.
Pick Paseo if you want:
- Linux alongside macOS and Windows
- A native iOS and Android app for the same agent workflow
- Claude Code, Codex, OpenCode, Copilot, Pi, and 30+ more agents in one interface
- A self-hosted daemon you can run on a laptop, VM, or dev server
- A CLI and MCP server for scripting and multi-agent workflows
- Open source you can audit and fork
## Architecture
Paseo runs a daemon on your machine. Desktop, web, mobile, and CLI clients connect to it over a websocket. The daemon launches Claude Code and other providers as local processes, using your installed CLIs, credentials, MCP servers, skills, and project config.
Claude Desktop is the host app. The Code tab can run Claude Code locally, connect over SSH, or run remote sessions on Anthropic infrastructure.
## Providers
Claude Desktop runs Claude Code.
Paseo runs Claude Code too, plus Codex, OpenCode, and Pi natively, plus 30+ more agents through the in-app catalog including GitHub Copilot, Cursor, Gemini CLI, and Amp. Paseo speaks the [Agent Client Protocol](https://agentclientprotocol.com), so any ACP agent works. Custom providers run any CLI agent. See [Supported providers](/docs/supported-providers).
## Desktop platforms
Claude Desktop is available on macOS and Windows. Anthropic lists Linux as not available.
Paseo ships on macOS, Linux, and Windows.
## Mobile
Paseo ships native iOS and Android apps with the same agent workflow as the desktop app.
Claude has iOS and Android apps. Claude Code can be controlled from mobile through Remote Control, and Claude Desktop can pair with mobile for some workflows.
## Panes
Both tools support visual coding workflows around Claude Code.
Paseo's app has split panes and tabs (⌘D for vertical, ⌘⇧D for horizontal). Panes include agents, terminals, a diff viewer, and a browser for testing running services.
Claude Desktop has a graphical Code tab with sessions, integrated terminal, file editor, visual diff review, live app preview, PR monitoring, and scheduled tasks.
## GitHub
Paseo's app handles commit, push, opening PRs, watching checks and reviews, and merging.
Claude Desktop can monitor pull request status and can fix failures or merge when checks pass, depending on the workflow and permissions.
## CLI and automation
Claude Code has its own CLI, IDE integrations, web surface, scheduled tasks, and cloud sessions.
Paseo's CLI controls the same daemon as the app:
```bash
paseo run --provider claude "implement OAuth"
paseo run --provider codex --worktree refactor-auth "refactor auth"
paseo run --host devbox:6767 "run the test suite"
paseo ls
paseo send <agent-id> "add tests"
paseo schedule create --cron "0 9 * * 1" "audit the codebase"
```
`paseo run --host` connects to a remote daemon. `paseo schedule` runs an agent on a cron. `paseo loop` retries an agent until a verification command passes. The MCP server lets other agents create worktrees, launch agents, open terminals, and send prompts.
## Worktrees and services
Both tools support parallel coding sessions, including Git worktrees.
Paseo also gives each worktree its own dev server URL. Two agents running their dev servers at the same time get `web.fix-auth.my-app.localhost` and `web.add-search.my-app.localhost` instead of port collisions.
## Voice
Paseo supports dictation and realtime voice mode. Speech-to-text and text-to-speech can run locally on your device.
Claude supports voice in Claude's own mobile and app surfaces. Claude Code itself is available in Claude Desktop, terminal, IDE, web, and mobile Remote Control workflows.
## Comparison
| | Paseo | Claude Desktop |
| ---------------------------- | --------------------------------------------------------------- | --------------------------------- |
| License | Open source (AGPL-3.0) | Not published as open source |
| Desktop platforms | macOS, Linux, Windows | macOS, Windows |
| Native mobile | iOS, Android | iOS, Android Claude apps |
| Coding agents | Claude Code, Codex, OpenCode, Pi + 30+ via ACP catalog + custom | Claude Code |
| General chat | No | Claude Chat |
| Cloud agent | Cloud waitlist | Claude Cowork and remote sessions |
| Local execution | Yes | Yes |
| SSH remote execution | Via daemon on the remote host | Yes |
| Git worktrees | Yes | Yes |
| Per-worktree dev server URLs | Yes | No |
| Split panes and tabs | Yes | Yes |
| In-app terminal | Yes | Yes |
| In-app browser / preview | Yes | Yes |
| GitHub workflow in app | Commit, push, PR, checks, reviews, merge | PR monitoring and merge workflows |
| CLI | Run, `--host`, ls, send, schedule, loop | Claude Code CLI |
| MCP server for orchestration | Yes | MCP support inside Claude Code |
| Self-hosted daemon | Yes | No |
See also: [Paseo vs Codex App](/docs/alternatives/codex-app), [Paseo vs OpenCode Desktop](/docs/alternatives/opencode-desktop), [Paseo vs Conductor](/docs/alternatives/conductor).

110
public-docs/alternatives/codex-app.md
View File

@@ -1,110 +0,0 @@
---
title: Open Source Codex App Alternative With Linux, Mobile, and Multi-Provider Support
description: Paseo is an open source alternative to Codex App for developers who want Linux, native mobile apps, a self-hosted daemon, and Codex alongside Claude Code, OpenCode, Copilot, and more.
nav: Codex App
order: 105
---
# Paseo vs Codex App
Codex App is OpenAI's desktop app for working with Codex threads in parallel. It runs on macOS and Windows, with local, worktree, and cloud modes.
Paseo is an app for orchestrating coding agents, with native clients on desktop, mobile, web, and the CLI. Open source (AGPL-3.0).
![Paseo desktop and mobile app](/hero-mockup.png)
## When to pick what
Pick Codex App if you want OpenAI's first-party app for Codex, with Codex-specific features like cloud threads, appshots, image generation, and computer use on macOS.
Pick Paseo if you want:
- Linux alongside macOS and Windows
- A native iOS and Android app
- Codex, Claude Code, OpenCode, Copilot, Pi, and 30+ more agents in one interface
- A self-hosted daemon you can run on a laptop, VM, or dev server
- A CLI and MCP server for scripting and multi-agent workflows
- Open source you can audit and fork
## Architecture
Paseo runs a daemon on your machine. Desktop, web, mobile, and CLI clients connect to it over a websocket. The daemon launches Codex and other providers as local processes, using your installed CLIs and credentials.
Codex App is a desktop app for Codex. It can run local and worktree threads on your computer, and cloud threads on OpenAI-managed infrastructure.
## Providers
Codex App runs Codex.
Paseo runs Codex too, plus Claude Code, OpenCode, and Pi natively, plus 30+ more agents through the in-app catalog including GitHub Copilot, Cursor, Gemini CLI, and Amp. Paseo speaks the [Agent Client Protocol](https://agentclientprotocol.com), so any ACP agent works. Custom providers run any CLI agent. See [Supported providers](/docs/supported-providers).
## Desktop platforms
Codex App is available on macOS and Windows. OpenAI lists Linux as not available yet.
Paseo ships on macOS, Linux, and Windows.
## Mobile
Paseo ships native iOS and Android apps with the same agent workflow as the desktop app.
Codex can be controlled remotely through OpenAI's mobile surfaces, including ChatGPT mobile remote connections. Codex App itself is a desktop app.
## Worktrees and local setup
Both tools support Git worktrees for parallel work.
Codex App creates Codex-managed worktrees under `$CODEX_HOME/worktrees` and supports local environment setup scripts and project actions through `.codex` configuration.
Paseo creates worktrees under `$PASEO_HOME/worktrees`, runs setup and teardown hooks from `paseo.json`, and gives each worktree its own dev server URLs like `web.fix-auth.my-app.localhost` so parallel services don't fight for ports.
## GitHub and review
Both tools support reviewing diffs, committing, pushing, and opening pull requests from the app.
Paseo also surfaces PR checks and reviews in the app, and exposes the same workflow through the CLI and MCP server.
## CLI and automation
Codex has its own CLI, IDE extension, web app, automations, and SDK.
Paseo's CLI controls the same daemon as the app:
```bash
paseo run --provider codex "implement OAuth"
paseo run --provider claude --worktree refactor-auth "refactor auth"
paseo run --host devbox:6767 "run the test suite"
paseo ls
paseo send <agent-id> "add tests"
paseo schedule create --cron "0 9 * * 1" "audit the codebase"
```
`paseo run --host` connects to a remote daemon. `paseo schedule` runs an agent on a cron. `paseo loop` retries an agent until a verification command passes. The MCP server lets other agents create worktrees, launch agents, open terminals, and send prompts.
## Voice
Codex App supports voice dictation.
Paseo supports dictation and realtime voice mode. Speech-to-text and text-to-speech can run locally on your device.
## Comparison
| | Paseo | Codex App |
| ---------------------------- | --------------------------------------------------------------- | ---------------------------- |
| License | Open source (AGPL-3.0) | Not published as open source |
| Desktop platforms | macOS, Linux, Windows | macOS, Windows |
| Native mobile | iOS, Android | No |
| Providers | Codex, Claude Code, OpenCode, Pi + 30+ via ACP catalog + custom | Codex |
| Local execution | Yes | Yes |
| Cloud execution | Cloud waitlist | Yes |
| Git worktrees | Yes | Yes |
| Per-worktree dev server URLs | Yes | No |
| In-app terminal | Yes | Yes |
| In-app browser | Yes | Yes |
| GitHub workflow in app | Commit, push, PR, checks, reviews, merge | Commit, push, PR |
| CLI | Run, `--host`, ls, send, schedule, loop | Codex CLI |
| MCP server for orchestration | Yes | MCP support inside Codex |
| Voice | Dictation and realtime voice | Dictation |
| Self-hosted daemon | Yes | No |
See also: [Paseo vs Claude Desktop](/docs/alternatives/claude-desktop), [Paseo vs OpenCode Desktop](/docs/alternatives/opencode-desktop), [Supported providers](/docs/supported-providers).

97
public-docs/alternatives/conductor.md
View File

@@ -1,97 +0,0 @@
---
title: Open Source Conductor Alternative With Linux, Windows, and Mobile
description: Paseo is open source, runs on macOS, Linux, and Windows, ships native iOS and Android apps, and supports 30+ agents through the in-app catalog plus any ACP or CLI agent. Conductor is macOS only and Claude Code or Codex only.
nav: Conductor
order: 100
---
# Paseo vs Conductor
Conductor is a macOS app for running Claude Code and Codex in parallel git worktrees. Closed source.
Paseo is an app for orchestrating coding agents, with native clients on desktop, mobile, web, and the CLI. Open source (AGPL-3.0).
![Paseo desktop and mobile app](/hero-mockup.png)
## Why pick Paseo
Conductor runs on macOS, with Claude Code and Codex, in parallel git worktrees. Paseo does all of that. Pick Paseo if you want:
- Linux or Windows alongside macOS
- A native iOS and Android app
- Many more agents than Claude Code and Codex
- A CLI to script agent work and drive remote daemons
- A self-hosted daemon you can run on a server, VM, or homelab
- Open source you can audit and fork
## Architecture
The Paseo daemon runs as its own process. Desktop, web, mobile, and CLI all connect to it over a websocket. Run the daemon on your laptop, on a VM, in Docker, or across a fleet, and connect to any of them from any client.
Conductor's desktop app is the host. Agents run inside it.
## Providers
Paseo runs Claude Code, Codex, OpenCode, and Pi natively, plus 30+ more agents through the in-app catalog including GitHub Copilot, Cursor, Gemini CLI, and Amp. Paseo speaks the [Agent Client Protocol](https://agentclientprotocol.com), so any ACP agent works. Custom providers run any CLI agent. See [Supported providers](/docs/supported-providers).
Conductor runs Claude Code and Codex.
Both tools launch the official CLIs as subprocesses with your own credentials. Neither extracts tokens or proxies model calls.
## Panes
Paseo's app has split panes and tabs (⌘D for vertical, ⌘⇧D for horizontal). Panes include a terminal alongside your agents, a diff viewer, and a browser for testing running services.
## GitHub
Paseo's app handles commit, push, opening PRs, watching checks and reviews, and merging.
## CLI
Paseo has a CLI that mirrors the app:
```bash
paseo run --provider codex "implement OAuth"
paseo run --host devbox:6767 "run the test suite"
paseo ls
paseo send <agent-id> "add tests"
paseo schedule create --cron "0 9 * * 1" "audit the codebase"
```
`paseo run --host` connects to a remote daemon. `paseo schedule` runs an agent on a cron. `paseo loop` retries an agent until a verification command passes.
Conductor does not have a CLI.
## Worktrees and services
Both tools isolate parallel agents in git worktrees.
Paseo also gives each worktree its own dev server URL. Two agents running their dev servers at the same time get `web.fix-auth.my-app.localhost` and `web.add-search.my-app.localhost` instead of port collisions.
## Mobile
Paseo ships native iOS and Android apps with the same feature set as the desktop app. Conductor has no mobile app.
## Voice
Paseo's speech-to-text and text-to-speech run locally on your device. Nothing leaves your network. Conductor does not have voice.
## Comparison
| | Paseo | Conductor |
| ---------------------------- | --------------------------------------------------------------- | ------------------ |
| License | Open source (AGPL-3.0) | Closed source |
| Platforms | macOS, Linux, Windows | macOS only |
| Native mobile | iOS, Android | — |
| Providers | Claude Code, Codex, OpenCode, Pi + 30+ via ACP catalog + custom | Claude Code, Codex |
| Git worktrees | Yes | Yes |
| Per-worktree dev server URLs | Yes | — |
| Split panes and tabs | Yes | — |
| In-app terminal | Yes | Yes |
| In-app browser | Yes | — |
| GitHub workflow in app | Commit, push, PR, checks, reviews, merge | Yes |
| CLI | Run, `--host`, ls, send, schedule, loop | — |
| Local voice (on-device) | Yes | — |
| Self-hosted daemon | Yes | — |
See also: [Paseo vs Superset](/docs/alternatives/superset), [Paseo vs OpenChamber](/docs/alternatives/openchamber), [Paseo vs Happy Coder](/docs/alternatives/happy-coder).

99
public-docs/alternatives/happy-coder.md
View File

@@ -1,99 +0,0 @@
---
title: Happy Coder Alternative With a Desktop App and Git Worktrees
description: Paseo ships a native desktop app, runs agents in isolated git worktrees, and supports 30+ agents. Happy Coder is mobile and web only, wraps the agent CLI, and supports Claude Code and Codex.
nav: Happy Coder
order: 104
---
# Paseo vs Happy Coder
Happy Coder is a mobile and web client for Claude Code and Codex. It wraps the agent CLI on your laptop and syncs sessions to phone and browser over an end-to-end encrypted relay. Open source under MIT.
Paseo is an app for orchestrating coding agents, with native clients on desktop, mobile, web, and the CLI. Open source (AGPL-3.0).
![Paseo desktop and mobile app](/hero-mockup.png)
## When to pick what
Pick Happy Coder if you want the most minimal setup. Wrap an existing Claude Code or Codex session on your laptop and check in on it from your phone.
Pick Paseo if you want:
- A native desktop app on macOS, Linux, and Windows
- Git worktrees for parallel agents
- Per-worktree dev server URLs
- GitHub PRs, checks, reviews, and merges in the app
- Many more agents than Claude Code and Codex
- A CLI to script agent work and drive remote daemons
## Architecture
Paseo runs the agent inside its own daemon. The daemon owns the agent lifecycle, the worktree, and the dev servers. Clients connect over a websocket and drive the daemon.
Happy Coder runs the agent inside its existing CLI on your laptop and syncs the session to its mobile and web clients through an end-to-end encrypted relay.
## Panes
Paseo's app has split panes and tabs (⌘D for vertical, ⌘⇧D for horizontal). Panes include a terminal alongside your agents, a diff viewer, and a browser for testing running services.
Happy Coder does not have a desktop app.
## GitHub
Paseo's app handles commit, push, opening PRs, watching checks and reviews, and merging.
## Mobile
Both tools ship native iOS and Android apps.
## Providers
Paseo runs Claude Code, Codex, OpenCode, and Pi natively, plus 30+ more agents through the in-app catalog including GitHub Copilot, Cursor, Gemini CLI, and Amp. Paseo speaks the [Agent Client Protocol](https://agentclientprotocol.com), so any ACP agent works. Custom providers run any CLI agent. See [Supported providers](/docs/supported-providers).
Happy Coder runs Claude Code and Codex.
## Worktrees and services
Paseo runs each agent in its own git worktree. Each worktree gets its own dev server URL like `web.fix-auth.my-app.localhost`, so parallel agents don't fight for the same port.
Happy Coder runs the agent in the directory you launched the CLI from.
## CLI
Paseo has a CLI that mirrors the app:
```bash
paseo run --provider codex "implement OAuth"
paseo run --host devbox:6767 "run the test suite"
paseo ls
paseo send <agent-id> "add tests"
paseo schedule create --cron "0 9 * * 1" "audit the codebase"
```
`paseo run --host` connects to a remote daemon. `paseo schedule` runs an agent on a cron. `paseo loop` retries an agent until a verification command passes.
Happy Coder has a CLI to launch the wrapped session. It does not have schedules or loops.
## Voice
Paseo's speech-to-text and text-to-speech run locally on your device. Nothing leaves your network.
## Comparison
| | Paseo | Happy Coder |
| ---------------------------- | --------------------------------------------------------------- | ---------------------- |
| License | Open source (AGPL-3.0) | Open source (MIT) |
| Desktop app | macOS, Linux, Windows | — |
| Native mobile | iOS, Android | iOS, Android |
| Architecture | Daemon owns agent lifecycle | Wraps the agent CLI |
| Providers | Claude Code, Codex, OpenCode, Pi + 30+ via ACP catalog + custom | Claude Code, Codex |
| Split panes and tabs | Yes | — |
| In-app terminal | Yes | — |
| In-app browser | Yes | — |
| GitHub workflow in app | Commit, push, PR, checks, reviews, merge | — |
| Git worktrees | Yes | — |
| Per-worktree dev server URLs | Yes | — |
| CLI | Run, `--host`, ls, send, schedule, loop | Launch wrapped session |
| Local voice (on-device) | Yes | — |
See also: [Paseo vs Conductor](/docs/alternatives/conductor), [Paseo vs Superset](/docs/alternatives/superset), [Paseo vs OpenChamber](/docs/alternatives/openchamber).

93
public-docs/alternatives/openchamber.md
View File

@@ -1,93 +0,0 @@
---
title: OpenChamber Alternative With Linux, Windows, and Mobile
description: Paseo ships native iOS and Android apps, runs on macOS, Linux, and Windows, and supports 30+ agents. OpenChamber is macOS only with a PWA and is built around OpenCode.
nav: OpenChamber
order: 103
---
# Paseo vs OpenChamber
OpenChamber is a macOS desktop app for OpenCode. Also available as a PWA. Open source under MIT.
Paseo is an app for orchestrating coding agents, with native clients on desktop, mobile, web, and the CLI. Open source (AGPL-3.0).
![Paseo desktop and mobile app](/hero-mockup.png)
## Why pick Paseo
OpenChamber runs on macOS, around OpenCode, with a phone PWA. Paseo runs OpenCode too, on macOS, and adds:
- Linux and Windows desktop
- A native iOS and Android app
- Many more agents than OpenCode (Claude Code, Codex, Pi, plus 30+ more via the in-app ACP catalog)
- A scriptable CLI to drive agents and connect to remote daemons
## Mobile
Paseo ships a native iOS and Android app with the same feature set as the desktop. Install from the App Store or Google Play.
OpenChamber does not have a native mobile app.
## Desktop
Paseo ships on macOS, Linux, and Windows.
OpenChamber ships on macOS.
## Providers
Paseo runs Claude Code, Codex, OpenCode, and Pi natively, plus 30+ more agents through the in-app catalog including GitHub Copilot, Cursor, Gemini CLI, and Amp. Paseo speaks the [Agent Client Protocol](https://agentclientprotocol.com), so any ACP agent works. Custom providers run any CLI agent. See [Supported providers](/docs/supported-providers).
OpenChamber is built around OpenCode.
## Panes
Paseo's app has split panes and tabs (⌘D for vertical, ⌘⇧D for horizontal). Panes include a terminal alongside your agents, a diff viewer, and a browser for testing running services.
## GitHub
Paseo's app handles commit, push, opening PRs, watching checks and reviews, and merging.
## CLI
Paseo has a CLI that mirrors the app:
```bash
paseo run --provider codex "implement OAuth"
paseo run --host devbox:6767 "run the test suite"
paseo ls
paseo send <agent-id> "add tests"
paseo schedule create --cron "0 9 * * 1" "audit the codebase"
```
`paseo run --host` connects to a remote daemon. `paseo schedule` runs an agent on a cron. `paseo loop` retries an agent until a verification command passes.
OpenChamber does not have a CLI.
## Worktrees and services
Paseo runs each agent in its own git worktree. Each worktree gets its own dev server URL like `web.fix-auth.my-app.localhost`, so parallel agents don't fight for ports.
## Voice
Paseo's speech-to-text and text-to-speech run locally on your device. OpenChamber does not have voice.
## Comparison
| | Paseo | OpenChamber |
| ---------------------------- | --------------------------------------------------------------- | ----------------- |
| License | Open source (AGPL-3.0) | Open source (MIT) |
| Desktop platforms | macOS, Linux, Windows | macOS |
| Mobile | Native iOS, Android | PWA |
| Providers | Claude Code, Codex, OpenCode, Pi + 30+ via ACP catalog + custom | OpenCode |
| Split panes and tabs | Yes | — |
| In-app terminal | Yes | — |
| In-app browser | Yes | — |
| GitHub workflow in app | Commit, push, PR, checks, reviews, merge | Yes |
| CLI | Run, `--host`, ls, send, schedule, loop | — |
| Git worktrees | Yes | Yes |
| Per-worktree dev server URLs | Yes | — |
| Local voice (on-device) | Yes | — |
| Self-hosted daemon | Yes | — |
See also: [Paseo vs Conductor](/docs/alternatives/conductor), [Paseo vs Superset](/docs/alternatives/superset), [Paseo vs Happy Coder](/docs/alternatives/happy-coder).

116
public-docs/alternatives/opencode-desktop.md
View File

@@ -1,116 +0,0 @@
---
title: OpenCode Desktop Alternative With Native Mobile and Multi-Provider Orchestration
description: Paseo is an OpenCode Desktop alternative for developers who want native mobile apps, a self-hosted daemon, and OpenCode alongside Claude Code, Codex, Copilot, and more.
nav: OpenCode Desktop
order: 107
---
# Paseo vs OpenCode Desktop
OpenCode Desktop is the desktop app for OpenCode. It is available in beta for macOS, Windows, and Linux.
Paseo is an app for orchestrating coding agents, with native clients on desktop, mobile, web, and the CLI. Open source (AGPL-3.0).
![Paseo desktop and mobile app](/hero-mockup.png)
## When to pick what
Pick OpenCode Desktop if you want the OpenCode app, the OpenCode terminal workflow, and OpenCode's multi-model provider system.
Pick Paseo if you want:
- A native iOS and Android app
- OpenCode beside Claude Code, Codex, Copilot, Pi, and 30+ more agents
- First-party harnesses for Claude Code and Codex instead of one agent runtime for everything
- A self-hosted daemon you can run on a laptop, VM, or dev server
- GitHub PRs, checks, reviews, and merges in the app
- A CLI and MCP server for scripting and multi-agent workflows
## Architecture
Paseo runs a daemon on your machine. Desktop, web, mobile, and CLI clients connect to it over a websocket. The daemon launches OpenCode and other providers as local processes, using your installed CLIs and credentials.
OpenCode Desktop is the desktop app for OpenCode. OpenCode is available as a terminal interface, desktop app, IDE extension, web surface, and integrations.
## Providers
OpenCode is a multi-model coding agent. It can connect to many LLM providers through its own provider system, including OpenCode Zen, local models, and API providers.
Paseo is multi-provider at the agent harness layer. It runs OpenCode, Claude Code, Codex, and Pi natively, plus 30+ more agents through the in-app catalog including GitHub Copilot, Cursor, Gemini CLI, and Amp. Paseo speaks the [Agent Client Protocol](https://agentclientprotocol.com), so any ACP agent works. Custom providers run any CLI agent. See [Supported providers](/docs/supported-providers).
## Desktop platforms
Both tools ship on macOS, Linux, and Windows.
## Mobile
Paseo ships native iOS and Android apps with the same agent workflow as the desktop app.
OpenCode Desktop is a desktop app. OpenCode also has web and share-link workflows, but not a native mobile app.
## Panes
Paseo's app has split panes and tabs (⌘D for vertical, ⌘⇧D for horizontal). Panes include agents, terminals, a diff viewer, and a browser for testing running services.
OpenCode is available in terminal, IDE, and desktop surfaces. Its core workflow centers on OpenCode sessions.
## GitHub
Paseo's app handles commit, push, opening PRs, watching checks and reviews, and merging.
OpenCode has GitHub and GitLab integrations, and OpenCode sessions can make and review code changes through its agent workflow.
## CLI and automation
OpenCode has its own terminal interface, CLI, IDE extension, GitHub and GitLab integrations, and share links.
Paseo's CLI controls the same daemon as the app:
```bash
paseo run --provider opencode "implement OAuth"
paseo run --provider claude --worktree refactor-auth "refactor auth"
paseo run --host devbox:6767 "run the test suite"
paseo ls
paseo send <agent-id> "add tests"
paseo schedule create --cron "0 9 * * 1" "audit the codebase"
```
`paseo run --host` connects to a remote daemon. `paseo schedule` runs an agent on a cron. `paseo loop` retries an agent until a verification command passes. The MCP server lets other agents create worktrees, launch agents, open terminals, and send prompts.
## Worktrees and services
Paseo runs each agent in its own Git worktree. Each worktree gets its own dev server URL like `web.fix-auth.my-app.localhost`, so parallel agents don't fight for ports.
OpenCode supports multi-session work on the same project. If you want worktree isolation around OpenCode sessions, Paseo can provide that by launching OpenCode inside Paseo workspaces.
## Privacy and source
Both tools are open source.
Paseo is AGPL-3.0 and runs your agents through a daemon you control. OpenCode is open source and says it does not store your code or context data by default. OpenCode share links are public when you create them.
## Voice
Paseo supports dictation and realtime voice mode. Speech-to-text and text-to-speech can run locally on your device.
## Comparison
| | Paseo | OpenCode Desktop |
| ---------------------------- | --------------------------------------------------------------- | ------------------------------- |
| License | Open source (AGPL-3.0) | Open source |
| Desktop platforms | macOS, Linux, Windows | macOS, Linux, Windows |
| Native mobile | iOS, Android | No |
| Agent harnesses | Claude Code, Codex, OpenCode, Pi + 30+ via ACP catalog + custom | OpenCode |
| Multi-model support | Through supported agent harnesses | Through OpenCode providers |
| Git worktrees | Yes | No built-in worktree manager |
| Per-worktree dev server URLs | Yes | No |
| Split panes and tabs | Yes | Desktop sessions |
| In-app terminal | Yes | OpenCode terminal workflow |
| In-app browser | Yes | No |
| GitHub workflow in app | Commit, push, PR, checks, reviews, merge | GitHub integration |
| CLI | Run, `--host`, ls, send, schedule, loop | OpenCode CLI |
| MCP server for orchestration | Yes | MCP support inside OpenCode |
| Local voice | Yes | No |
| Self-hosted daemon | Yes | OpenCode server / local runtime |
See also: [Paseo vs Codex App](/docs/alternatives/codex-app), [Paseo vs Claude Desktop](/docs/alternatives/claude-desktop), [Paseo vs OpenChamber](/docs/alternatives/openchamber).

116
public-docs/alternatives/superset.md
View File

@@ -1,116 +0,0 @@
---
title: Superset Alternative With Linux, Windows, and Mobile
description: Paseo is open source under an OSI license, has no login wall, ships native mobile, and runs on macOS, Linux, and Windows. Superset is source-available, macOS only, and gates the desktop app on a Superset login.
nav: Superset
order: 101
---
# Paseo vs Superset
Superset is a macOS desktop app for running CLI coding agents in parallel git worktrees. Source-available under the Elastic License 2.0.
Paseo is an app for orchestrating coding agents, with native clients on desktop, mobile, web, and the CLI. Open source (AGPL-3.0).
![Paseo desktop and mobile app](/hero-mockup.png)
## When to pick what
Pick Superset if you prefer a terminal-first interface where agents live inside terminal panes.
Pick Paseo if you want:
- An OSI-approved open source license (AGPL-3.0)
- Linux or Windows
- A native mobile app
- No login wall
- A per-agent UI with modes, slash commands, and file pickers
- Free without seat limits
## License
Paseo is open source under AGPL-3.0. Audit it, fork it, redistribute it.
Superset is source-available under the Elastic License 2.0. The source is on GitHub, but the license restricts hosting it as a service and limits redistribution.
## Login
Superset's desktop app shows a Superset login wall on first launch. A Superset account is required to use it.
Paseo does not require any login.
## Architecture
The Paseo daemon runs as its own process. Desktop, web, mobile, and CLI clients connect to it. Run the daemon on your laptop, on a server, or in Docker, and connect from anywhere.
Superset's desktop is the host. Agents run inside it.
## Providers
Both tools support many agents. Superset is a terminal multiplexer where each agent runs inside a terminal pane. Paseo runs Claude Code, Codex, OpenCode, and Pi natively with a per-agent UI (modes, slash commands, file picker, diff viewer), plus 30+ more agents through the in-app catalog via ACP, plus any custom CLI agent. See [Supported providers](/docs/supported-providers).
## Panes
Paseo's app has split panes and tabs. Panes include a diff viewer and a browser for testing running services. Agents render as native UI with modes, slash commands, and file pickers.
In Superset, each agent runs inside a terminal pane.
## GitHub
Paseo's app handles commit, push, opening PRs, watching checks and reviews, and merging.
## CLI
Paseo has a CLI that mirrors the app:
```bash
paseo run --provider codex "implement OAuth"
paseo run --host devbox:6767 "run the test suite"
paseo ls
paseo send <agent-id> "add tests"
paseo schedule create --cron "0 9 * * 1" "audit the codebase"
```
`paseo run --host` connects to a remote daemon. `paseo schedule` runs an agent on a cron. `paseo loop` retries an agent until a verification command passes.
Superset is a desktop app and does not have a CLI.
## Worktrees and services
Both tools isolate parallel agents in git worktrees.
Paseo also gives each worktree its own dev server URL like `web.fix-auth.my-app.localhost`, so parallel agents don't fight for ports.
## Mobile
Paseo ships native iOS and Android apps with the same feature set as the desktop. Superset does not have a mobile app.
## Voice
Paseo's speech-to-text and text-to-speech run locally on your device. Superset does not have voice.
## Pricing
Paseo is free with no seat limits.
Superset is free for one seat with local workspaces only. Team features and sync start at $20 per seat per month.
## Comparison
| | Paseo | Superset |
| ---------------------------- | ----------------------------------------------------- | -------------------------------------- |
| License | Open source (AGPL-3.0) | Source-available (Elastic License 2.0) |
| Platforms | macOS, Linux, Windows | macOS only |
| Native mobile | iOS, Android | — |
| Login required | No | Yes (Superset account) |
| Pricing | Free | Free 1 seat, $20/seat/mo Pro |
| Per-agent native UI | Yes (modes, slash commands, file picker, diff viewer) | Terminal output |
| Split panes and tabs | Yes | Yes (terminals) |
| In-app browser | Yes | — |
| GitHub workflow in app | Commit, push, PR, checks, reviews, merge | Yes |
| Git worktrees | Yes | Yes |
| Per-worktree dev server URLs | Yes | — |
| CLI | Run, `--host`, ls, send, schedule, loop | — |
| Local voice (on-device) | Yes | — |
| Self-hosted daemon | Yes | — |
See also: [Paseo vs Conductor](/docs/alternatives/conductor), [Paseo vs OpenChamber](/docs/alternatives/openchamber), [Paseo vs Happy Coder](/docs/alternatives/happy-coder).

56
public-docs/best-practices.md
View File

@@ -1,56 +0,0 @@
---
title: Best practices
description: Tips for getting the most out of Paseo and mobile-first agent workflows.
nav: Best practices
order: 17
---
# Best practices
What I've learned from using Paseo daily. Not rules, just patterns that have worked for me.
## Agents replace typing, not thinking
Your role has changed. You're no longer the one writing code line by line. You're the one making decisions: what to build, how it should work, what the architecture looks like. The agent executes, but you direct.
You can't just say "implement feature X" and walk away. You still have to do the hard part: deciding what to build, how it fits into the system, what trade-offs to make. Thinking is not optional. At least for now, agents replace the typing, not the thinking.
## Verification loops
The agent needs a way to verify its work. TDD is one implementation of this pattern: get the agent to write a failing test, verify it fails for the right reasons, then tell it to make the test pass. The agent can loop on its own because it knows what "done" means.
## Invest in tooling
It's not just test runners. For web apps, something like Playwright MCP lets the agent take screenshots and verify UI changes. For a SaaS app I built a CLI that wraps all the business logic so the agent could launch jobs, check statuses, and scrape data without going through the UI.
Code is cheap with coding agents. I would have never written that CLI before because it felt like wasted effort. Now I bootstrap tooling first. It pays off exponentially.
## Agents are cheap
Don't be shy about running multiple agents. Paseo lets you launch agents in isolated worktrees. Kick one off with voice while walking, then kick off another. They work independently. You get a notification when they're done.
## Use voice extensively
It's much more natural to use voice to communicate ideas and pull them out of your brain. The agent will parse and organize your thoughts better than if you try to write the perfect prompt. You don't need to organize anything. Just talk.
Current speech-to-text models are really good. They catch accents, acronyms, technical terms. And even when they don't, the LLM will infer what you meant.
## Understand the type of work
Sometimes you need to plan: design a spec, verify it, get the agent to follow through. Maybe it takes a couple of agents to work through it. Other times it's conversational: kick off a single agent and start talking, asking questions. Match your approach to the task.
## Iterate and refactor often
Don't expect perfect. Expect working. Make it work, make it correct, make it beautiful. Each iteration gets you closer. With tests, refactoring is cheap.
I don't let myself add too many features before stopping to refactor. Sometimes I kick off an agent and have it trace code paths, explain dependencies, show me how modules connect. I make mental notes during code review and circle back.
## Use agents to check agents
If an agent implements something and you ask it to review its own work, it will never find issues. Launch a separate agent with a fresh context to review the first agent's code. It will catch things the first agent missed or glossed over. An agent might say it's done when it's not. Another agent can detect that.
## Learn your agents' quirks
People argue about which model is better. That's the wrong question. Each model has strengths and weaknesses. Knowing them is more useful than chasing benchmarks. Benchmarks don't mean anything. You need to try the models yourself to form an opinion.
I use Claude Code as my main driver because it's quick and uses tools well. But sometimes it jumps to conclusions and gives up too easily. Codex is frustratingly slow but goes deep, doesn't stop, and is methodical. It's also stubborn and too serious. These aren't good or bad traits, just differences you learn to work around. Use the right model for the job.

5
public-docs/claude-code.md
View File

@@ -2,7 +2,8 @@
title: Claude Code
description: How Paseo runs Claude Code and how Anthropic's usage policy applies.
nav: Claude Code
order: 7
order: 23
category: Providers
---
# Claude Code
@@ -57,4 +58,4 @@ Paseo has first-class terminal support. You can run Claude Code in your terminal
- [Anthropic: Use the Claude Agent SDK with your Claude plan](https://support.claude.com/en/articles/15036540-use-the-claude-agent-sdk-with-your-claude-plan)
- [Custom providers](/docs/custom-providers), for custom binaries, third-party endpoints, or multiple Claude profiles.
- [Supported providers](/docs/supported-providers), for other agents you can run alongside Claude Code.
- [Paseo vs Claude Desktop](/docs/alternatives/claude-desktop), for a feature comparison.
- [Paseo vs Claude Desktop](/alternatives/claude-desktop), for a feature comparison.

3
public-docs/cli.md
View File

@@ -2,7 +2,8 @@
title: CLI
description: "Paseo CLI reference: manage agents, daemons, permissions, and worktrees from your terminal."
nav: CLI
order: 8
order: 3
category: Getting started
---
# CLI

3
public-docs/configuration.md
View File

@@ -2,7 +2,8 @@
title: Configuration
description: Configure Paseo via config.json, environment variables, and CLI overrides.
nav: Configuration
order: 14
order: 40
category: Configuration
---
# Configuration

3
public-docs/custom-providers.md
View File

@@ -2,7 +2,8 @@
title: Custom providers
description: Configure custom providers, alternative endpoints, profiles, custom binaries, and ACP agents in ~/.paseo/config.json.
nav: Custom providers
order: 7
order: 22
category: Providers
---
# Custom providers

1
public-docs/index.md
View File

@@ -3,6 +3,7 @@ title: Getting started
description: Install Paseo and start running coding agents from anywhere.
nav: Getting started
order: 1
category: Getting started
---
# Getting started

3
public-docs/mcp.md
View File

@@ -2,7 +2,8 @@
title: Paseo MCP
description: Paseo MCP tools injected into agents.
nav: Paseo MCP
order: 9
order: 30
category: Automation
---
# Paseo MCP

3
public-docs/metadata-generation.md
View File

@@ -2,7 +2,8 @@
title: Metadata generation
description: How Paseo uses providers to generate agent titles, branch names, commit messages, and pull request text, and how to configure them.
nav: Metadata generation
order: 15
order: 42
category: Configuration
---
# Metadata generation

3
public-docs/providers.md
View File

@@ -2,7 +2,8 @@
title: Providers
description: How Paseo thinks about coding agents, wrapping existing CLIs, native vs ACP support, and where to go next.
nav: Providers
order: 5
order: 20
category: Providers
---
# Providers

3
public-docs/schedules.md
View File

@@ -2,7 +2,8 @@
title: Schedules
description: Run Paseo agents on intervals or cron.
nav: Schedules
order: 11
order: 31
category: Automation
---
# Schedules

3
public-docs/security.md
View File

@@ -2,7 +2,8 @@
title: Security
description: "Security model for Paseo: architecture overview, connection methods, relay encryption, and best practices."
nav: Security
order: 16
order: 4
category: Getting started
---
# Security

3
public-docs/skills.md
View File

@@ -2,7 +2,8 @@
title: Orchestration skills
description: "Paseo orchestration skills: teach coding agents to spawn, coordinate, and manage other agents using slash commands."
nav: Skills
order: 12
order: 32
category: Automation
---
# Orchestration skills

3
public-docs/supported-providers.md
View File

@@ -2,7 +2,8 @@
title: Supported providers
description: Every coding agent Paseo can launch, natively supported providers and the ACP catalog.
nav: Supported providers
order: 6
order: 21
category: Providers
---
# Supported providers

3
public-docs/updates.md
View File

@@ -2,7 +2,8 @@
title: Updates
description: How Paseo releases work, the difference between stable and beta channels, and how to opt in to earlier updates.
nav: Updates
order: 18
order: 5
category: Getting started
---
# Updates

3
public-docs/voice.md
View File

@@ -2,7 +2,8 @@
title: Voice
description: Paseo voice architecture, local-first model execution, and provider configuration.
nav: Voice
order: 13
order: 41
category: Configuration
---
# Voice

1
public-docs/why.md
View File

@@ -3,6 +3,7 @@ title: Why Paseo?
description: What Paseo is, what it isn't, and how it fits into your workflow.
nav: Why Paseo?
order: 2
category: Getting started
---
# Why Paseo?

3
public-docs/workspaces.md
View File

@@ -2,7 +2,8 @@
title: Workspaces
description: Understand Paseo's project, workspace, and session model before setting up agents or git worktrees.
nav: Workspaces
order: 3
order: 10
category: Workspaces
---
# Workspaces

3
public-docs/worktrees.md
View File

@@ -2,7 +2,8 @@
title: Git worktrees
description: Run agents in isolated git worktrees with setup hooks, scripts, and long-running services.
nav: Git worktrees
order: 4
order: 11
category: Workspaces
---
# Git worktrees