Paseo

Desktop OS: macOS

Typed value: Yes.

Paseo offers desktop, native phone, browser and CLI clients for its daemon; the shared browser app includes compact phone layouts.

• Desktop os: Docs state the desktop app is available on macOS, Windows and Linux (Linux .deb, .rpm, AppImage); homepage download button targets Mac.
• Mobile apps: Native iOS (App Store) and Android (Google Play) apps are linked from the homepage; Android APK also on GitHub releases. Minimum OS versions not checked.
• Browser: Hosted web app at app.paseo.sh and a daemon-served web UI (off by default).
• Cli: npm i -g @getpaseo/cli installs the CLI and daemon; TypeScript SDK @getpaseo/client.
• Cross device continuity: Docs: the daemon owns running agents so mobile, web and CLI clients continue in the same environment. No transition test.

Checked

2026-11-07 · checked 1 week ago

Plan

Not specified in this finding

Surface

Paseo desktop; Paseo mobile; Paseo web; Paseo daemon and APIs; Paseo CLI and TypeScript SDK

Version

Paseo v0.15.4 at 1c00b365c9e0b74c1580eba33d905d693125ae21; inspected 2026-11-13

• Documentation and pinned source inspection only; no hands-on scenario was run.

1. Paseo homepage

   Finding: Current homepage presents desktop/mobile/web/CLI and SDK control of user-hosted agents, native Claude/Codex/OpenCode/Pi/OMP/Antigravity/Muse and additional ACP tools. App is free/open source, with optional E2E relay and user provider accounts.

   Locator

   Run it anywhere; providers; FAQ; sponsor section

   Retrieved

   2026-11-07

2. Paseo: Getting started

   Finding: Desktop app bundles its own daemon; Linux .deb/.rpm/AppImage; headless install via npm i -g @getpaseo/cli; Docker image; at least one provider CLI must be installed by the user; gh CLI recommended for PR-aware worktrees.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

3. Paseo: Why Paseo?

   Finding: Desktop app on macOS, Windows and Linux; daemon owns agents and workspaces; mobile, web and CLI clients connect to the same environment; runs agents with the user's own subscriptions, credentials, skills and MCP servers; Apache-2.0 with no telemetry, tracking or required Paseo account. The v0.15.3 tag text of this page is an earlier version; it says the daemon manages agents and clients connect locally or over a relay, and it also states no telemetry and Apache-2.0.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

Desktop OS: Windows

Typed value: Yes.

Paseo offers desktop, native phone, browser and CLI clients for its daemon; the shared browser app includes compact phone layouts.

• Desktop os: Docs state the desktop app is available on macOS, Windows and Linux (Linux .deb, .rpm, AppImage); homepage download button targets Mac.
• Mobile apps: Native iOS (App Store) and Android (Google Play) apps are linked from the homepage; Android APK also on GitHub releases. Minimum OS versions not checked.
• Browser: Hosted web app at app.paseo.sh and a daemon-served web UI (off by default).
• Cli: npm i -g @getpaseo/cli installs the CLI and daemon; TypeScript SDK @getpaseo/client.
• Cross device continuity: Docs: the daemon owns running agents so mobile, web and CLI clients continue in the same environment. No transition test.

Checked

2026-11-07 · checked 1 week ago

Plan

Not specified in this finding

Surface

Paseo desktop; Paseo mobile; Paseo web; Paseo daemon and APIs; Paseo CLI and TypeScript SDK

Version

Paseo v0.15.4 at 1c00b365c9e0b74c1580eba33d905d693125ae21; inspected 2026-11-13

• Documentation and pinned source inspection only; no hands-on scenario was run.

1. Paseo homepage

   Finding: Current homepage presents desktop/mobile/web/CLI and SDK control of user-hosted agents, native Claude/Codex/OpenCode/Pi/OMP/Antigravity/Muse and additional ACP tools. App is free/open source, with optional E2E relay and user provider accounts.

   Locator

   Run it anywhere; providers; FAQ; sponsor section

   Retrieved

   2026-11-07

2. Paseo: Getting started

   Finding: Desktop app bundles its own daemon; Linux .deb/.rpm/AppImage; headless install via npm i -g @getpaseo/cli; Docker image; at least one provider CLI must be installed by the user; gh CLI recommended for PR-aware worktrees.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

3. Paseo: Why Paseo?

   Finding: Desktop app on macOS, Windows and Linux; daemon owns agents and workspaces; mobile, web and CLI clients connect to the same environment; runs agents with the user's own subscriptions, credentials, skills and MCP servers; Apache-2.0 with no telemetry, tracking or required Paseo account. The v0.15.3 tag text of this page is an earlier version; it says the daemon manages agents and clients connect locally or over a relay, and it also states no telemetry and Apache-2.0.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

Desktop OS: Linux

Typed value: Yes.

Paseo offers desktop, native phone, browser and CLI clients for its daemon; the shared browser app includes compact phone layouts.

• Desktop os: Docs state the desktop app is available on macOS, Windows and Linux (Linux .deb, .rpm, AppImage); homepage download button targets Mac.
• Mobile apps: Native iOS (App Store) and Android (Google Play) apps are linked from the homepage; Android APK also on GitHub releases. Minimum OS versions not checked.
• Browser: Hosted web app at app.paseo.sh and a daemon-served web UI (off by default).
• Cli: npm i -g @getpaseo/cli installs the CLI and daemon; TypeScript SDK @getpaseo/client.
• Cross device continuity: Docs: the daemon owns running agents so mobile, web and CLI clients continue in the same environment. No transition test.

Checked

2026-11-07 · checked 1 week ago

Plan

Not specified in this finding

Surface

Paseo desktop; Paseo mobile; Paseo web; Paseo daemon and APIs; Paseo CLI and TypeScript SDK

Version

Paseo v0.15.4 at 1c00b365c9e0b74c1580eba33d905d693125ae21; inspected 2026-11-13

• Documentation and pinned source inspection only; no hands-on scenario was run.

1. Paseo homepage

   Finding: Current homepage presents desktop/mobile/web/CLI and SDK control of user-hosted agents, native Claude/Codex/OpenCode/Pi/OMP/Antigravity/Muse and additional ACP tools. App is free/open source, with optional E2E relay and user provider accounts.

   Locator

   Run it anywhere; providers; FAQ; sponsor section

   Retrieved

   2026-11-07

2. Paseo: Getting started

   Finding: Desktop app bundles its own daemon; Linux .deb/.rpm/AppImage; headless install via npm i -g @getpaseo/cli; Docker image; at least one provider CLI must be installed by the user; gh CLI recommended for PR-aware worktrees.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

3. Paseo: Why Paseo?

   Finding: Desktop app on macOS, Windows and Linux; daemon owns agents and workspaces; mobile, web and CLI clients connect to the same environment; runs agents with the user's own subscriptions, credentials, skills and MCP servers; Apache-2.0 with no telemetry, tracking or required Paseo account. The v0.15.3 tag text of this page is an earlier version; it says the daemon manages agents and clients connect locally or over a relay, and it also states no telemetry and Apache-2.0.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

Web client

Typed value: Yes.

Paseo offers desktop, native phone, browser and CLI clients for its daemon; the shared browser app includes compact phone layouts.

• Desktop os: Docs state the desktop app is available on macOS, Windows and Linux (Linux .deb, .rpm, AppImage); homepage download button targets Mac.
• Mobile apps: Native iOS (App Store) and Android (Google Play) apps are linked from the homepage; Android APK also on GitHub releases. Minimum OS versions not checked.
• Browser: Hosted web app at app.paseo.sh and a daemon-served web UI (off by default).
• Cross device continuity: Docs: the daemon owns running agents so mobile, web and CLI clients continue in the same environment. No transition test.

Checked

2026-11-07 · checked 1 week ago

Plan

Not specified in this finding

Surface

Paseo desktop; Paseo mobile; Paseo web; Paseo daemon and APIs; Paseo CLI and TypeScript SDK

Version

Paseo v0.15.4 at 1c00b365c9e0b74c1580eba33d905d693125ae21; inspected 2026-11-13

• Documentation and pinned source inspection only; no hands-on scenario was run.

1. Paseo homepage

   Finding: Current homepage presents desktop/mobile/web/CLI and SDK control of user-hosted agents, native Claude/Codex/OpenCode/Pi/OMP/Antigravity/Muse and additional ACP tools. App is free/open source, with optional E2E relay and user provider accounts.

   Locator

   Run it anywhere; providers; FAQ; sponsor section

   Retrieved

   2026-11-07

2. Paseo: Self-hosting the web UI

   Finding: Daemon can serve the full browser UI from its own address (off by default, features.webUi.enabled); password and TLS reverse proxy guidance.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

Phone access: Native iOS

Typed value: Yes.

Paseo offers desktop, native phone, browser and CLI clients for its daemon; the shared browser app includes compact phone layouts.

• Desktop os: Docs state the desktop app is available on macOS, Windows and Linux (Linux .deb, .rpm, AppImage); homepage download button targets Mac.
• Mobile apps: Native iOS (App Store) and Android (Google Play) apps are linked from the homepage; Android APK also on GitHub releases. Minimum OS versions not checked.
• Browser: Hosted web app at app.paseo.sh and a daemon-served web UI (off by default).
• Cross device continuity: Docs: the daemon owns running agents so mobile, web and CLI clients continue in the same environment. No transition test.

Checked

2026-11-07 · checked 1 week ago

Plan

Not specified in this finding

Surface

Paseo desktop; Paseo mobile; Paseo web; Paseo daemon and APIs; Paseo CLI and TypeScript SDK

Version

Paseo v0.15.4 at 1c00b365c9e0b74c1580eba33d905d693125ae21; inspected 2026-11-13

• Documentation and pinned source inspection only; no hands-on scenario was run.

1. Paseo homepage

   Finding: Current homepage presents desktop/mobile/web/CLI and SDK control of user-hosted agents, native Claude/Codex/OpenCode/Pi/OMP/Antigravity/Muse and additional ACP tools. App is free/open source, with optional E2E relay and user provider accounts.

   Locator

   Run it anywhere; providers; FAQ; sponsor section

   Retrieved

   2026-11-07

2. Paseo: Updates

   Finding: Stable and Beta channels; stable desktop rolls out gradually over 36 hours; app-store releases can lag desktop and CLI; no beta in app stores; Android APK on GitHub releases.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

Phone access: Native Android

Typed value: Yes.

Paseo offers desktop, native phone, browser and CLI clients for its daemon; the shared browser app includes compact phone layouts.

• Desktop os: Docs state the desktop app is available on macOS, Windows and Linux (Linux .deb, .rpm, AppImage); homepage download button targets Mac.
• Mobile apps: Native iOS (App Store) and Android (Google Play) apps are linked from the homepage; Android APK also on GitHub releases. Minimum OS versions not checked.
• Browser: Hosted web app at app.paseo.sh and a daemon-served web UI (off by default).
• Cross device continuity: Docs: the daemon owns running agents so mobile, web and CLI clients continue in the same environment. No transition test.

Checked

2026-11-07 · checked 1 week ago

Plan

Not specified in this finding

Surface

Paseo desktop; Paseo mobile; Paseo web; Paseo daemon and APIs; Paseo CLI and TypeScript SDK

Version

Paseo v0.15.4 at 1c00b365c9e0b74c1580eba33d905d693125ae21; inspected 2026-11-13

• Documentation and pinned source inspection only; no hands-on scenario was run.

1. Paseo homepage

   Finding: Current homepage presents desktop/mobile/web/CLI and SDK control of user-hosted agents, native Claude/Codex/OpenCode/Pi/OMP/Antigravity/Muse and additional ACP tools. App is free/open source, with optional E2E relay and user provider accounts.

   Locator

   Run it anywhere; providers; FAQ; sponsor section

   Retrieved

   2026-11-07

2. Paseo: Updates

   Finding: Stable and Beta channels; stable desktop rolls out gradually over 36 hours; app-store releases can lag desktop and CLI; no beta in app stores; Android APK on GitHub releases.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

Phone access: Phone browser

Typed value: Yes.

Paseo offers desktop, native phone, browser and CLI clients for its daemon; the shared browser app includes compact phone layouts.

• Mobile browser: The browser app implements a mobile visual viewport and compact mobile panel layout.

Checked

2026-11-13 · checked 2 days ago

Plan

Not specified in this finding

Surface

Paseo desktop; Paseo mobile; Paseo web; Paseo daemon and APIs; Paseo CLI and TypeScript SDK

Version

Paseo v0.15.4 at 1c00b365c9e0b74c1580eba33d905d693125ae21; inspected 2026-11-13

• Documentation and pinned source inspection only; no hands-on scenario was run.

1. Paseo: packages/app/src/composer/dock/internal/fullscreen.tsx

   Finding: The shipped browser app explicitly handles the mobile browser visual viewport and uses compact mobile panel routing in the shared app layout. The daemon-served browser UI connects to the same agents. This establishes phone-browser access without claiming tested feature parity.

   Locator

   Mobile browser visible viewport; packages/app/src/app/_layout.tsx compact/mobile panel routing; public-docs/web-ui.md

   Retrieved

   2026-11-13

CLI

Typed value: Yes.

Paseo offers desktop, native phone, browser and CLI clients for its daemon; the shared browser app includes compact phone layouts.

• Desktop os: Docs state the desktop app is available on macOS, Windows and Linux (Linux .deb, .rpm, AppImage); homepage download button targets Mac.
• Cli: npm i -g @getpaseo/cli installs the CLI and daemon; TypeScript SDK @getpaseo/client.

Checked

2026-11-07 · checked 1 week ago

Plan

Not specified in this finding

Surface

Paseo desktop; Paseo mobile; Paseo web; Paseo daemon and APIs; Paseo CLI and TypeScript SDK

Version

Paseo v0.15.4 at 1c00b365c9e0b74c1580eba33d905d693125ae21; inspected 2026-11-13

• Documentation and pinned source inspection only; no hands-on scenario was run.

1. Paseo: Getting started

   Finding: Desktop app bundles its own daemon; Linux .deb/.rpm/AppImage; headless install via npm i -g @getpaseo/cli; Docker image; at least one provider CLI must be installed by the user; gh CLI recommended for PR-aware worktrees.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

2. Paseo: CLI reference

   Finding: CLI covers run/ls/attach/send/logs/wait/stop, projects, workspaces, terminals, scripts, plugins, schedules, permissions (paseo permit ls/allow/deny), agent modes and detach, daemon management, Hub commands, remote --host (including ssh://) and JSON/YAML output.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

3. Paseo: TypeScript SDK

   Finding: @getpaseo/client drives a daemon from a program: create agents with provider/model, cwd and prompt, wait for finish, send follow-ups; agents created through the SDK appear in the Paseo app and persist after the program exits.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

Coding agents: Claude Code

Typed value: Yes.

Current stable and homepage document native Claude Code, Codex, OpenCode, Pi, OMP, Antigravity and Muse plus a version-pinned ACP catalog and custom providers. Provider-specific MCP and permission limits remain separate. Paseo v0.15.4 registers a native Antigravity provider with the agy command, host-side availability checks and a session connection implementation.

• Harnesses: Native adapters and the ACP catalog support existing installed agent CLIs, including Claude Code, Codex, OpenCode, Pi, Cursor, Gemini CLI and Grok. Catalog and provider-specific tool/permission limits differ. Paseo v0.15.4 registers a native Antigravity provider with the agy command, host-side availability checks and a session connection implementation.
• Model providers: Model choice follows the provider CLI (for example OpenCode multi-provider, custom endpoints via agents.providers); Paseo does not itself list a model catalog beyond what each provider reports.
• Custom adapters: Custom providers via config (extends, ACP agents, binary override) and provider plugins.
• Session integration: Existing provider sessions can be imported (Import session on the New workspace screen, paseo import); provider coverage differs (Pi/OMP named in changelog).
• Mixed harness operation: Orchestration docs: agents can launch workers on any configured provider and model, including different providers in one task.

Checked

2026-11-07 · checked 1 week ago

Cross-check

cross-checked 2026-11-10

Plan

Not specified in this finding

Surface

Paseo daemon and APIs; Paseo desktop; Paseo CLI and TypeScript SDK

Version

Paseo v0.15.3 at d91ae138cb931447635e94296023414a58bedcc5; hosted Hub page reread 2026-11-07 Antigravity source pass: v0.15.4 (1c00b365c9e0b74c1580eba33d905d693125ae21).

• No mixed-provider execution test; installed tool credentials/model access are separate.
• Antigravity has Full access only and no Paseo tools or steering in the documented adapter.
• Antigravity requires agy on the host and its own sign-in. The documented adapter has Full access only and no Paseo tools or steering.

1. Paseo homepage

   Finding: Current homepage presents desktop/mobile/web/CLI and SDK control of user-hosted agents, native Claude/Codex/OpenCode/Pi/OMP/Antigravity/Muse and additional ACP tools. App is free/open source, with optional E2E relay and user provider accounts.

   Locator

   Run it anywhere; providers; FAQ; sponsor section

   Retrieved

   2026-11-07

2. Paseo: CHANGELOG.md

   Finding: Current stable changelog starts 0.15.3, November 6, 2026, and describes stable changes since the older v0.11.1 source pass.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

   Source date

   2026-11-06

3. Paseo: public-docs/orchestration.md

   Finding: Agents can launch other agents across providers and models, prompt them by ID, check progress, cancel, create workspaces/worktrees, use the CLI against remote hosts, create schedules and heartbeats. Paseo tool injection is off by default; workers appear in a Subagents track and completion notifies the parent.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

4. Paseo: public-docs/orchestration-workflows.md

   Finding: Recipes: fan-out research (workers share files), parallel edits in separate worktrees, implement-then-review, prompt another agent by ID, redirect/cancel a worker, remote-host CLI, heartbeats. Distinguishes interactive Paseo subagents from read-only native provider subagent timelines.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

5. Paseo: Supported providers

   Finding: Current stable guide covers native Claude Code, Codex, OpenCode, Pi, OMP, Antigravity and Muse plus ACP/custom routes; provider-specific permission, MCP and steering limits are explicit.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

6. Paseo: Plugins

   Finding: Plugins add screens, sidebar items, panels, commands, themes, attachment sources, daemon RPCs and providers; client contributions run on every connected client including mobile; registry install via paseo plugin add owner/slug.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

7. Paseo: Custom providers

   Finding: agents.providers in config.json can extend providers to other API endpoints, add profiles, override binaries, add ACP agents or disable providers.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

8. Native support (6 entries); ACP catalog (36 entries)

   Finding: Current stable guide names native providers and a version-pinned in-app ACP catalog plus custom providers. Antigravity has Full access only and no Paseo tools or steering; no exact stale catalog count repeated.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

9. Paseo homepage FAQ and integrations list

   Finding: Current homepage lists native Claude, Codex, OpenCode, Pi, OMP, Antigravity and Muse plus ACP; no exact catalog count inferred.

   Locator

   Works with your tools list; FAQ native implementations

   Retrieved

   2026-11-07

Coding agents: Codex

Typed value: Yes.

Current stable and homepage document native Claude Code, Codex, OpenCode, Pi, OMP, Antigravity and Muse plus a version-pinned ACP catalog and custom providers. Provider-specific MCP and permission limits remain separate. Paseo v0.15.4 registers a native Antigravity provider with the agy command, host-side availability checks and a session connection implementation.

• Harnesses: Native adapters and the ACP catalog support existing installed agent CLIs, including Claude Code, Codex, OpenCode, Pi, Cursor, Gemini CLI and Grok. Catalog and provider-specific tool/permission limits differ. Paseo v0.15.4 registers a native Antigravity provider with the agy command, host-side availability checks and a session connection implementation.
• Model providers: Model choice follows the provider CLI (for example OpenCode multi-provider, custom endpoints via agents.providers); Paseo does not itself list a model catalog beyond what each provider reports.
• Custom adapters: Custom providers via config (extends, ACP agents, binary override) and provider plugins.
• Session integration: Existing provider sessions can be imported (Import session on the New workspace screen, paseo import); provider coverage differs (Pi/OMP named in changelog).
• Mixed harness operation: Orchestration docs: agents can launch workers on any configured provider and model, including different providers in one task.

Checked

2026-11-07 · checked 1 week ago

Cross-check

cross-checked 2026-11-10

Plan

Not specified in this finding

Surface

Paseo daemon and APIs; Paseo desktop; Paseo CLI and TypeScript SDK

Version

Paseo v0.15.3 at d91ae138cb931447635e94296023414a58bedcc5; hosted Hub page reread 2026-11-07 Antigravity source pass: v0.15.4 (1c00b365c9e0b74c1580eba33d905d693125ae21).

• No mixed-provider execution test; installed tool credentials/model access are separate.
• Antigravity has Full access only and no Paseo tools or steering in the documented adapter.
• Antigravity requires agy on the host and its own sign-in. The documented adapter has Full access only and no Paseo tools or steering.

1. Paseo homepage

   Finding: Current homepage presents desktop/mobile/web/CLI and SDK control of user-hosted agents, native Claude/Codex/OpenCode/Pi/OMP/Antigravity/Muse and additional ACP tools. App is free/open source, with optional E2E relay and user provider accounts.

   Locator

   Run it anywhere; providers; FAQ; sponsor section

   Retrieved

   2026-11-07

2. Paseo: CHANGELOG.md

   Finding: Current stable changelog starts 0.15.3, November 6, 2026, and describes stable changes since the older v0.11.1 source pass.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

   Source date

   2026-11-06

3. Paseo: public-docs/orchestration.md

   Finding: Agents can launch other agents across providers and models, prompt them by ID, check progress, cancel, create workspaces/worktrees, use the CLI against remote hosts, create schedules and heartbeats. Paseo tool injection is off by default; workers appear in a Subagents track and completion notifies the parent.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

4. Paseo: public-docs/orchestration-workflows.md

   Finding: Recipes: fan-out research (workers share files), parallel edits in separate worktrees, implement-then-review, prompt another agent by ID, redirect/cancel a worker, remote-host CLI, heartbeats. Distinguishes interactive Paseo subagents from read-only native provider subagent timelines.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

5. Paseo: Supported providers

   Finding: Current stable guide covers native Claude Code, Codex, OpenCode, Pi, OMP, Antigravity and Muse plus ACP/custom routes; provider-specific permission, MCP and steering limits are explicit.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

6. Paseo: Plugins

   Finding: Plugins add screens, sidebar items, panels, commands, themes, attachment sources, daemon RPCs and providers; client contributions run on every connected client including mobile; registry install via paseo plugin add owner/slug.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

7. Paseo: Custom providers

   Finding: agents.providers in config.json can extend providers to other API endpoints, add profiles, override binaries, add ACP agents or disable providers.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

8. Native support (6 entries); ACP catalog (36 entries)

   Finding: Current stable guide names native providers and a version-pinned in-app ACP catalog plus custom providers. Antigravity has Full access only and no Paseo tools or steering; no exact stale catalog count repeated.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

9. Paseo homepage FAQ and integrations list

   Finding: Current homepage lists native Claude, Codex, OpenCode, Pi, OMP, Antigravity and Muse plus ACP; no exact catalog count inferred.

   Locator

   Works with your tools list; FAQ native implementations

   Retrieved

   2026-11-07

Coding agents: Cursor Agent

Typed value: Yes.

Current stable and homepage document native Claude Code, Codex, OpenCode, Pi, OMP, Antigravity and Muse plus a version-pinned ACP catalog and custom providers. Provider-specific MCP and permission limits remain separate. Paseo v0.15.4 registers a native Antigravity provider with the agy command, host-side availability checks and a session connection implementation.

• Harnesses: Native adapters and the ACP catalog support existing installed agent CLIs, including Claude Code, Codex, OpenCode, Pi, Cursor, Gemini CLI and Grok. Catalog and provider-specific tool/permission limits differ. Paseo v0.15.4 registers a native Antigravity provider with the agy command, host-side availability checks and a session connection implementation.

Checked

2026-11-07 · checked 1 week ago

Cross-check

cross-checked 2026-11-10

Plan

Not specified in this finding

Surface

Paseo daemon and APIs; Paseo desktop; Paseo CLI and TypeScript SDK

Version

Paseo v0.15.3 at d91ae138cb931447635e94296023414a58bedcc5; hosted Hub page reread 2026-11-07 Antigravity source pass: v0.15.4 (1c00b365c9e0b74c1580eba33d905d693125ae21).

• No mixed-provider execution test; installed tool credentials/model access are separate.
• Antigravity has Full access only and no Paseo tools or steering in the documented adapter.
• Antigravity requires agy on the host and its own sign-in. The documented adapter has Full access only and no Paseo tools or steering.

1. Paseo v0.15.3: public-docs/supported-providers.md

   Finding: The shipped ACP catalog explicitly lists Cursor, Gemini CLI and Grok; underlying CLIs must be installed and authenticated. No Aider listing was established.

   Locator

   Native support and ACP catalog

   Retrieved

   2026-11-07

Coding agents: Gemini CLI

Typed value: Yes.

Current stable and homepage document native Claude Code, Codex, OpenCode, Pi, OMP, Antigravity and Muse plus a version-pinned ACP catalog and custom providers. Provider-specific MCP and permission limits remain separate. Paseo v0.15.4 registers a native Antigravity provider with the agy command, host-side availability checks and a session connection implementation.

• Harnesses: Native adapters and the ACP catalog support existing installed agent CLIs, including Claude Code, Codex, OpenCode, Pi, Cursor, Gemini CLI and Grok. Catalog and provider-specific tool/permission limits differ. Paseo v0.15.4 registers a native Antigravity provider with the agy command, host-side availability checks and a session connection implementation.

Checked

2026-11-07 · checked 1 week ago

Cross-check

cross-checked 2026-11-10

Plan

Not specified in this finding

Surface

Paseo daemon and APIs; Paseo desktop; Paseo CLI and TypeScript SDK

Version

Paseo v0.15.3 at d91ae138cb931447635e94296023414a58bedcc5; hosted Hub page reread 2026-11-07 Antigravity source pass: v0.15.4 (1c00b365c9e0b74c1580eba33d905d693125ae21).

• No mixed-provider execution test; installed tool credentials/model access are separate.
• Antigravity has Full access only and no Paseo tools or steering in the documented adapter.
• Antigravity requires agy on the host and its own sign-in. The documented adapter has Full access only and no Paseo tools or steering.

1. Paseo v0.15.3: public-docs/supported-providers.md

   Finding: The shipped ACP catalog explicitly lists Cursor, Gemini CLI and Grok; underlying CLIs must be installed and authenticated. No Aider listing was established.

   Locator

   Native support and ACP catalog

   Retrieved

   2026-11-07

Coding agents: OpenCode

Typed value: Yes.

Current stable and homepage document native Claude Code, Codex, OpenCode, Pi, OMP, Antigravity and Muse plus a version-pinned ACP catalog and custom providers. Provider-specific MCP and permission limits remain separate. Paseo v0.15.4 registers a native Antigravity provider with the agy command, host-side availability checks and a session connection implementation.

• Harnesses: Native adapters and the ACP catalog support existing installed agent CLIs, including Claude Code, Codex, OpenCode, Pi, Cursor, Gemini CLI and Grok. Catalog and provider-specific tool/permission limits differ. Paseo v0.15.4 registers a native Antigravity provider with the agy command, host-side availability checks and a session connection implementation.
• Model providers: Model choice follows the provider CLI (for example OpenCode multi-provider, custom endpoints via agents.providers); Paseo does not itself list a model catalog beyond what each provider reports.
• Custom adapters: Custom providers via config (extends, ACP agents, binary override) and provider plugins.
• Session integration: Existing provider sessions can be imported (Import session on the New workspace screen, paseo import); provider coverage differs (Pi/OMP named in changelog).
• Mixed harness operation: Orchestration docs: agents can launch workers on any configured provider and model, including different providers in one task.

Checked

2026-11-07 · checked 1 week ago

Cross-check

cross-checked 2026-11-10

Plan

Not specified in this finding

Surface

Paseo daemon and APIs; Paseo desktop; Paseo CLI and TypeScript SDK

Version

Paseo v0.15.3 at d91ae138cb931447635e94296023414a58bedcc5; hosted Hub page reread 2026-11-07 Antigravity source pass: v0.15.4 (1c00b365c9e0b74c1580eba33d905d693125ae21).

• No mixed-provider execution test; installed tool credentials/model access are separate.
• Antigravity has Full access only and no Paseo tools or steering in the documented adapter.
• Antigravity requires agy on the host and its own sign-in. The documented adapter has Full access only and no Paseo tools or steering.

1. Paseo homepage

   Finding: Current homepage presents desktop/mobile/web/CLI and SDK control of user-hosted agents, native Claude/Codex/OpenCode/Pi/OMP/Antigravity/Muse and additional ACP tools. App is free/open source, with optional E2E relay and user provider accounts.

   Locator

   Run it anywhere; providers; FAQ; sponsor section

   Retrieved

   2026-11-07

2. Paseo: CHANGELOG.md

   Finding: Current stable changelog starts 0.15.3, November 6, 2026, and describes stable changes since the older v0.11.1 source pass.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

   Source date

   2026-11-06

3. Paseo: public-docs/orchestration.md

   Finding: Agents can launch other agents across providers and models, prompt them by ID, check progress, cancel, create workspaces/worktrees, use the CLI against remote hosts, create schedules and heartbeats. Paseo tool injection is off by default; workers appear in a Subagents track and completion notifies the parent.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

4. Paseo: public-docs/orchestration-workflows.md

   Finding: Recipes: fan-out research (workers share files), parallel edits in separate worktrees, implement-then-review, prompt another agent by ID, redirect/cancel a worker, remote-host CLI, heartbeats. Distinguishes interactive Paseo subagents from read-only native provider subagent timelines.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

5. Paseo: Supported providers

   Finding: Current stable guide covers native Claude Code, Codex, OpenCode, Pi, OMP, Antigravity and Muse plus ACP/custom routes; provider-specific permission, MCP and steering limits are explicit.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

6. Paseo: Plugins

   Finding: Plugins add screens, sidebar items, panels, commands, themes, attachment sources, daemon RPCs and providers; client contributions run on every connected client including mobile; registry install via paseo plugin add owner/slug.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

7. Paseo: Custom providers

   Finding: agents.providers in config.json can extend providers to other API endpoints, add profiles, override binaries, add ACP agents or disable providers.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

8. Native support (6 entries); ACP catalog (36 entries)

   Finding: Current stable guide names native providers and a version-pinned in-app ACP catalog plus custom providers. Antigravity has Full access only and no Paseo tools or steering; no exact stale catalog count repeated.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

9. Paseo homepage FAQ and integrations list

   Finding: Current homepage lists native Claude, Codex, OpenCode, Pi, OMP, Antigravity and Muse plus ACP; no exact catalog count inferred.

   Locator

   Works with your tools list; FAQ native implementations

   Retrieved

   2026-11-07

Coding agents: Pi

Typed value: Yes.

Current stable and homepage document native Claude Code, Codex, OpenCode, Pi, OMP, Antigravity and Muse plus a version-pinned ACP catalog and custom providers. Provider-specific MCP and permission limits remain separate. Paseo v0.15.4 registers a native Antigravity provider with the agy command, host-side availability checks and a session connection implementation.

• Harnesses: Native adapters and the ACP catalog support existing installed agent CLIs, including Claude Code, Codex, OpenCode, Pi, Cursor, Gemini CLI and Grok. Catalog and provider-specific tool/permission limits differ. Paseo v0.15.4 registers a native Antigravity provider with the agy command, host-side availability checks and a session connection implementation.
• Model providers: Model choice follows the provider CLI (for example OpenCode multi-provider, custom endpoints via agents.providers); Paseo does not itself list a model catalog beyond what each provider reports.
• Custom adapters: Custom providers via config (extends, ACP agents, binary override) and provider plugins.
• Session integration: Existing provider sessions can be imported (Import session on the New workspace screen, paseo import); provider coverage differs (Pi/OMP named in changelog).
• Mixed harness operation: Orchestration docs: agents can launch workers on any configured provider and model, including different providers in one task.

Checked

2026-11-07 · checked 1 week ago

Cross-check

cross-checked 2026-11-10

Plan

Not specified in this finding

Surface

Paseo daemon and APIs; Paseo desktop; Paseo CLI and TypeScript SDK

Version

Paseo v0.15.3 at d91ae138cb931447635e94296023414a58bedcc5; hosted Hub page reread 2026-11-07 Antigravity source pass: v0.15.4 (1c00b365c9e0b74c1580eba33d905d693125ae21).

• No mixed-provider execution test; installed tool credentials/model access are separate.
• Antigravity has Full access only and no Paseo tools or steering in the documented adapter.
• Antigravity requires agy on the host and its own sign-in. The documented adapter has Full access only and no Paseo tools or steering.

1. Paseo homepage

   Finding: Current homepage presents desktop/mobile/web/CLI and SDK control of user-hosted agents, native Claude/Codex/OpenCode/Pi/OMP/Antigravity/Muse and additional ACP tools. App is free/open source, with optional E2E relay and user provider accounts.

   Locator

   Run it anywhere; providers; FAQ; sponsor section

   Retrieved

   2026-11-07

2. Paseo: CHANGELOG.md

   Finding: Current stable changelog starts 0.15.3, November 6, 2026, and describes stable changes since the older v0.11.1 source pass.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

   Source date

   2026-11-06

3. Paseo: public-docs/orchestration.md

   Finding: Agents can launch other agents across providers and models, prompt them by ID, check progress, cancel, create workspaces/worktrees, use the CLI against remote hosts, create schedules and heartbeats. Paseo tool injection is off by default; workers appear in a Subagents track and completion notifies the parent.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

4. Paseo: public-docs/orchestration-workflows.md

   Finding: Recipes: fan-out research (workers share files), parallel edits in separate worktrees, implement-then-review, prompt another agent by ID, redirect/cancel a worker, remote-host CLI, heartbeats. Distinguishes interactive Paseo subagents from read-only native provider subagent timelines.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

5. Paseo: Supported providers

   Finding: Current stable guide covers native Claude Code, Codex, OpenCode, Pi, OMP, Antigravity and Muse plus ACP/custom routes; provider-specific permission, MCP and steering limits are explicit.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

6. Paseo: Plugins

   Finding: Plugins add screens, sidebar items, panels, commands, themes, attachment sources, daemon RPCs and providers; client contributions run on every connected client including mobile; registry install via paseo plugin add owner/slug.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

7. Paseo: Custom providers

   Finding: agents.providers in config.json can extend providers to other API endpoints, add profiles, override binaries, add ACP agents or disable providers.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

8. Native support (6 entries); ACP catalog (36 entries)

   Finding: Current stable guide names native providers and a version-pinned in-app ACP catalog plus custom providers. Antigravity has Full access only and no Paseo tools or steering; no exact stale catalog count repeated.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

9. Paseo homepage FAQ and integrations list

   Finding: Current homepage lists native Claude, Codex, OpenCode, Pi, OMP, Antigravity and Muse plus ACP; no exact catalog count inferred.

   Locator

   Works with your tools list; FAQ native implementations

   Retrieved

   2026-11-07

Coding agents: Grok

Typed value: Yes.

Current stable and homepage document native Claude Code, Codex, OpenCode, Pi, OMP, Antigravity and Muse plus a version-pinned ACP catalog and custom providers. Provider-specific MCP and permission limits remain separate. Paseo v0.15.4 registers a native Antigravity provider with the agy command, host-side availability checks and a session connection implementation.

• Harnesses: Native adapters and the ACP catalog support existing installed agent CLIs, including Claude Code, Codex, OpenCode, Pi, Cursor, Gemini CLI and Grok. Catalog and provider-specific tool/permission limits differ. Paseo v0.15.4 registers a native Antigravity provider with the agy command, host-side availability checks and a session connection implementation.

Checked

2026-11-07 · checked 1 week ago

Cross-check

cross-checked 2026-11-10

Plan

Not specified in this finding

Surface

Paseo daemon and APIs; Paseo desktop; Paseo CLI and TypeScript SDK

Version

Paseo v0.15.3 at d91ae138cb931447635e94296023414a58bedcc5; hosted Hub page reread 2026-11-07 Antigravity source pass: v0.15.4 (1c00b365c9e0b74c1580eba33d905d693125ae21).

• No mixed-provider execution test; installed tool credentials/model access are separate.
• Antigravity has Full access only and no Paseo tools or steering in the documented adapter.
• Antigravity requires agy on the host and its own sign-in. The documented adapter has Full access only and no Paseo tools or steering.

1. Paseo v0.15.3: public-docs/supported-providers.md

   Finding: The shipped ACP catalog explicitly lists Cursor, Gemini CLI and Grok; underlying CLIs must be installed and authenticated. No Aider listing was established.

   Locator

   Native support and ACP catalog

   Retrieved

   2026-11-07

Coding agents: Antigravity

Typed value: Yes.

Current stable and homepage document native Claude Code, Codex, OpenCode, Pi, OMP, Antigravity and Muse plus a version-pinned ACP catalog and custom providers. Provider-specific MCP and permission limits remain separate. Paseo v0.15.4 registers a native Antigravity provider with the agy command, host-side availability checks and a session connection implementation.

• Harnesses: Native adapters and the ACP catalog support existing installed agent CLIs, including Claude Code, Codex, OpenCode, Pi, Cursor, Gemini CLI and Grok. Catalog and provider-specific tool/permission limits differ. Paseo v0.15.4 registers a native Antigravity provider with the agy command, host-side availability checks and a session connection implementation.

Checked

2026-11-10 · checked 5 days ago

Cross-check

cross-checked 2026-11-10

Plan

Not specified in this finding

Surface

Paseo daemon and APIs; Paseo desktop; Paseo CLI and TypeScript SDK

Version

Paseo v0.15.3 at d91ae138cb931447635e94296023414a58bedcc5; hosted Hub page reread 2026-11-07 Antigravity source pass: v0.15.4 (1c00b365c9e0b74c1580eba33d905d693125ae21).

• No mixed-provider execution test; installed tool credentials/model access are separate.
• Antigravity has Full access only and no Paseo tools or steering in the documented adapter.
• Antigravity requires agy on the host and its own sign-in. The documented adapter has Full access only and no Paseo tools or steering.

1. Paseo Antigravity support at v0.15.4

   Finding: Paseo v0.15.4 registers a native Antigravity provider with the agy command, host-side availability checks and a session connection implementation.

   Locator

   plugins/antigravity-provider/server/provider.ts lines 16-53, v0.15.4, commit 1c00b365c9e0b74c1580eba33d905d693125ae21

   Retrieved

   2026-11-10

   Source date

   2026-11-10

Use my subscription

Typed value: Yes.

Paseo reuses each provider CLI's own login for Claude plan, ChatGPT plan and API-key use, and adds no charge for Claude Code or Codex. Optional custom-provider and speech credentials can be written to Paseo config.

• Agent subscriptions: Claude Code usage counts against the normal Claude plan; Codex can use ChatGPT plan access.
• Api accounts: Codex can use an OpenAI API key; OpenCode uses provider API keys through its CLI. Custom provider env entries (for example ANTHROPIC_API_KEY) and speech provider keys can be written to Paseo config (custom-providers and voice docs at the tag). That is optional configuration, not the normal login path.
• Vendor credits: Docs state no separate Agent SDK credit pool is needed for Claude Code in Paseo; other vendor credit handling not documented.

Checked

2026-11-07 · checked 1 week ago

Cross-check

cross-checked 2026-11-07

Plan

Not specified in this finding

Surface

Paseo daemon and APIs; Paseo desktop

Version

Paseo v0.15.3 at d91ae138cb931447635e94296023414a58bedcc5; hosted Hub page reread 2026-11-07

• Credentials for the normal login path stay in the provider CLI. Multiple accounts are supported per provider: profiles bind different credentials per provider entry (custom-providers docs, Multiple profiles), and agents respect custom CLAUDE_CONFIG_DIR and CODEX_HOME homes (changelog, PR #5465). The exact user action for switching between accounts is not documented. Vendor-side restrictions are not documented by Paseo.
• Claude plan requirement and limits are Anthropic's, per Paseo's own docs.

1. Paseo: Claude Code provider

   Finding: Runs the official claude CLI via the Claude Agent SDK; usage counts against the user's normal Claude plan limits with no separate Agent SDK credit pool; a Claude plan including Claude Code is required.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

2. Paseo: Codex provider

   Finding: No Paseo charge for Codex; sign in with ChatGPT (plan access) or an OpenAI API key.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

Where agents run: On your computer

Typed value: Yes.

Paseo runs agents on operator-owned local or server daemon machines. Clients attach independently, while hosted Hub only dispatches to connected user daemons and does not provide agent compute.

• Local: The desktop app starts/manages a local daemon and agents use files/tools on that machine.
• Byo remote: The guide deliberately supports running the environment on a server and remote SSH/Tailscale client attachment.
• Client disconnect: The daemon owns running agents/workspaces independently of its thin clients; the separately hosted daemon must stay running.

Checked

2026-11-13 · checked 2 days ago

Plan

Not specified in this finding

Surface

Paseo daemon and APIs; Paseo desktop; Paseo mobile; Paseo web; Paseo CLI and TypeScript SDK

Version

Paseo v0.15.4 at 1c00b365c9e0b74c1580eba33d905d693125ae21 and current Hub page; checked 2026-11-13

• Documentation and pinned source inspection only; no hands-on scenario was run.
• Other atomic questions remain unestablished: resources, region, expiry.

1. Paseo: public-docs/why.md

   Finding: The current pinned release documents automatic local daemon management, with the daemon owning running agents/workspaces and separate desktop/mobile/web/CLI clients. It explicitly supports running the environment on a server and continuing from other devices; client-laptop disconnect does not move execution off that operator daemon host.

   Locator

   Develop in one workspace; Continue from another device

   Retrieved

   2026-11-13

Where agents run: On your own server

Typed value: Yes.

Paseo runs agents on operator-owned local or server daemon machines. Clients attach independently, while hosted Hub only dispatches to connected user daemons and does not provide agent compute.

• Local: The desktop app starts/manages a local daemon and agents use files/tools on that machine.
• Byo remote: The guide deliberately supports running the environment on a server and remote SSH/Tailscale client attachment.
• Client disconnect: The daemon owns running agents/workspaces independently of its thin clients; the separately hosted daemon must stay running.

Checked

2026-11-13 · checked 2 days ago

Plan

Not specified in this finding

Surface

Paseo daemon and APIs; Paseo desktop; Paseo mobile; Paseo web; Paseo CLI and TypeScript SDK

Version

Paseo v0.15.4 at 1c00b365c9e0b74c1580eba33d905d693125ae21 and current Hub page; checked 2026-11-13

• Documentation and pinned source inspection only; no hands-on scenario was run.
• Other atomic questions remain unestablished: resources, region, expiry.

1. Paseo: public-docs/why.md

   Finding: The current pinned release documents automatic local daemon management, with the daemon owning running agents/workspaces and separate desktop/mobile/web/CLI clients. It explicitly supports running the environment on a server and continuing from other devices; client-laptop disconnect does not move execution off that operator daemon host.

   Locator

   Develop in one workspace; Continue from another device

   Retrieved

   2026-11-13

2. Paseo: public-docs/connectivity.md

   Finding: The pinned release explicitly supports a daemon on the user computer or server. Desktop and CLI attach through SSH to an already-running remote daemon, while mobile can use relay/Tailscale; this is an operator-owned execution host rather than a vendor compute service.

   Locator

   SSH setup and Tailscale daemon listen configuration

   Retrieved

   2026-11-13

Where agents run: In the vendor's cloud

Typed value: No.

Paseo runs agents on operator-owned local or server daemon machines. Clients attach independently, while hosted Hub only dispatches to connected user daemons and does not provide agent compute.

• Managed cloud: The current Hub offering executes agents on connected user daemons and nowhere else.

Checked

2026-11-13 · checked 2 days ago

Plan

Not specified in this finding

Surface

Paseo daemon and APIs; Paseo desktop; Paseo mobile; Paseo web; Paseo CLI and TypeScript SDK

Version

Paseo v0.15.4 at 1c00b365c9e0b74c1580eba33d905d693125ae21 and current Hub page; checked 2026-11-13

• Documentation and pinned source inspection only; no hands-on scenario was run.
• Other atomic questions remain unestablished: resources, region, expiry.

1. Paseo: Hub FAQ Can the Hub run code on my machines; plan list

   Finding: The first-party Hub page says agents run on connected user daemons and nowhere else. Both Hosted Free and Pro specify that daemons run on the user machines. Hosted Hub does not provision agent compute.

   Locator

   Hub FAQ Can the Hub run code on my machines; plan list

   Retrieved

   2026-11-13

Workspace isolation: Git worktree

Typed value: Yes.

Paseo isolates file changes with optional git worktrees per workspace; same-workspace agents share files. Paseo documents no per-task process sandbox: Hub states it does not sandbox provider processes, provider-native sandbox settings apply, and network isolation is unknown.

• Branch: Worktree workspaces get a branch (branch-off, checkout-branch, checkout-pr).
• Worktree: Managed git worktrees per workspace with setup/teardown hooks.
• Process: Services get per-worktree ports; processes still share machine ports unless configured.

Checked

2026-11-07 · checked 1 week ago

Cross-check

cross-checked 2026-11-10

Plan

Not specified in this finding

Surface

Paseo desktop; Paseo daemon and APIs; Paseo Hub

Version

v0.11.1 release (tag ab10a6694); sources read at main d0bc188a5 (eight later commits)

• Docker image is a deployment option, not per-task isolation; Hub explicitly states it does not sandbox the agent; provider-native sandbox options exist per provider.

1. Paseo: Git worktrees

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Worktrees under $PASEO_HOME/worktrees; branch-off, checkout-branch and checkout-pr modes; paseo.json setup/teardown hooks, scripts, supervised services with per-worktree ports, port ranges or external allocator, reverse proxy hostnames, auto-opened terminals.

   Locator

   public-docs/worktrees.md

   Retrieved

   2026-10-09

Workspace isolation: Container

Typed value: Yes.

Paseo isolates file changes with optional git worktrees per workspace; same-workspace agents share files. Paseo documents no per-task process sandbox: Hub states it does not sandbox provider processes, provider-native sandbox settings apply, and network isolation is unknown.

• Container: The official stable Docker image runs the daemon and its launched agents as non-root paseo with scoped code/home mounts. This isolates a deployment rather than each task.
• Code separation: Docker mounts bound reachable repositories and credentials; all agents in that daemon share the mounted environment unless the operator isolates hosts.

Checked

2026-11-07 · checked 1 week ago

Plan

Not specified in this finding

Surface

Paseo desktop; Paseo daemon and APIs; Paseo Hub

Version

v0.11.1 release (tag ab10a6694); sources read at main d0bc188a5 (eight later commits)

• Docker image is a deployment option, not per-task isolation; Hub explicitly states it does not sandbox the agent; provider-native sandbox options exist per provider.

1. Paseo v0.15.3: public-docs/docker.md

   Finding: Official stable Docker image runs daemon and launched agents as non-root paseo with explicit code/home mounts; this is host deployment, not one container per task. Agent CLIs are installed in a child image.

   Locator

   What the image includes; Volumes; Security

   Retrieved

   2026-11-07

Workspace isolation: VM or microVM

Typed value: Yes.

Paseo isolates file changes with optional git worktrees per workspace; same-workspace agents share files. Paseo documents no per-task process sandbox: Hub states it does not sandbox provider processes, provider-native sandbox settings apply, and network isolation is unknown.

• Vm: Hub recommends an operator-supplied VM when stronger host isolation is needed; Paseo does not provision a VM for each task.
• Network: Hub carries the selected provider native network policy, such as Codex network_access false; OS/network isolation remains the operator responsibility.

Checked

2026-11-07 · checked 1 week ago

Plan

Not specified in this finding

Surface

Paseo desktop; Paseo daemon and APIs; Paseo Hub

Version

v0.11.1 release (tag ab10a6694); sources read at main d0bc188a5 (eight later commits)

• Docker image is a deployment option, not per-task isolation; Hub explicitly states it does not sandbox the agent; provider-native sandbox options exist per provider.

1. Paseo v0.15.3: public-docs/hub/security.md

   Finding: Hub does not sandbox agent processes. For stronger host containment it recommends an OS user, container or VM; named Codex options can deny network_access and choose writable roots, with provider/OS enforcement remaining separate.

   Locator

   Protect configuration authority; Provider-native controls

   Retrieved

   2026-11-07

Parallel runs

Typed value: Yes.

Paseo runs multiple agents and workspaces concurrently, each in its own worktree if wanted; documented recipes cover parallel research and parallel edits.

• Concurrent sessions: A workspace can run multiple agent sessions, terminals and browsers at once.

Checked

2026-11-07 · checked 1 week ago

Cross-check

cross-checked 2026-11-07

Plan

Not specified in this finding

Surface

Paseo desktop; Paseo daemon and APIs; Paseo CLI and TypeScript SDK

Version

v0.11.1 release (tag ab10a6694); sources read at main d0bc188a5 (eight later commits)

• No concurrency quota or observed concurrency measurement documented; research workers in one workspace share files.

1. Paseo: Workspaces

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Project, workspace and session model; workspace isolation is Local (existing directory, shared files) or Worktree (managed git worktree and branch); workspaces can be created without an agent; any directory on a daemon host can be a project.

   Locator

   public-docs/workspaces.md

   Retrieved

   2026-10-09

Coordinator

Typed value: Yes.

Agents can launch, prompt, inspect and cancel other agents of any provider; workers are retained as inspectable subagent sessions with notifications back to the parent.

• Roles: Agent profiles carry When-to-use notes; roles are conventions rather than enforced.
• Model harness effort: create_agent takes provider/model; profiles store thinking level and mode.
• Messages: send_agent_prompt and paseo send address agents by ID, including across workspaces on a host.
• Results return: Parent receives a notification when a worker finishes; paseo wait and get_agent_activity collect results; --output-schema yields structured output.
• Cross harness: Workers can use a different provider than the parent.
• Orchestration owner: Parentage records which agent owns delegated work.
• Activation: Settings > Agents > Enable Paseo tools, off by default; CLI route needs no injection.
• Authentication: MCP and CLI act with the daemon's access; per-provider tool policy is explicitly not a security boundary.
• Live progress: Subagents track and attach/logs follow worker output.
• Retained results: Subagent conversations persist as sessions; closed agents resume.
• Followup: Workers continue in their existing conversation after follow-up prompts.
• Invocation: Natural-language request, MCP tools, CLI or skills.

Checked

2026-11-07 · checked 1 week ago

Cross-check

cross-checked 2026-11-07

Plan

Not specified in this finding

Surface

Paseo desktop; Paseo daemon and APIs; Paseo CLI and TypeScript SDK

Version

v0.11.1 release (tag ab10a6694); sources read at main d0bc188a5 (eight later commits)

• Paseo tool injection is off by default; Antigravity lacks Paseo tools; native provider subagents are read-only timelines.
• No hands-on delegation scenario run.

1. Paseo: public-docs/orchestration.md

   Finding: Agents can launch other agents across providers and models, prompt them by ID, check progress, cancel, create workspaces/worktrees, use the CLI against remote hosts, create schedules and heartbeats. Paseo tool injection is off by default; workers appear in a Subagents track and completion notifies the parent.

   Locator

   public-docs/orchestration.md

   Retrieved

   2026-10-08

2. Paseo: public-docs/orchestration-workflows.md

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Recipes: fan-out research (workers share files), parallel edits in separate worktrees, implement-then-review, prompt another agent by ID, redirect/cancel a worker, remote-host CLI, heartbeats. Distinguishes interactive Paseo subagents from read-only native provider subagent timelines.

   Locator

   public-docs/orchestration-workflows.md

   Retrieved

   2026-10-09

3. Paseo: MCP reference

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Paseo MCP server on the daemon (enabled by default; injection into agents off by default) exposing agent, workspace, workspace-script, terminal, schedule/heartbeat, profile, provider, permission, browser and voice tools; per-provider tool allow/deny policy, explicitly not a security boundary.

   Locator

   public-docs/mcp.md

   Retrieved

   2026-10-09

4. Paseo: CLI reference

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): CLI covers run/ls/attach/send/logs/wait/stop, projects, workspaces, terminals, scripts, plugins, schedules, permissions (paseo permit ls/allow/deny), agent modes and detach, daemon management, Hub commands, remote --host (including ssh://) and JSON/YAML output.

   Locator

   public-docs/cli.md

   Retrieved

   2026-10-09

5. Paseo: Agent lifecycle

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Agent states initializing/idle/running/error/closed; closed agents keep identity, timeline and persistence handle and resume under the same ID; a runtime that dies between turns can leave an idle-looking agent until reported; cancellation and permission notifications to parent agents.

   Locator

   docs/agent-lifecycle.md

   Retrieved

   2026-10-09

6. Paseo: Agent profiles

   Finding: Named profiles store provider, model, mode, thinking level and features with When-to-use notes that orchestrating agents read via list_profiles.

   Locator

   public-docs/agent-profiles.md

   Retrieved

   2026-10-08

7. Paseo: Orchestration skills

   Finding: Installable /paseo, /paseo-handoff, /paseo-committee and /paseo-advisor skills for delegation, handoff and second opinions.

   Locator

   public-docs/skills.md

   Retrieved

   2026-10-08

Native issue tracking

Typed value: No.

The inspected release exposes agent workspaces and provider task displays, but no native issue tracker. The FileTaskStore utility is not connected to an accessible product action.

• Create: No native issue-create action is wired into the daemon, app, CLI or Hub.
• Task session separation: The standalone task-store library has no product entrypoint in the inspected release; external trackers remain separate.
• Durable states: Durable state in the accessible product belongs to agent workspaces or workflow runs, not independent native issues.

Checked

2026-11-13 · checked 2 days ago

Plan

Not specified in this finding

Surface

Paseo desktop; Paseo mobile; Paseo web; Paseo daemon and APIs; Paseo Hub; Paseo CLI and TypeScript SDK

Version

Paseo v0.15.4 and public Hub commit 61e51c56f8756e40c55a30982160ce000f2aa177; inspected 2026-11-13

• Documentation and pinned source inspection only; no hands-on scenario was run.
• Other atomic questions remain unestablished: edit, discuss, prioritize, label, assign, search, filter, archive, reopen, project_epic_views, idea_parking, explicit_dispatch, metadata, external_tracker_requirement.

1. Paseo: packages/server/src/tasks/task-store.ts

   Finding: The source contains a standalone FileTaskStore library with task states, but it is not imported into a shipped daemon route, app action or CLI command. Inspection of the app, daemon, CLI and public Hub routes/schema found provider task displays, agent workspaces and execution runs rather than an accessible product-owned issue tracker. External GitHub and Linear issues remain external.

   Locator

   FileTaskStore; types.ts; references across packages/server, packages/cli and packages/app; Hub routes and schema

   Retrieved

   2026-11-13

Unattended triggers

Typed value: Yes.

Paseo schedules start new agents on a cron cadence (with run and expiry limits) and heartbeats re-prompt an existing agent; Hub starts workflows from GitHub, Slack and Discord events.

• Schedules: Cron schedules with timezone, run-now, pause/resume/run-once.
• Recurring tasks: Schedules and heartbeats are recurring.
• Completion conditions: Schedules carry --max-runs and --expires-in; heartbeats can expire; Hub steps require agents to call hub.finish_execution.
• Scheduler location: Schedules are managed by the daemon on the user's host; Hub holds triggers and dispatches to daemons.
• Client independence: The daemon manages schedules and heartbeats and keeps running agents without a connected client; the schedule docs do not state no-client behavior explicitly.

Checked

2026-11-07 · checked 1 week ago

Cross-check

cross-checked 2026-11-07

Plan

Not specified in this finding

Surface

Paseo daemon and APIs; Paseo Hub; Paseo CLI and TypeScript SDK

Version

v0.11.1 release (tag ab10a6694); sources read at main d0bc188a5 (eight later commits)

• Schedules run on the daemon, so the daemon must be up; Hub does not queue events and does not retry an offline dispatch; overlap behavior was not documented.

1. Paseo: Schedules

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Schedules start a new agent per run on a cron cadence; heartbeats prompt one existing agent; both can be created in the app, from chat, via CLI or MCP; inspect, pause, resume, run once, update, delete.

   Locator

   public-docs/schedules.md

   Retrieved

   2026-10-09

2. Paseo: Schedules from the CLI

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): paseo schedule create with --every/--cron, --timezone, --max-runs, --expires-in, --run-now, --provider, --cwd; ls/inspect/logs/pause/resume/run-once/update/delete; heartbeats via paseo heartbeat; remote daemons via --host.

   Locator

   public-docs/schedules-cli.md

   Retrieved

   2026-10-09

Shared prompting

Typed value: Yes.

In self-hosted Paseo Hub, distinct permitted Slack users can send instructions to one daemon agent by enabling Same conversation continuity for a Slack trigger. Generic daemon-principal pairing alone does not establish distinct human collaboration.

• Coprompting: Slack author IDs pass a per-human allowlist; the thread conversation key omits author ID and Hub sends each arrival to the same persisted agent session.
• Permissions: The Slack trigger independently filters human authors, and the daemon owner explicitly grants Hub hub.execute authority.
• Owner online: The running self-hosted Hub and daemon deliver allowed Slack messages without a desktop-owner client connection.

Checked

2026-11-13 · checked 2 days ago

Plan

Self-hosted early-development Paseo Hub; Slack trigger Agent continuity = Same conversation; explicit hub.execute grant

Surface

Paseo Hub; Paseo daemon and APIs

Availability

beta

Version

Paseo v0.15.4 at 1c00b365c9e0b74c1580eba33d905d693125ae21; Hub source 61e51c56f8756e40c55a30982160ce000f2aa177; checked 2026-11-13

• Documentation and pinned source inspection only; no hands-on scenario was run.
• Other atomic questions remain unestablished: discussion, comments, presence, ordering, conflicts.

1. Paseo: src/triggers/slack/match.ts

   Finding: The Hub Slack trigger independently checks each real Slack author ID or username against from_users (or an explicit wildcard); bot messages are excluded. This establishes distinct permitted human Slack identities rather than shared daemon-owner bearer principals.

   Locator

   matchesFilters from_users; events.ts normalized author ID

   Retrieved

   2026-11-13

2. Paseo: src/triggers/slack/provider.ts

   Finding: The first-party Agent continuity control offers Same conversation to continue the same agent for a conversation. Slack conversation keys contain team, channel and root thread timestamp, excluding author ID. Multiple permitted Slack humans in one thread therefore resolve to one continuation key. Custom key is also available; New agent remains separate.

   Locator

   Accepted match conversation key; triggers/panel.tsx Agent continuity control; triggers/continuation.ts

   Retrieved

   2026-11-13

3. Paseo: src/agent-sessions/index.ts

   Finding: The Hub selects/persists one agent session per project plus conversation continuation key and delivers each arriving request to that stored agent ID through connection.send. It does not create a fresh agent for each human message when Same conversation is selected. The UI continuity setting is product-owned and publicly configurable.

   Locator

   AgentSessions.dispatch findAgentSessionByKey and deliver; workflows/engine.ts continuationKey

   Retrieved

   2026-11-13

4. Paseo: docs/hub.md

   Finding: The released Paseo daemon documents opt-in Hub connection and hub.execute permission for ordinary agent creation, messaging, observation and recovery. Hub owns conversation routing and maps it to workspace/agent IDs; send_agent_message_request reaches the existing provider session with its native steer/queue behavior.

   Locator

   Connection and authority; Session grants and agent operations

   Retrieved

   2026-11-13

Team roles

Typed value: Yes.

Paseo Hub has owner, admin and member organization roles with enforced management permissions. Its public authentication composition has no enterprise SSO; daemon grants remain separate.

• Organization roles: Hub defines owner/admin/member roles and enforces separate member, owner and resource management capabilities.

Checked

2026-11-13 · checked 2 days ago

Plan

Not specified in this finding

Surface

Paseo daemon and APIs; Paseo Hub

Availability

beta

Version

Public Hub source commit 61e51c56f8756e40c55a30982160ce000f2aa177; inspected 2026-11-13

• Documentation and pinned source inspection only; no hands-on scenario was run.
• Other atomic questions remain unestablished: project_roles, provisioning, plan_scope.

1. Paseo: src/auth/organization-policy.ts

   Finding: Paseo Hub defines owner, admin and member roles. Owners manage members, owners and resources; admins manage members and resources but not owners; members can view but cannot manage them. Organization access and member-role mutation handlers enforce these capabilities.

   Locator

   ROLE_CAPABILITIES; organization-contract.ts ORGANIZATION_ROLES; organization-access.ts role mutations

   Retrieved

   2026-11-13

SSO

Typed value: No.

Paseo Hub has owner, admin and member organization roles with enforced management permissions. Its public authentication composition has no enterprise SSO; daemon grants remain separate.

• Sso: Hub enables email/password and organization membership without an enterprise SAML/OIDC SSO plugin.

Checked

2026-11-13 · checked 2 days ago

Plan

Not specified in this finding

Surface

Paseo daemon and APIs; Paseo Hub

Availability

beta

Version

Public Hub source commit 61e51c56f8756e40c55a30982160ce000f2aa177; inspected 2026-11-13

• Documentation and pinned source inspection only; no hands-on scenario was run.
• Other atomic questions remain unestablished: project_roles, provisioning, plan_scope.

1. Paseo: src/auth/server.ts

   Finding: The public Hub authentication composition enables email/password and the organization plugin. Inspection of src/auth, routes, schema and dependencies for SAML, OIDC, SSO and single sign-on found no enterprise SSO implementation. Provider app OAuth connections are workflow integrations, not enterprise user SSO.

   Locator

   createAuthServer emailAndPassword and plugins; src/auth; package.json

   Retrieved

   2026-11-13

Pull request workflow

Typed value: Yes.

Paseo creates worktrees and branches, drafts commit messages and PR text, opens PR workspaces and detects linked PRs; the changelog records pull and merge request support for GitLab, Gitea, Forgejo and Codeberg as well as GitHub. Merge and conflict handling are not documented as Paseo features; git runs through the user or agent.

• Commits: Commit messages are generated for changes being committed; agent or user runs git.
• Pull requests: PR title and body drafted from the diff; PR workspaces and PR detection; the changelog records forge support beyond GitHub (GitLab, Gitea, Forgejo, Codeberg).
• Ci response: Check summaries in PR panel; schedules can babysit builds.
• Product state: Workspace auto-archive after a merged PR appears in changelog fixes.

Checked

2026-11-07 · checked 1 week ago

Cross-check

cross-checked 2026-11-07

Plan

Not specified in this finding

Surface

Paseo desktop; Paseo daemon and APIs

Version

v0.11.1 release (tag ab10a6694); sources read at main d0bc188a5 (eight later commits)

• Commit and PR actions are done by the user or agent through normal git; no merge automation documented.

1. Paseo: CHANGELOG.md

   Finding: Re-read 2026-10-09 at pinned CHANGELOG.md (d0bc188, identical to main). The file is unchanged between the v0.11.1 tag and d0bc188; its top entry is 0.11.1 (2026-10-07) and there is no Unreleased heading. Earlier finding: 0.11.0 adds the plugin registry, Muse Code and Antigravity providers, a Usage view of subscription quota windows, and OMP mid-turn steering; 0.11.1 adds Claude Haiku 5.5 support and fixes subagent status and Claude history after daemon restart. Earlier entries mention push notifications, GitLab/Gitea/Forgejo/Codeberg PR support and PR check summaries.

   Locator

   0.11.1 and 0.11.0 sections

   Retrieved

   2026-10-09

   Source date

   2026-10-07

2. Paseo: Metadata generation

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Background model calls generate workspace titles, branch names, commit messages and PR titles/bodies from the diff.

   Locator

   public-docs/metadata-generation.md

   Retrieved

   2026-10-09

Review interface

Typed value: Yes.

Paseo shows workspace diffs and files, previews apps in built-in browser tabs and service proxy URLs, and browser automation on the desktop app can take screenshots; a gallery or revision-linked artifact store was not documented.

• Diffs: Changes tab shows workspace diffs.
• Screenshots: Browser automation can take screenshots on the desktop app.
• Previews: Built-in browser tabs and service proxy URLs preview workspace apps.

Checked

2026-11-07 · checked 1 week ago

Cross-check

cross-checked 2026-11-07

Plan

Not specified in this finding

Surface

Paseo desktop

Version

v0.11.1 release (tag ab10a6694); sources read at main d0bc188a5 (eight later commits)

• Documentation and source-level pass of Paseo v0.11.1; no hands-on scenario was run and unknown sub-questions remain unknown.

1. Paseo: Run parallel tasks

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Desktop walkthrough: separate worktree workspaces run agents concurrently, Changes tab for diffs, Files, terminals and built-in browser tabs; commit and PR via the user's usual git workflow or the agent; processes still share machine ports.

   Locator

   public-docs/parallel-development.md

   Retrieved

   2026-10-09

Product license: Apache-2.0

Typed value: Yes. Apache-2.0.

Paseo v0.15.3 root code is Apache-2.0 with third-party licence exceptions; its desktop manifest also declares Apache-2.0. Hub self-hosting is documented, but the separate relay licence, all package licences and hosted-service parity were not audited.

• Client license: Root LICENSE is Apache-2.0 except third-party components; desktop 0.15.3 manifest also declares Apache-2.0.
• Server license: Root notice applies Apache-2.0 to Paseo repository code including the daemon, except incorporated third-party components. A per-package dependency audit was not performed.
• Source visibility: Public GitHub stable release and pinned licence/component files are available.
• Source revision: Stable v0.15.3 annotated tag peels to d91ae138cb931447635e94296023414a58bedcc5; licence and desktop manifest inspected at that commit.

Checked

2026-11-07 · checked 1 week ago

Cross-check

cross-checked 2026-11-07

Plan

Not specified in this finding

Surface

Paseo desktop; Paseo daemon and APIs; Paseo Hub; Paseo CLI and TypeScript SDK

Version

v0.15.3 at d91ae138cb931447635e94296023414a58bedcc5

• Root licence and desktop manifest checked; dependency and separate relay licence audit not performed.
• Hub documentation establishes self-hosting instructions, not hosted-service parity.
• No installation or authenticated service test.

1. Paseo licence at v0.15.3

   Finding: Root notice licenses Paseo under Apache-2.0 except incorporated third-party components, which retain their own licences. Read at pinned stable v0.15.3; no hosted-service parity inferred.

   Locator

   LICENSE opening notice and Apache-2.0 terms

   Retrieved

   2026-11-07

2. Paseo desktop manifest at v0.15.3

   Finding: The @getpaseo/desktop Electron wrapper manifest is version 0.15.3 and declares Apache-2.0; depends on Paseo CLI and server packages. This checks the distributed desktop component manifest, not every dependency licence.

   Locator

   name, version and license fields

   Retrieved

   2026-11-07

Product license: MIT

Typed value: No. Apache-2.0.

Paseo v0.15.3 root code is Apache-2.0 with third-party licence exceptions; its desktop manifest also declares Apache-2.0. Hub self-hosting is documented, but the separate relay licence, all package licences and hosted-service parity were not audited.

• Client license: Root LICENSE is Apache-2.0 except third-party components; desktop 0.15.3 manifest also declares Apache-2.0.
• Server license: Root notice applies Apache-2.0 to Paseo repository code including the daemon, except incorporated third-party components. A per-package dependency audit was not performed.
• Source visibility: Public GitHub stable release and pinned licence/component files are available.
• Source revision: Stable v0.15.3 annotated tag peels to d91ae138cb931447635e94296023414a58bedcc5; licence and desktop manifest inspected at that commit.

Checked

2026-11-07 · checked 1 week ago

Cross-check

cross-checked 2026-11-07

Plan

Not specified in this finding

Surface

Paseo desktop; Paseo daemon and APIs; Paseo Hub; Paseo CLI and TypeScript SDK

Version

v0.15.3 at d91ae138cb931447635e94296023414a58bedcc5

• Root licence and desktop manifest checked; dependency and separate relay licence audit not performed.
• Hub documentation establishes self-hosting instructions, not hosted-service parity.
• No installation or authenticated service test.

1. Paseo licence at v0.15.3

   Finding: Root notice licenses Paseo under Apache-2.0 except incorporated third-party components, which retain their own licences. Read at pinned stable v0.15.3; no hosted-service parity inferred.

   Locator

   LICENSE opening notice and Apache-2.0 terms

   Retrieved

   2026-11-07

2. Paseo desktop manifest at v0.15.3

   Finding: The @getpaseo/desktop Electron wrapper manifest is version 0.15.3 and declares Apache-2.0; depends on Paseo CLI and server packages. This checks the distributed desktop component manifest, not every dependency licence.

   Locator

   name, version and license fields

   Retrieved

   2026-11-07

Product license: GPL-3.0

Typed value: No. Apache-2.0.

Paseo v0.15.3 root code is Apache-2.0 with third-party licence exceptions; its desktop manifest also declares Apache-2.0. Hub self-hosting is documented, but the separate relay licence, all package licences and hosted-service parity were not audited.

• Client license: Root LICENSE is Apache-2.0 except third-party components; desktop 0.15.3 manifest also declares Apache-2.0.
• Server license: Root notice applies Apache-2.0 to Paseo repository code including the daemon, except incorporated third-party components. A per-package dependency audit was not performed.
• Source visibility: Public GitHub stable release and pinned licence/component files are available.
• Source revision: Stable v0.15.3 annotated tag peels to d91ae138cb931447635e94296023414a58bedcc5; licence and desktop manifest inspected at that commit.

Checked

2026-11-07 · checked 1 week ago

Cross-check

cross-checked 2026-11-07

Plan

Not specified in this finding

Surface

Paseo desktop; Paseo daemon and APIs; Paseo Hub; Paseo CLI and TypeScript SDK

Version

v0.15.3 at d91ae138cb931447635e94296023414a58bedcc5

• Root licence and desktop manifest checked; dependency and separate relay licence audit not performed.
• Hub documentation establishes self-hosting instructions, not hosted-service parity.
• No installation or authenticated service test.

1. Paseo licence at v0.15.3

   Finding: Root notice licenses Paseo under Apache-2.0 except incorporated third-party components, which retain their own licences. Read at pinned stable v0.15.3; no hosted-service parity inferred.

   Locator

   LICENSE opening notice and Apache-2.0 terms

   Retrieved

   2026-11-07

2. Paseo desktop manifest at v0.15.3

   Finding: The @getpaseo/desktop Electron wrapper manifest is version 0.15.3 and declares Apache-2.0; depends on Paseo CLI and server packages. This checks the distributed desktop component manifest, not every dependency licence.

   Locator

   name, version and license fields

   Retrieved

   2026-11-07

Product license: GPL-3.0-or-later

Typed value: No. Apache-2.0.

Paseo v0.15.3 root code is Apache-2.0 with third-party licence exceptions; its desktop manifest also declares Apache-2.0. Hub self-hosting is documented, but the separate relay licence, all package licences and hosted-service parity were not audited.

• Client license: Root LICENSE is Apache-2.0 except third-party components; desktop 0.15.3 manifest also declares Apache-2.0.
• Server license: Root notice applies Apache-2.0 to Paseo repository code including the daemon, except incorporated third-party components. A per-package dependency audit was not performed.
• Source visibility: Public GitHub stable release and pinned licence/component files are available.
• Source revision: Stable v0.15.3 annotated tag peels to d91ae138cb931447635e94296023414a58bedcc5; licence and desktop manifest inspected at that commit.

Checked

2026-11-07 · checked 1 week ago

Cross-check

cross-checked 2026-11-07

Plan

Not specified in this finding

Surface

Paseo desktop; Paseo daemon and APIs; Paseo Hub; Paseo CLI and TypeScript SDK

Version

v0.15.3 at d91ae138cb931447635e94296023414a58bedcc5

• Root licence and desktop manifest checked; dependency and separate relay licence audit not performed.
• Hub documentation establishes self-hosting instructions, not hosted-service parity.
• No installation or authenticated service test.

1. Paseo licence at v0.15.3

   Finding: Root notice licenses Paseo under Apache-2.0 except incorporated third-party components, which retain their own licences. Read at pinned stable v0.15.3; no hosted-service parity inferred.

   Locator

   LICENSE opening notice and Apache-2.0 terms

   Retrieved

   2026-11-07

2. Paseo desktop manifest at v0.15.3

   Finding: The @getpaseo/desktop Electron wrapper manifest is version 0.15.3 and declares Apache-2.0; depends on Paseo CLI and server packages. This checks the distributed desktop component manifest, not every dependency licence.

   Locator

   name, version and license fields

   Retrieved

   2026-11-07

Product license: AGPL-3.0

Typed value: No. Apache-2.0.

Paseo v0.15.3 root code is Apache-2.0 with third-party licence exceptions; its desktop manifest also declares Apache-2.0. Hub self-hosting is documented, but the separate relay licence, all package licences and hosted-service parity were not audited.

• Client license: Root LICENSE is Apache-2.0 except third-party components; desktop 0.15.3 manifest also declares Apache-2.0.
• Server license: Root notice applies Apache-2.0 to Paseo repository code including the daemon, except incorporated third-party components. A per-package dependency audit was not performed.
• Source visibility: Public GitHub stable release and pinned licence/component files are available.
• Source revision: Stable v0.15.3 annotated tag peels to d91ae138cb931447635e94296023414a58bedcc5; licence and desktop manifest inspected at that commit.

Checked

2026-11-07 · checked 1 week ago

Cross-check

cross-checked 2026-11-07

Plan

Not specified in this finding

Surface

Paseo desktop; Paseo daemon and APIs; Paseo Hub; Paseo CLI and TypeScript SDK

Version

v0.15.3 at d91ae138cb931447635e94296023414a58bedcc5

• Root licence and desktop manifest checked; dependency and separate relay licence audit not performed.
• Hub documentation establishes self-hosting instructions, not hosted-service parity.
• No installation or authenticated service test.

1. Paseo licence at v0.15.3

   Finding: Root notice licenses Paseo under Apache-2.0 except incorporated third-party components, which retain their own licences. Read at pinned stable v0.15.3; no hosted-service parity inferred.

   Locator

   LICENSE opening notice and Apache-2.0 terms

   Retrieved

   2026-11-07

2. Paseo desktop manifest at v0.15.3

   Finding: The @getpaseo/desktop Electron wrapper manifest is version 0.15.3 and declares Apache-2.0; depends on Paseo CLI and server packages. This checks the distributed desktop component manifest, not every dependency licence.

   Locator

   name, version and license fields

   Retrieved

   2026-11-07

Product license: AGPL-3.0-or-later

Typed value: No. Apache-2.0.

Paseo v0.15.3 root code is Apache-2.0 with third-party licence exceptions; its desktop manifest also declares Apache-2.0. Hub self-hosting is documented, but the separate relay licence, all package licences and hosted-service parity were not audited.

• Client license: Root LICENSE is Apache-2.0 except third-party components; desktop 0.15.3 manifest also declares Apache-2.0.
• Server license: Root notice applies Apache-2.0 to Paseo repository code including the daemon, except incorporated third-party components. A per-package dependency audit was not performed.
• Source visibility: Public GitHub stable release and pinned licence/component files are available.
• Source revision: Stable v0.15.3 annotated tag peels to d91ae138cb931447635e94296023414a58bedcc5; licence and desktop manifest inspected at that commit.

Checked

2026-11-07 · checked 1 week ago

Cross-check

cross-checked 2026-11-07

Plan

Not specified in this finding

Surface

Paseo desktop; Paseo daemon and APIs; Paseo Hub; Paseo CLI and TypeScript SDK

Version

v0.15.3 at d91ae138cb931447635e94296023414a58bedcc5

• Root licence and desktop manifest checked; dependency and separate relay licence audit not performed.
• Hub documentation establishes self-hosting instructions, not hosted-service parity.
• No installation or authenticated service test.

1. Paseo licence at v0.15.3

   Finding: Root notice licenses Paseo under Apache-2.0 except incorporated third-party components, which retain their own licences. Read at pinned stable v0.15.3; no hosted-service parity inferred.

   Locator

   LICENSE opening notice and Apache-2.0 terms

   Retrieved

   2026-11-07

2. Paseo desktop manifest at v0.15.3

   Finding: The @getpaseo/desktop Electron wrapper manifest is version 0.15.3 and declares Apache-2.0; depends on Paseo CLI and server packages. This checks the distributed desktop component manifest, not every dependency licence.

   Locator

   name, version and license fields

   Retrieved

   2026-11-07

Product license: Elastic License 2.0

Typed value: No. Apache-2.0.

Paseo v0.15.3 root code is Apache-2.0 with third-party licence exceptions; its desktop manifest also declares Apache-2.0. Hub self-hosting is documented, but the separate relay licence, all package licences and hosted-service parity were not audited.

• Client license: Root LICENSE is Apache-2.0 except third-party components; desktop 0.15.3 manifest also declares Apache-2.0.
• Server license: Root notice applies Apache-2.0 to Paseo repository code including the daemon, except incorporated third-party components. A per-package dependency audit was not performed.
• Source visibility: Public GitHub stable release and pinned licence/component files are available.
• Source revision: Stable v0.15.3 annotated tag peels to d91ae138cb931447635e94296023414a58bedcc5; licence and desktop manifest inspected at that commit.

Checked

2026-11-07 · checked 1 week ago

Cross-check

cross-checked 2026-11-07

Plan

Not specified in this finding

Surface

Paseo desktop; Paseo daemon and APIs; Paseo Hub; Paseo CLI and TypeScript SDK

Version

v0.15.3 at d91ae138cb931447635e94296023414a58bedcc5

• Root licence and desktop manifest checked; dependency and separate relay licence audit not performed.
• Hub documentation establishes self-hosting instructions, not hosted-service parity.
• No installation or authenticated service test.

1. Paseo licence at v0.15.3

   Finding: Root notice licenses Paseo under Apache-2.0 except incorporated third-party components, which retain their own licences. Read at pinned stable v0.15.3; no hosted-service parity inferred.

   Locator

   LICENSE opening notice and Apache-2.0 terms

   Retrieved

   2026-11-07

2. Paseo desktop manifest at v0.15.3

   Finding: The @getpaseo/desktop Electron wrapper manifest is version 0.15.3 and declares Apache-2.0; depends on Paseo CLI and server packages. This checks the distributed desktop component manifest, not every dependency licence.

   Locator

   name, version and license fields

   Retrieved

   2026-11-07

Product license: Custom terms

Typed value: No. Apache-2.0.

Paseo v0.15.3 root code is Apache-2.0 with third-party licence exceptions; its desktop manifest also declares Apache-2.0. Hub self-hosting is documented, but the separate relay licence, all package licences and hosted-service parity were not audited.

• Client license: Root LICENSE is Apache-2.0 except third-party components; desktop 0.15.3 manifest also declares Apache-2.0.
• Server license: Root notice applies Apache-2.0 to Paseo repository code including the daemon, except incorporated third-party components. A per-package dependency audit was not performed.
• Source visibility: Public GitHub stable release and pinned licence/component files are available.
• Source revision: Stable v0.15.3 annotated tag peels to d91ae138cb931447635e94296023414a58bedcc5; licence and desktop manifest inspected at that commit.

Checked

2026-11-07 · checked 1 week ago

Cross-check

cross-checked 2026-11-07

Plan

Not specified in this finding

Surface

Paseo desktop; Paseo daemon and APIs; Paseo Hub; Paseo CLI and TypeScript SDK

Version

v0.15.3 at d91ae138cb931447635e94296023414a58bedcc5

• Root licence and desktop manifest checked; dependency and separate relay licence audit not performed.
• Hub documentation establishes self-hosting instructions, not hosted-service parity.
• No installation or authenticated service test.

1. Paseo licence at v0.15.3

   Finding: Root notice licenses Paseo under Apache-2.0 except incorporated third-party components, which retain their own licences. Read at pinned stable v0.15.3; no hosted-service parity inferred.

   Locator

   LICENSE opening notice and Apache-2.0 terms

   Retrieved

   2026-11-07

2. Paseo desktop manifest at v0.15.3

   Finding: The @getpaseo/desktop Electron wrapper manifest is version 0.15.3 and declares Apache-2.0; depends on Paseo CLI and server packages. This checks the distributed desktop component manifest, not every dependency licence.

   Locator

   name, version and license fields

   Retrieved

   2026-11-07

Product license: Proprietary

Typed value: No. Apache-2.0.

Paseo v0.15.3 root code is Apache-2.0 with third-party licence exceptions; its desktop manifest also declares Apache-2.0. Hub self-hosting is documented, but the separate relay licence, all package licences and hosted-service parity were not audited.

• Client license: Root LICENSE is Apache-2.0 except third-party components; desktop 0.15.3 manifest also declares Apache-2.0.
• Server license: Root notice applies Apache-2.0 to Paseo repository code including the daemon, except incorporated third-party components. A per-package dependency audit was not performed.
• Source visibility: Public GitHub stable release and pinned licence/component files are available.
• Source revision: Stable v0.15.3 annotated tag peels to d91ae138cb931447635e94296023414a58bedcc5; licence and desktop manifest inspected at that commit.

Checked

2026-11-07 · checked 1 week ago

Cross-check

cross-checked 2026-11-07

Plan

Not specified in this finding

Surface

Paseo desktop; Paseo daemon and APIs; Paseo Hub; Paseo CLI and TypeScript SDK

Version

v0.15.3 at d91ae138cb931447635e94296023414a58bedcc5

• Root licence and desktop manifest checked; dependency and separate relay licence audit not performed.
• Hub documentation establishes self-hosting instructions, not hosted-service parity.
• No installation or authenticated service test.

1. Paseo licence at v0.15.3

   Finding: Root notice licenses Paseo under Apache-2.0 except incorporated third-party components, which retain their own licences. Read at pinned stable v0.15.3; no hosted-service parity inferred.

   Locator

   LICENSE opening notice and Apache-2.0 terms

   Retrieved

   2026-11-07

2. Paseo desktop manifest at v0.15.3

   Finding: The @getpaseo/desktop Electron wrapper manifest is version 0.15.3 and declares Apache-2.0; depends on Paseo CLI and server packages. This checks the distributed desktop component manifest, not every dependency licence.

   Locator

   name, version and license fields

   Retrieved

   2026-11-07

Self-hosting

Typed value: Yes.

Paseo runs entirely on user machines, with optional relay and Hub; self-hosting Hub is documented. Export and import formats were not documented.

• Self hosting: Daemon via desktop, npm or Docker; Hub via npx @getpaseo/hub with embedded or PostgreSQL storage.

Checked

2026-11-07 · checked 1 week ago

Cross-check

cross-checked 2026-11-07

Plan

Not specified in this finding

Surface

Paseo daemon and APIs; Paseo Hub

Version

v0.11.1 release (tag ab10a6694); sources read at main d0bc188a5 (eight later commits)

• Documentation and source-level pass of Paseo v0.11.1; no hands-on scenario was run and unknown sub-questions remain unknown.

1. Paseo: Getting started

   Finding: Desktop app bundles its own daemon; Linux .deb/.rpm/AppImage; headless install via npm i -g @getpaseo/cli; Docker image; at least one provider CLI must be installed by the user; gh CLI recommended for PR-aware worktrees.

   Locator

   public-docs/index.md

   Retrieved

   2026-10-08

2. Paseo: Self-hosting Hub

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): npx @getpaseo/hub runs Hub locally with embedded PGlite storage or PostgreSQL via DATABASE_URL; public HTTPS needed for GitHub webhooks; self-hosted uses user-created provider apps.

   Locator

   public-docs/hub/self-hosting/index.md

   Retrieved

   2026-10-09

3. Paseo: Docker

   Finding: Official image ghcr.io/getpaseo/paseo runs the daemon and bundled web UI as non-root user; does not bundle agent CLIs; PASEO_PASSWORD recommended before publishing the port; state under /home/paseo.

   Locator

   public-docs/docker.md

   Retrieved

   2026-10-08

Free access

Typed value: Yes.

The Paseo app, daemon, CLI and SDK are free and open source with no usage cap documented; hosted Hub offers a no-card, non-expiring Free plan (50 runs, 1 seat) and a self-hosted Hub is free.

• Ongoing free: Core app is free; Hub Free needs no card and does not expire.
• Card required: Hub Free requires no card.

Checked

2026-11-07 · checked 1 week ago

Cross-check

cross-checked 2026-11-07

Plan

Free

Surface

Paseo desktop; Paseo Hub

Version

Paseo v0.15.3 at d91ae138cb931447635e94296023414a58bedcc5; hosted Hub page reread 2026-11-07

• Free tier limits for Hub are vendor-stated; users still pay their own provider plans.
• Hub maturity is ambiguous: the live Hub page refers to "access to the beta" (hub-live-faq), and no GA or preview label was found. Hub pricing and signup are read as availability; its maturity status is not established.

1. Paseo homepage

   Finding: Current homepage presents desktop/mobile/web/CLI and SDK control of user-hosted agents, native Claude/Codex/OpenCode/Pi/OMP/Antigravity/Muse and additional ACP tools. App is free/open source, with optional E2E relay and user provider accounts.

   Locator

   Run it anywhere; providers; FAQ; sponsor section

   Retrieved

   2026-11-07

2. Paseo: Hosted Hub

   Finding: Managed service at hub.paseo.sh; organizations start on Free (one seat, monthly run allowance, no card, no expiry); Pro for unlimited runs, more seats and invitations; self-hosted Hub has no plans or billing.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

Starting price: Free

Typed value: Yes. Free.

The Paseo app, daemon, CLI and SDK are free and open source with no usage cap documented; hosted Hub offers a no-card, non-expiring Free plan (50 runs, 1 seat) and a self-hosted Hub is free.

• Ongoing free: Core app is free; Hub Free needs no card and does not expire.
• Card required: Hub Free requires no card.

Checked

2026-11-07 · checked 1 week ago

Cross-check

cross-checked 2026-11-07

Plan

Free

Surface

Paseo desktop; Paseo Hub

Version

Paseo v0.15.3 at d91ae138cb931447635e94296023414a58bedcc5; hosted Hub page reread 2026-11-07

• Free tier limits for Hub are vendor-stated; users still pay their own provider plans.
• Hub maturity is ambiguous: the live Hub page refers to "access to the beta" (hub-live-faq), and no GA or preview label was found. Hub pricing and signup are read as availability; its maturity status is not established.

1. Paseo homepage

   Finding: Current homepage presents desktop/mobile/web/CLI and SDK control of user-hosted agents, native Claude/Codex/OpenCode/Pi/OMP/Antigravity/Muse and additional ACP tools. App is free/open source, with optional E2E relay and user provider accounts.

   Locator

   Run it anywhere; providers; FAQ; sponsor section

   Retrieved

   2026-11-07

2. Paseo: Hosted Hub

   Finding: Managed service at hub.paseo.sh; organizations start on Free (one seat, monthly run allowance, no card, no expiry); Pro for unlimited runs, more seats and invitations; self-hosted Hub has no plans or billing.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

Starting price: Up to $20/month

Typed value: No. Free.

The Paseo app, daemon, CLI and SDK are free and open source with no usage cap documented; hosted Hub offers a no-card, non-expiring Free plan (50 runs, 1 seat) and a self-hosted Hub is free.

• Ongoing free: Core app is free; Hub Free needs no card and does not expire.
• Card required: Hub Free requires no card.

Checked

2026-11-07 · checked 1 week ago

Cross-check

cross-checked 2026-11-07

Plan

Free

Surface

Paseo desktop; Paseo Hub

Version

Paseo v0.15.3 at d91ae138cb931447635e94296023414a58bedcc5; hosted Hub page reread 2026-11-07

• Free tier limits for Hub are vendor-stated; users still pay their own provider plans.
• Hub maturity is ambiguous: the live Hub page refers to "access to the beta" (hub-live-faq), and no GA or preview label was found. Hub pricing and signup are read as availability; its maturity status is not established.

1. Paseo homepage

   Finding: Current homepage presents desktop/mobile/web/CLI and SDK control of user-hosted agents, native Claude/Codex/OpenCode/Pi/OMP/Antigravity/Muse and additional ACP tools. App is free/open source, with optional E2E relay and user provider accounts.

   Locator

   Run it anywhere; providers; FAQ; sponsor section

   Retrieved

   2026-11-07

2. Paseo: Hosted Hub

   Finding: Managed service at hub.paseo.sh; organizations start on Free (one seat, monthly run allowance, no card, no expiry); Pro for unlimited runs, more seats and invitations; self-hosted Hub has no plans or billing.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

Starting price: $21–40/month

Typed value: No. Free.

The Paseo app, daemon, CLI and SDK are free and open source with no usage cap documented; hosted Hub offers a no-card, non-expiring Free plan (50 runs, 1 seat) and a self-hosted Hub is free.

• Ongoing free: Core app is free; Hub Free needs no card and does not expire.
• Card required: Hub Free requires no card.

Checked

2026-11-07 · checked 1 week ago

Cross-check

cross-checked 2026-11-07

Plan

Free

Surface

Paseo desktop; Paseo Hub

Version

Paseo v0.15.3 at d91ae138cb931447635e94296023414a58bedcc5; hosted Hub page reread 2026-11-07

• Free tier limits for Hub are vendor-stated; users still pay their own provider plans.
• Hub maturity is ambiguous: the live Hub page refers to "access to the beta" (hub-live-faq), and no GA or preview label was found. Hub pricing and signup are read as availability; its maturity status is not established.

1. Paseo homepage

   Finding: Current homepage presents desktop/mobile/web/CLI and SDK control of user-hosted agents, native Claude/Codex/OpenCode/Pi/OMP/Antigravity/Muse and additional ACP tools. App is free/open source, with optional E2E relay and user provider accounts.

   Locator

   Run it anywhere; providers; FAQ; sponsor section

   Retrieved

   2026-11-07

2. Paseo: Hosted Hub

   Finding: Managed service at hub.paseo.sh; organizations start on Free (one seat, monthly run allowance, no card, no expiry); Pro for unlimited runs, more seats and invitations; self-hosted Hub has no plans or billing.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

Starting price: $41–100/month

Typed value: No. Free.

The Paseo app, daemon, CLI and SDK are free and open source with no usage cap documented; hosted Hub offers a no-card, non-expiring Free plan (50 runs, 1 seat) and a self-hosted Hub is free.

• Ongoing free: Core app is free; Hub Free needs no card and does not expire.
• Card required: Hub Free requires no card.

Checked

2026-11-07 · checked 1 week ago

Cross-check

cross-checked 2026-11-07

Plan

Free

Surface

Paseo desktop; Paseo Hub

Version

Paseo v0.15.3 at d91ae138cb931447635e94296023414a58bedcc5; hosted Hub page reread 2026-11-07

• Free tier limits for Hub are vendor-stated; users still pay their own provider plans.
• Hub maturity is ambiguous: the live Hub page refers to "access to the beta" (hub-live-faq), and no GA or preview label was found. Hub pricing and signup are read as availability; its maturity status is not established.

1. Paseo homepage

   Finding: Current homepage presents desktop/mobile/web/CLI and SDK control of user-hosted agents, native Claude/Codex/OpenCode/Pi/OMP/Antigravity/Muse and additional ACP tools. App is free/open source, with optional E2E relay and user provider accounts.

   Locator

   Run it anywhere; providers; FAQ; sponsor section

   Retrieved

   2026-11-07

2. Paseo: Hosted Hub

   Finding: Managed service at hub.paseo.sh; organizations start on Free (one seat, monthly run allowance, no card, no expiry); Pro for unlimited runs, more seats and invitations; self-hosted Hub has no plans or billing.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

Starting price: Over $100/month

Typed value: No. Free.

The Paseo app, daemon, CLI and SDK are free and open source with no usage cap documented; hosted Hub offers a no-card, non-expiring Free plan (50 runs, 1 seat) and a self-hosted Hub is free.

• Ongoing free: Core app is free; Hub Free needs no card and does not expire.
• Card required: Hub Free requires no card.

Checked

2026-11-07 · checked 1 week ago

Cross-check

cross-checked 2026-11-07

Plan

Free

Surface

Paseo desktop; Paseo Hub

Version

Paseo v0.15.3 at d91ae138cb931447635e94296023414a58bedcc5; hosted Hub page reread 2026-11-07

• Free tier limits for Hub are vendor-stated; users still pay their own provider plans.
• Hub maturity is ambiguous: the live Hub page refers to "access to the beta" (hub-live-faq), and no GA or preview label was found. Hub pricing and signup are read as availability; its maturity status is not established.

1. Paseo homepage

   Finding: Current homepage presents desktop/mobile/web/CLI and SDK control of user-hosted agents, native Claude/Codex/OpenCode/Pi/OMP/Antigravity/Muse and additional ACP tools. App is free/open source, with optional E2E relay and user provider accounts.

   Locator

   Run it anywhere; providers; FAQ; sponsor section

   Retrieved

   2026-11-07

2. Paseo: Hosted Hub

   Finding: Managed service at hub.paseo.sh; organizations start on Free (one seat, monthly run allowance, no card, no expiry); Pro for unlimited runs, more seats and invitations; self-hosted Hub has no plans or billing.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

Starting price: Contact for pricing

Typed value: No. Free.

The Paseo app, daemon, CLI and SDK are free and open source with no usage cap documented; hosted Hub offers a no-card, non-expiring Free plan (50 runs, 1 seat) and a self-hosted Hub is free.

• Ongoing free: Core app is free; Hub Free needs no card and does not expire.
• Card required: Hub Free requires no card.

Checked

2026-11-07 · checked 1 week ago

Cross-check

cross-checked 2026-11-07

Plan

Free

Surface

Paseo desktop; Paseo Hub

Version

Paseo v0.15.3 at d91ae138cb931447635e94296023414a58bedcc5; hosted Hub page reread 2026-11-07

• Free tier limits for Hub are vendor-stated; users still pay their own provider plans.
• Hub maturity is ambiguous: the live Hub page refers to "access to the beta" (hub-live-faq), and no GA or preview label was found. Hub pricing and signup are read as availability; its maturity status is not established.

1. Paseo homepage

   Finding: Current homepage presents desktop/mobile/web/CLI and SDK control of user-hosted agents, native Claude/Codex/OpenCode/Pi/OMP/Antigravity/Muse and additional ACP tools. App is free/open source, with optional E2E relay and user provider accounts.

   Locator

   Run it anywhere; providers; FAQ; sponsor section

   Retrieved

   2026-11-07

2. Paseo: Hosted Hub

   Finding: Managed service at hub.paseo.sh; organizations start on Free (one seat, monthly run allowance, no card, no expiry); Pro for unlimited runs, more seats and invitations; self-hosted Hub has no plans or billing.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

Pricing model: Free, no paid plan

Typed value: No.

The Paseo app, daemon, CLI and SDK are free; hosted Hub is Free ($0, 50 agent runs/month, 1 seat) or Pro ($15 per seat per month, unlimited runs); model and compute costs are the user's.

• Currency: Price shown with $ symbol; currency not named.
• Interval: Monthly.
• Seats: Pro $15 per seat; Free 1 seat; trigger-only users do not count; invitations count.
• Included usage: Free: 50 agent runs per month; Pro unlimited runs.

Checked

2026-11-13 · checked 2 days ago

Plan

Hub Free / Pro; self-hosted

Surface

Paseo Hub

Version

Paseo v0.15.3 at d91ae138cb931447635e94296023414a58bedcc5; hosted Hub page reread 2026-11-07

• Currency is shown as $ without naming it; taxes, trial and overage terms not stated; prices read from the vendor pricing page.

1. Paseo Hub plans and pricing

   Finding: Re-read 2026-10-09 (live pricing page): self-hosted Hub is free and open source; Free is $0 per month with 50 agent runs a month and 1 seat; Pro is $15 per seat per month with unlimited runs and seats. Seats are Hub members plus pending invitations; people who only trigger agents through GitHub, Slack or Discord do not count. No card, trial, expiry, SSO, retention or compliance terms are stated on the page. Planned items are listed as "Not built yet" with no dates: provisioning daemons for a team, sharing settings and skills across a team, more integrations.

   Locator

   Plans section

   Retrieved

   2026-11-07

2. Paseo: Hosted Hub

   Finding: Managed service at hub.paseo.sh; organizations start on Free (one seat, monthly run allowance, no card, no expiry); Pro for unlimited runs, more seats and invitations; self-hosted Hub has no plans or billing.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

Pricing model: Free plan

Typed value: Yes.

The Paseo app, daemon, CLI and SDK are free; hosted Hub is Free ($0, 50 agent runs/month, 1 seat) or Pro ($15 per seat per month, unlimited runs); model and compute costs are the user's.

• Currency: Price shown with $ symbol; currency not named.
• Interval: Monthly.
• Seats: Pro $15 per seat; Free 1 seat; trigger-only users do not count; invitations count.
• Included usage: Free: 50 agent runs per month; Pro unlimited runs.

Checked

2026-11-07 · checked 1 week ago

Cross-check

cross-checked 2026-11-10

Plan

Hub Free / Pro; self-hosted

Surface

Paseo Hub

Version

Paseo v0.15.3 at d91ae138cb931447635e94296023414a58bedcc5; hosted Hub page reread 2026-11-07

• Currency is shown as $ without naming it; taxes, trial and overage terms not stated; prices read from the vendor pricing page.

1. Paseo Hub plans and pricing

   Finding: Re-read 2026-10-09 (live pricing page): self-hosted Hub is free and open source; Free is $0 per month with 50 agent runs a month and 1 seat; Pro is $15 per seat per month with unlimited runs and seats. Seats are Hub members plus pending invitations; people who only trigger agents through GitHub, Slack or Discord do not count. No card, trial, expiry, SSO, retention or compliance terms are stated on the page. Planned items are listed as "Not built yet" with no dates: provisioning daemons for a team, sharing settings and skills across a team, more integrations.

   Locator

   Plans section

   Retrieved

   2026-11-07

Pricing model: Subscription

Typed value: Yes.

The Paseo app, daemon, CLI and SDK are free; hosted Hub is Free ($0, 50 agent runs/month, 1 seat) or Pro ($15 per seat per month, unlimited runs); model and compute costs are the user's.

• Currency: Price shown with $ symbol; currency not named.
• Interval: Monthly.
• Seats: Pro $15 per seat; Free 1 seat; trigger-only users do not count; invitations count.
• Included usage: Free: 50 agent runs per month; Pro unlimited runs.

Checked

2026-11-13 · checked 2 days ago

Plan

Hub Free / Pro; self-hosted

Surface

Paseo Hub

Version

Paseo v0.15.3 at d91ae138cb931447635e94296023414a58bedcc5; hosted Hub page reread 2026-11-07

• Currency is shown as $ without naming it; taxes, trial and overage terms not stated; prices read from the vendor pricing page.

1. Paseo Hub plans and pricing

   Finding: Re-read 2026-10-09 (live pricing page): self-hosted Hub is free and open source; Free is $0 per month with 50 agent runs a month and 1 seat; Pro is $15 per seat per month with unlimited runs and seats. Seats are Hub members plus pending invitations; people who only trigger agents through GitHub, Slack or Discord do not count. No card, trial, expiry, SSO, retention or compliance terms are stated on the page. Planned items are listed as "Not built yet" with no dates: provisioning daemons for a team, sharing settings and skills across a team, more integrations.

   Locator

   Plans section

   Retrieved

   2026-11-07

2. Paseo: Hosted Hub

   Finding: Managed service at hub.paseo.sh; organizations start on Free (one seat, monthly run allowance, no card, no expiry); Pro for unlimited runs, more seats and invitations; self-hosted Hub has no plans or billing.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

Pricing model: Per seat

Typed value: Yes.

The Paseo app, daemon, CLI and SDK are free; hosted Hub is Free ($0, 50 agent runs/month, 1 seat) or Pro ($15 per seat per month, unlimited runs); model and compute costs are the user's.

• Currency: Price shown with $ symbol; currency not named.
• Interval: Monthly.
• Seats: Pro $15 per seat; Free 1 seat; trigger-only users do not count; invitations count.
• Included usage: Free: 50 agent runs per month; Pro unlimited runs.

Checked

2026-11-07 · checked 1 week ago

Cross-check

cross-checked 2026-11-10

Plan

Hub Free / Pro; self-hosted

Surface

Paseo Hub

Version

Paseo v0.15.3 at d91ae138cb931447635e94296023414a58bedcc5; hosted Hub page reread 2026-11-07

• Currency is shown as $ without naming it; taxes, trial and overage terms not stated; prices read from the vendor pricing page.

1. Paseo Hub plans and pricing

   Finding: Re-read 2026-10-09 (live pricing page): self-hosted Hub is free and open source; Free is $0 per month with 50 agent runs a month and 1 seat; Pro is $15 per seat per month with unlimited runs and seats. Seats are Hub members plus pending invitations; people who only trigger agents through GitHub, Slack or Discord do not count. No card, trial, expiry, SSO, retention or compliance terms are stated on the page. Planned items are listed as "Not built yet" with no dates: provisioning daemons for a team, sharing settings and skills across a team, more integrations.

   Locator

   Plans section

   Retrieved

   2026-11-07

Pricing model: Usage-based

Typed value: No.

The Paseo app, daemon, CLI and SDK are free; hosted Hub is Free ($0, 50 agent runs/month, 1 seat) or Pro ($15 per seat per month, unlimited runs); model and compute costs are the user's.

• Currency: Price shown with $ symbol; currency not named.
• Interval: Monthly.
• Seats: Pro $15 per seat; Free 1 seat; trigger-only users do not count; invitations count.
• Included usage: Free: 50 agent runs per month; Pro unlimited runs.

Checked

2026-11-13 · checked 2 days ago

Plan

Hub Free / Pro; self-hosted

Surface

Paseo Hub

Version

Paseo v0.15.3 at d91ae138cb931447635e94296023414a58bedcc5; hosted Hub page reread 2026-11-07

• Currency is shown as $ without naming it; taxes, trial and overage terms not stated; prices read from the vendor pricing page.

1. Paseo Hub plans and pricing

   Finding: Re-read 2026-10-09 (live pricing page): self-hosted Hub is free and open source; Free is $0 per month with 50 agent runs a month and 1 seat; Pro is $15 per seat per month with unlimited runs and seats. Seats are Hub members plus pending invitations; people who only trigger agents through GitHub, Slack or Discord do not count. No card, trial, expiry, SSO, retention or compliance terms are stated on the page. Planned items are listed as "Not built yet" with no dates: provisioning daemons for a team, sharing settings and skills across a team, more integrations.

   Locator

   Plans section

   Retrieved

   2026-11-07

2. Paseo: Hosted Hub

   Finding: Managed service at hub.paseo.sh; organizations start on Free (one seat, monthly run allowance, no card, no expiry); Pro for unlimited runs, more seats and invitations; self-hosted Hub has no plans or billing.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

Pricing model: Per machine or compute

Typed value: No.

The Paseo app, daemon, CLI and SDK are free; hosted Hub is Free ($0, 50 agent runs/month, 1 seat) or Pro ($15 per seat per month, unlimited runs); model and compute costs are the user's.

• Currency: Price shown with $ symbol; currency not named.
• Interval: Monthly.
• Seats: Pro $15 per seat; Free 1 seat; trigger-only users do not count; invitations count.
• Included usage: Free: 50 agent runs per month; Pro unlimited runs.

Checked

2026-11-13 · checked 2 days ago

Plan

Hub Free / Pro; self-hosted

Surface

Paseo Hub

Version

Paseo v0.15.3 at d91ae138cb931447635e94296023414a58bedcc5; hosted Hub page reread 2026-11-07

• Currency is shown as $ without naming it; taxes, trial and overage terms not stated; prices read from the vendor pricing page.

1. Paseo Hub plans and pricing

   Finding: Re-read 2026-10-09 (live pricing page): self-hosted Hub is free and open source; Free is $0 per month with 50 agent runs a month and 1 seat; Pro is $15 per seat per month with unlimited runs and seats. Seats are Hub members plus pending invitations; people who only trigger agents through GitHub, Slack or Discord do not count. No card, trial, expiry, SSO, retention or compliance terms are stated on the page. Planned items are listed as "Not built yet" with no dates: provisioning daemons for a team, sharing settings and skills across a team, more integrations.

   Locator

   Plans section

   Retrieved

   2026-11-07

2. Paseo: Hosted Hub

   Finding: Managed service at hub.paseo.sh; organizations start on Free (one seat, monthly run allowance, no card, no expiry); Pro for unlimited runs, more seats and invitations; self-hosted Hub has no plans or billing.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

Pricing model: Bring your own key

Typed value: Yes.

Paseo reuses each provider CLI's own login for Claude plan, ChatGPT plan and API-key use, and adds no charge for Claude Code or Codex. Optional custom-provider and speech credentials can be written to Paseo config.

• Agent subscriptions: Claude Code usage counts against the normal Claude plan; Codex can use ChatGPT plan access.
• Api accounts: Codex can use an OpenAI API key; OpenCode uses provider API keys through its CLI. Custom provider env entries (for example ANTHROPIC_API_KEY) and speech provider keys can be written to Paseo config (custom-providers and voice docs at the tag). That is optional configuration, not the normal login path.

Checked

2026-11-07 · checked 1 week ago

Cross-check

cross-checked 2026-11-10

Plan

Not specified in this finding

Surface

Paseo daemon and APIs; Paseo desktop

Version

Paseo v0.15.3 at d91ae138cb931447635e94296023414a58bedcc5; hosted Hub page reread 2026-11-07

• Credentials for the normal login path stay in the provider CLI. Multiple accounts are supported per provider: profiles bind different credentials per provider entry (custom-providers docs, Multiple profiles), and agents respect custom CLAUDE_CONFIG_DIR and CODEX_HOME homes (changelog, PR #5465). The exact user action for switching between accounts is not documented. Vendor-side restrictions are not documented by Paseo.
• Claude plan requirement and limits are Anthropic's, per Paseo's own docs.

1. Paseo: Codex provider

   Finding: No Paseo charge for Codex; sign in with ChatGPT (plan access) or an OpenAI API key.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

Pricing model: One-time purchase

Typed value: No.

The Paseo app, daemon, CLI and SDK are free; hosted Hub is Free ($0, 50 agent runs/month, 1 seat) or Pro ($15 per seat per month, unlimited runs); model and compute costs are the user's.

• Currency: Price shown with $ symbol; currency not named.
• Interval: Monthly.
• Seats: Pro $15 per seat; Free 1 seat; trigger-only users do not count; invitations count.
• Included usage: Free: 50 agent runs per month; Pro unlimited runs.

Checked

2026-11-13 · checked 2 days ago

Plan

Hub Free / Pro; self-hosted

Surface

Paseo Hub

Version

Paseo v0.15.3 at d91ae138cb931447635e94296023414a58bedcc5; hosted Hub page reread 2026-11-07

• Currency is shown as $ without naming it; taxes, trial and overage terms not stated; prices read from the vendor pricing page.

1. Paseo Hub plans and pricing

   Finding: Re-read 2026-10-09 (live pricing page): self-hosted Hub is free and open source; Free is $0 per month with 50 agent runs a month and 1 seat; Pro is $15 per seat per month with unlimited runs and seats. Seats are Hub members plus pending invitations; people who only trigger agents through GitHub, Slack or Discord do not count. No card, trial, expiry, SSO, retention or compliance terms are stated on the page. Planned items are listed as "Not built yet" with no dates: provisioning daemons for a team, sharing settings and skills across a team, more integrations.

   Locator

   Plans section

   Retrieved

   2026-11-07

2. Paseo: Hosted Hub

   Finding: Managed service at hub.paseo.sh; organizations start on Free (one seat, monthly run allowance, no card, no expiry); Pro for unlimited runs, more seats and invitations; self-hosted Hub has no plans or billing.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

Keeps going with laptop closed

Typed value: Yes.

Paseo runs agents on operator-owned local or server daemon machines. Clients attach independently, while hosted Hub only dispatches to connected user daemons and does not provide agent compute.

• Local: The desktop app starts/manages a local daemon and agents use files/tools on that machine.
• Byo remote: The guide deliberately supports running the environment on a server and remote SSH/Tailscale client attachment.
• Client disconnect: The daemon owns running agents/workspaces independently of its thin clients; the separately hosted daemon must stay running.

Checked

2026-11-13 · checked 2 days ago

Plan

Not specified in this finding

Surface

Paseo daemon and APIs; Paseo desktop; Paseo mobile; Paseo web; Paseo CLI and TypeScript SDK

Version

Paseo v0.15.4 at 1c00b365c9e0b74c1580eba33d905d693125ae21 and current Hub page; checked 2026-11-13

• Documentation and pinned source inspection only; no hands-on scenario was run.
• Other atomic questions remain unestablished: resources, region, expiry.

1. Paseo: public-docs/why.md

   Finding: The current pinned release documents automatic local daemon management, with the daemon owning running agents/workspaces and separate desktop/mobile/web/CLI clients. It explicitly supports running the environment on a server and continuing from other devices; client-laptop disconnect does not move execution off that operator daemon host.

   Locator

   Develop in one workspace; Continue from another device

   Retrieved

   2026-11-13

2. Paseo: public-docs/connectivity.md

   Finding: The pinned release explicitly supports a daemon on the user computer or server. Desktop and CLI attach through SSH to an already-running remote daemon, while mobile can use relay/Tailscale; this is an operator-owned execution host rather than a vendor compute service.

   Locator

   SSH setup and Tailscale daemon listen configuration

   Retrieved

   2026-11-13

Open-source license

Typed value: Yes. Apache-2.0.

Paseo v0.15.3 root code is Apache-2.0 with third-party licence exceptions; its desktop manifest also declares Apache-2.0. Hub self-hosting is documented, but the separate relay licence, all package licences and hosted-service parity were not audited.

• Client license: Root LICENSE is Apache-2.0 except third-party components; desktop 0.15.3 manifest also declares Apache-2.0.
• Server license: Root notice applies Apache-2.0 to Paseo repository code including the daemon, except incorporated third-party components. A per-package dependency audit was not performed.
• Source visibility: Public GitHub stable release and pinned licence/component files are available.
• Source revision: Stable v0.15.3 annotated tag peels to d91ae138cb931447635e94296023414a58bedcc5; licence and desktop manifest inspected at that commit.

Checked

2026-11-07 · checked 1 week ago

Cross-check

cross-checked 2026-11-07

Plan

Not specified in this finding

Surface

Paseo desktop; Paseo daemon and APIs; Paseo Hub; Paseo CLI and TypeScript SDK

Version

v0.15.3 at d91ae138cb931447635e94296023414a58bedcc5

• Root licence and desktop manifest checked; dependency and separate relay licence audit not performed.
• Hub documentation establishes self-hosting instructions, not hosted-service parity.
• No installation or authenticated service test.

1. Paseo licence at v0.15.3

   Finding: Root notice licenses Paseo under Apache-2.0 except incorporated third-party components, which retain their own licences. Read at pinned stable v0.15.3; no hosted-service parity inferred.

   Locator

   LICENSE opening notice and Apache-2.0 terms

   Retrieved

   2026-11-07

2. Paseo desktop manifest at v0.15.3

   Finding: The @getpaseo/desktop Electron wrapper manifest is version 0.15.3 and declares Apache-2.0; depends on Paseo CLI and server packages. This checks the distributed desktop component manifest, not every dependency licence.

   Locator

   name, version and license fields

   Retrieved

   2026-11-07

Any desktop app

Typed value: Yes.

Paseo offers desktop, native phone, browser and CLI clients for its daemon; the shared browser app includes compact phone layouts.

• Desktop os: Docs state the desktop app is available on macOS, Windows and Linux (Linux .deb, .rpm, AppImage); homepage download button targets Mac.
• Mobile apps: Native iOS (App Store) and Android (Google Play) apps are linked from the homepage; Android APK also on GitHub releases. Minimum OS versions not checked.
• Browser: Hosted web app at app.paseo.sh and a daemon-served web UI (off by default).
• Cli: npm i -g @getpaseo/cli installs the CLI and daemon; TypeScript SDK @getpaseo/client.
• Cross device continuity: Docs: the daemon owns running agents so mobile, web and CLI clients continue in the same environment. No transition test.

Checked

2026-11-07 · checked 1 week ago

Plan

Not specified in this finding

Surface

Paseo desktop; Paseo mobile; Paseo web; Paseo daemon and APIs; Paseo CLI and TypeScript SDK

Version

Paseo v0.15.4 at 1c00b365c9e0b74c1580eba33d905d693125ae21; inspected 2026-11-13

• Documentation and pinned source inspection only; no hands-on scenario was run.

1. Paseo homepage

   Finding: Current homepage presents desktop/mobile/web/CLI and SDK control of user-hosted agents, native Claude/Codex/OpenCode/Pi/OMP/Antigravity/Muse and additional ACP tools. App is free/open source, with optional E2E relay and user provider accounts.

   Locator

   Run it anywhere; providers; FAQ; sponsor section

   Retrieved

   2026-11-07

2. Paseo: Getting started

   Finding: Desktop app bundles its own daemon; Linux .deb/.rpm/AppImage; headless install via npm i -g @getpaseo/cli; Docker image; at least one provider CLI must be installed by the user; gh CLI recommended for PR-aware worktrees.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

3. Paseo: Why Paseo?

   Finding: Desktop app on macOS, Windows and Linux; daemon owns agents and workspaces; mobile, web and CLI clients connect to the same environment; runs agents with the user's own subscriptions, credentials, skills and MCP servers; Apache-2.0 with no telemetry, tracking or required Paseo account. The v0.15.3 tag text of this page is an earlier version; it says the daemon manages agents and clients connect locally or over a relay, and it also states no telemetry and Apache-2.0.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

Any phone client

Typed value: Yes.

Paseo offers desktop, native phone, browser and CLI clients for its daemon; the shared browser app includes compact phone layouts.

• Desktop os: Docs state the desktop app is available on macOS, Windows and Linux (Linux .deb, .rpm, AppImage); homepage download button targets Mac.
• Mobile apps: Native iOS (App Store) and Android (Google Play) apps are linked from the homepage; Android APK also on GitHub releases. Minimum OS versions not checked.
• Browser: Hosted web app at app.paseo.sh and a daemon-served web UI (off by default).
• Cross device continuity: Docs: the daemon owns running agents so mobile, web and CLI clients continue in the same environment. No transition test.

Checked

2026-11-07 · checked 1 week ago

Plan

Not specified in this finding

Surface

Paseo desktop; Paseo mobile; Paseo web; Paseo daemon and APIs; Paseo CLI and TypeScript SDK

Version

Paseo v0.15.4 at 1c00b365c9e0b74c1580eba33d905d693125ae21; inspected 2026-11-13

• Documentation and pinned source inspection only; no hands-on scenario was run.

1. Paseo homepage

   Finding: Current homepage presents desktop/mobile/web/CLI and SDK control of user-hosted agents, native Claude/Codex/OpenCode/Pi/OMP/Antigravity/Muse and additional ACP tools. App is free/open source, with optional E2E relay and user provider accounts.

   Locator

   Run it anywhere; providers; FAQ; sponsor section

   Retrieved

   2026-11-07

2. Paseo: Updates

   Finding: Stable and Beta channels; stable desktop rolls out gradually over 36 hours; app-store releases can lag desktop and CLI; no beta in app stores; Android APK on GitHub releases.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

paseo:ACC-01

Paseo offers desktop, native phone, browser and CLI clients for its daemon; the shared browser app includes compact phone layouts.

Checked

2026-11-07 · checked 1 week ago

Plan

Not specified in this finding

Surface

Paseo desktop; Paseo mobile; Paseo web; Paseo daemon and APIs; Paseo CLI and TypeScript SDK

Version

Paseo v0.15.4 at 1c00b365c9e0b74c1580eba33d905d693125ae21; inspected 2026-11-13

• Documentation and pinned source inspection only; no hands-on scenario was run.

1. Paseo homepage

   Finding: Current homepage presents desktop/mobile/web/CLI and SDK control of user-hosted agents, native Claude/Codex/OpenCode/Pi/OMP/Antigravity/Muse and additional ACP tools. App is free/open source, with optional E2E relay and user provider accounts.

   Locator

   Run it anywhere; providers; FAQ; sponsor section

   Retrieved

   2026-11-07

2. Paseo: CHANGELOG.md

   Finding: Current stable changelog starts 0.15.3, November 6, 2026, and describes stable changes since the older v0.11.1 source pass.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

   Source date

   2026-11-06

3. Paseo: Getting started

   Finding: Desktop app bundles its own daemon; Linux .deb/.rpm/AppImage; headless install via npm i -g @getpaseo/cli; Docker image; at least one provider CLI must be installed by the user; gh CLI recommended for PR-aware worktrees.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

4. Paseo: Why Paseo?

   Finding: Desktop app on macOS, Windows and Linux; daemon owns agents and workspaces; mobile, web and CLI clients connect to the same environment; runs agents with the user's own subscriptions, credentials, skills and MCP servers; Apache-2.0 with no telemetry, tracking or required Paseo account. The v0.15.3 tag text of this page is an earlier version; it says the daemon manages agents and clients connect locally or over a relay, and it also states no telemetry and Apache-2.0.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

5. Paseo: CLI reference

   Finding: CLI covers run/ls/attach/send/logs/wait/stop, projects, workspaces, terminals, scripts, plugins, schedules, permissions (paseo permit ls/allow/deny), agent modes and detach, daemon management, Hub commands, remote --host (including ssh://) and JSON/YAML output.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

6. Paseo: TypeScript SDK

   Finding: @getpaseo/client drives a daemon from a program: create agents with provider/model, cwd and prompt, wait for finish, send follow-ups; agents created through the SDK appear in the Paseo app and persist after the program exits.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

7. Paseo: Related projects

   Finding: Lists community-built projects (not first-party): a VS Code extension, a VS Code Web plugin, a macOS menu-bar status app, cross-daemon comms, Docker packaging, GCP devbox provisioning, and the paseo.cafe plugin directory; states they are not endorsed.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

8. Paseo: Updates

   Finding: Stable and Beta channels; stable desktop rolls out gradually over 36 hours; app-store releases can lag desktop and CLI; no beta in app stores; Android APK on GitHub releases.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

9. Paseo: Self-hosting the web UI

   Finding: Daemon can serve the full browser UI from its own address (off by default, features.webUi.enabled); password and TLS reverse proxy guidance.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

10. public-docs/why.md, line 23

    Finding: Current stable why.md describes desktop Mac/Windows/Linux, daemon-owned sessions, native mobile/files/terminals/diffs, optional E2E relay, Apache-2.0 and no required account/telemetry/tracking as vendor claims.

    Locator

    Current stable v0.15.3 file; named headings and operations

    Retrieved

    2026-11-07

11. public-docs/why.md, lines 35 and 43

    Finding: Current stable why.md now includes the earlier main-only mobile/telemetry wording. It is release documentation, not a packet capture.

    Locator

    Current stable v0.15.3 file; named headings and operations

    Retrieved

    2026-11-07

12. Paseo v0.11.1 Claude Code terminal access

    Finding: The release-tag documentation describes terminal use from desktop, web or mobile while retaining workspace and Git-change access. This is a documented route, not a tested parity claim.

    Locator

    Current stable v0.15.3 file; named headings and operations

    Retrieved

    2026-11-07

13. Paseo: packages/app/src/composer/dock/internal/fullscreen.tsx

    Finding: The shipped browser app explicitly handles the mobile browser visual viewport and uses compact mobile panel routing in the shared app layout. The daemon-served browser UI connects to the same agents. This establishes phone-browser access without claiming tested feature parity.

    Locator

    Mobile browser visible viewport; packages/app/src/app/_layout.tsx compact/mobile panel routing; public-docs/web-ui.md

    Retrieved

    2026-11-13

paseo:ACC-02

Current stable and homepage document native Claude Code, Codex, OpenCode, Pi, OMP, Antigravity and Muse plus a version-pinned ACP catalog and custom providers. Provider-specific MCP and permission limits remain separate. Paseo v0.15.4 registers a native Antigravity provider with the agy command, host-side availability checks and a session connection implementation.

Checked

2026-11-07 · checked 1 week ago

Cross-check

cross-checked 2026-11-10

Plan

Not specified in this finding

Surface

Paseo daemon and APIs; Paseo desktop; Paseo CLI and TypeScript SDK

Version

Paseo v0.15.3 at d91ae138cb931447635e94296023414a58bedcc5; hosted Hub page reread 2026-11-07 Antigravity source pass: v0.15.4 (1c00b365c9e0b74c1580eba33d905d693125ae21).

• No mixed-provider execution test; installed tool credentials/model access are separate.
• Antigravity has Full access only and no Paseo tools or steering in the documented adapter.
• Antigravity requires agy on the host and its own sign-in. The documented adapter has Full access only and no Paseo tools or steering.

1. Paseo homepage

   Finding: Current homepage presents desktop/mobile/web/CLI and SDK control of user-hosted agents, native Claude/Codex/OpenCode/Pi/OMP/Antigravity/Muse and additional ACP tools. App is free/open source, with optional E2E relay and user provider accounts.

   Locator

   Run it anywhere; providers; FAQ; sponsor section

   Retrieved

   2026-11-07

2. Paseo: CHANGELOG.md

   Finding: Current stable changelog starts 0.15.3, November 6, 2026, and describes stable changes since the older v0.11.1 source pass.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

   Source date

   2026-11-06

3. Paseo: public-docs/orchestration.md

   Finding: Agents can launch other agents across providers and models, prompt them by ID, check progress, cancel, create workspaces/worktrees, use the CLI against remote hosts, create schedules and heartbeats. Paseo tool injection is off by default; workers appear in a Subagents track and completion notifies the parent.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

4. Paseo: public-docs/orchestration-workflows.md

   Finding: Recipes: fan-out research (workers share files), parallel edits in separate worktrees, implement-then-review, prompt another agent by ID, redirect/cancel a worker, remote-host CLI, heartbeats. Distinguishes interactive Paseo subagents from read-only native provider subagent timelines.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

5. Paseo: Supported providers

   Finding: Current stable guide covers native Claude Code, Codex, OpenCode, Pi, OMP, Antigravity and Muse plus ACP/custom routes; provider-specific permission, MCP and steering limits are explicit.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

6. Paseo: Plugins

   Finding: Plugins add screens, sidebar items, panels, commands, themes, attachment sources, daemon RPCs and providers; client contributions run on every connected client including mobile; registry install via paseo plugin add owner/slug.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

7. Paseo: Custom providers

   Finding: agents.providers in config.json can extend providers to other API endpoints, add profiles, override binaries, add ACP agents or disable providers.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

8. Native support (6 entries); ACP catalog (36 entries)

   Finding: Current stable guide names native providers and a version-pinned in-app ACP catalog plus custom providers. Antigravity has Full access only and no Paseo tools or steering; no exact stale catalog count repeated.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

9. Paseo homepage FAQ and integrations list

   Finding: Current homepage lists native Claude, Codex, OpenCode, Pi, OMP, Antigravity and Muse plus ACP; no exact catalog count inferred.

   Locator

   Works with your tools list; FAQ native implementations

   Retrieved

   2026-11-07

10. Paseo v0.15.3: public-docs/supported-providers.md

    Finding: The shipped ACP catalog explicitly lists Cursor, Gemini CLI and Grok; underlying CLIs must be installed and authenticated. No Aider listing was established.

    Locator

    Native support and ACP catalog

    Retrieved

    2026-11-07

11. Paseo Antigravity support at v0.15.4

    Finding: Paseo v0.15.4 registers a native Antigravity provider with the agy command, host-side availability checks and a session connection implementation.

    Locator

    plugins/antigravity-provider/server/provider.ts lines 16-53, v0.15.4, commit 1c00b365c9e0b74c1580eba33d905d693125ae21

    Retrieved

    2026-11-10

    Source date

    2026-11-10

paseo:ACC-03

Paseo reuses each provider CLI's own login for Claude plan, ChatGPT plan and API-key use, and adds no charge for Claude Code or Codex. Optional custom-provider and speech credentials can be written to Paseo config.

Checked

2026-11-07 · checked 1 week ago

Cross-check

cross-checked 2026-11-07

Plan

Not specified in this finding

Surface

Paseo daemon and APIs; Paseo desktop

Version

Paseo v0.15.3 at d91ae138cb931447635e94296023414a58bedcc5; hosted Hub page reread 2026-11-07

• Credentials for the normal login path stay in the provider CLI. Multiple accounts are supported per provider: profiles bind different credentials per provider entry (custom-providers docs, Multiple profiles), and agents respect custom CLAUDE_CONFIG_DIR and CODEX_HOME homes (changelog, PR #5465). The exact user action for switching between accounts is not documented. Vendor-side restrictions are not documented by Paseo.
• Claude plan requirement and limits are Anthropic's, per Paseo's own docs.

1. Paseo: CHANGELOG.md

   Finding: Current stable changelog starts 0.15.3, November 6, 2026, and describes stable changes since the older v0.11.1 source pass.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

   Source date

   2026-11-06

2. Paseo: Getting started

   Finding: Desktop app bundles its own daemon; Linux .deb/.rpm/AppImage; headless install via npm i -g @getpaseo/cli; Docker image; at least one provider CLI must be installed by the user; gh CLI recommended for PR-aware worktrees.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

3. Paseo: Why Paseo?

   Finding: Desktop app on macOS, Windows and Linux; daemon owns agents and workspaces; mobile, web and CLI clients connect to the same environment; runs agents with the user's own subscriptions, credentials, skills and MCP servers; Apache-2.0 with no telemetry, tracking or required Paseo account. The v0.15.3 tag text of this page is an earlier version; it says the daemon manages agents and clients connect locally or over a relay, and it also states no telemetry and Apache-2.0.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

4. Paseo: Security

   Finding: Daemon on user hardware; relay is E2E encrypted (Curve25519/NaCl box) and off by default; optional bcrypt-hashed password for direct connections; DNS-rebinding host allowlist; Paseo never stores or transmits provider API keys; agents run in the user's context; Docker image runs as non-root but mounts are the boundary; Hub identities are separate from daemon identities.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

5. Paseo: Claude Code provider

   Finding: Runs the official claude CLI via the Claude Agent SDK; usage counts against the user's normal Claude plan limits with no separate Agent SDK credit pool; a Claude plan including Claude Code is required.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

6. Paseo: Codex provider

   Finding: No Paseo charge for Codex; sign in with ChatGPT (plan access) or an OpenAI API key.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

7. Paseo: Custom providers

   Finding: agents.providers in config.json can extend providers to other API endpoints, add profiles, override binaries, add ACP agents or disable providers.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

8. env examples lines 56, 129 and 134; Multiple profiles line 118

   Finding: example config sets ANTHROPIC_API_KEY in provider env entries (lines 56, 129, 134); profiles bind different credentials per provider entry (Multiple profiles, line 118).

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

9. providers.openai.stt and tts apiKey examples, lines 94 and 98

   Finding: providers.openai.stt and providers.openai.tts take apiKey values in the example config (lines 94 and 98); environment variables OPENAI_STT_API_KEY and OPENAI_TTS_API_KEY are listed (lines 118 and 119).

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

paseo:ACC-04

Paseo works in any directory on a daemon host, with or without git; worktree features and PR workspaces need a git checkout, and gh is recommended.

Checked

2026-10-09 · checked 1 month ago

Cross-check

cross-checked 2026-10-09

Plan

Not specified in this finding

Surface

Paseo desktop; Paseo daemon and APIs

Version

v0.11.1 release (tag ab10a6694); sources read at main d0bc188a5 (eight later commits)

• Onboarding steps are documented, not tested. Managed cloud setup is not established: the docs describe user-supplied machines and Hub dispatch to them.

1. Paseo: CHANGELOG.md

   Finding: Re-read 2026-10-09 at pinned CHANGELOG.md (d0bc188, identical to main). The file is unchanged between the v0.11.1 tag and d0bc188; its top entry is 0.11.1 (2026-10-07) and there is no Unreleased heading. Earlier finding: 0.11.0 adds the plugin registry, Muse Code and Antigravity providers, a Usage view of subscription quota windows, and OMP mid-turn steering; 0.11.1 adds Claude Haiku 5.5 support and fixes subagent status and Claude history after daemon restart. Earlier entries mention push notifications, GitLab/Gitea/Forgejo/Codeberg PR support and PR check summaries.

   Locator

   0.11.1 and 0.11.0 sections

   Retrieved

   2026-10-09

   Source date

   2026-10-07

2. Paseo: Getting started

   Finding: Desktop app bundles its own daemon; Linux .deb/.rpm/AppImage; headless install via npm i -g @getpaseo/cli; Docker image; at least one provider CLI must be installed by the user; gh CLI recommended for PR-aware worktrees.

   Locator

   public-docs/index.md

   Retrieved

   2026-10-08

3. Paseo: Why Paseo?

   Finding: Re-read 2026-10-09 at pinned d0bc188 (unchanged for the cited statements): Desktop app on macOS, Windows and Linux; daemon owns agents and workspaces; mobile, web and CLI clients connect to the same environment; runs agents with the user's own subscriptions, credentials, skills and MCP servers; Apache-2.0 with no telemetry, tracking or required Paseo account. The v0.11.1 tag text of this page is an earlier version; it says the daemon manages agents and clients connect locally or over a relay, and it also states no telemetry and Apache-2.0.

   Locator

   public-docs/why.md

   Retrieved

   2026-10-09

4. Paseo: Workspaces

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Project, workspace and session model; workspace isolation is Local (existing directory, shared files) or Worktree (managed git worktree and branch); workspaces can be created without an agent; any directory on a daemon host can be a project.

   Locator

   public-docs/workspaces.md

   Retrieved

   2026-10-09

5. Paseo: Git worktrees

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Worktrees under $PASEO_HOME/worktrees; branch-off, checkout-branch and checkout-pr modes; paseo.json setup/teardown hooks, scripts, supervised services with per-worktree ports, port ranges or external allocator, reverse proxy hostnames, auto-opened terminals.

   Locator

   public-docs/worktrees.md

   Retrieved

   2026-10-09

6. Paseo: Connectivity

   Finding: Client-to-daemon transports: SSH (desktop and CLI, daemon must already run), optional end-to-end encrypted relay (disabled until enabled), Tailscale/direct TCP with optional password.

   Locator

   public-docs/connectivity.md

   Retrieved

   2026-10-08

7. Paseo: Docker

   Finding: Official image ghcr.io/getpaseo/paseo runs the daemon and bundled web UI as non-root user; does not bundle agent CLIs; PASEO_PASSWORD recommended before publishing the port; state under /home/paseo.

   Locator

   public-docs/docker.md

   Retrieved

   2026-10-08

8. Paseo: Troubleshooting

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Desktop and daemon log locations (daemon.log under PASEO_HOME, main.log per OS); restarting the daemon keeps running agents and clients reconnect automatically; login-shell PATH resolution on macOS/Linux only.

   Locator

   public-docs/troubleshooting.md

   Retrieved

   2026-10-09

paseo:ACC-05

Paseo exposes a CLI, TypeScript SDK, daemon MCP tools and a Hub HTTP API with scoped keys and OpenAPI; daemon access is password-, pairing- or permission-based.

Checked

2026-10-09 · checked 1 month ago

Cross-check

cross-checked 2026-10-09

Plan

Not specified in this finding

Surface

Paseo daemon and APIs; Paseo CLI and TypeScript SDK; Paseo Hub

Version

v0.11.1 release (tag ab10a6694); sources read at main d0bc188a5 (eight later commits)

• MCP tool injection is off by default; stability or versioning guarantees were not found; Hub API only covers triggers, projects and daemons.

1. Paseo: public-docs/orchestration.md

   Finding: Agents can launch other agents across providers and models, prompt them by ID, check progress, cancel, create workspaces/worktrees, use the CLI against remote hosts, create schedules and heartbeats. Paseo tool injection is off by default; workers appear in a Subagents track and completion notifies the parent.

   Locator

   public-docs/orchestration.md

   Retrieved

   2026-10-08

2. Paseo: Security

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Daemon on user hardware; relay is E2E encrypted (Curve25519/NaCl box) and off by default; optional bcrypt-hashed password for direct connections; DNS-rebinding host allowlist; Paseo never stores or transmits provider API keys; agents run in the user's context; Docker image runs as non-root but mounts are the boundary; Hub identities are separate from daemon identities.

   Locator

   public-docs/security.md

   Retrieved

   2026-10-09

3. Paseo: MCP reference

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Paseo MCP server on the daemon (enabled by default; injection into agents off by default) exposing agent, workspace, workspace-script, terminal, schedule/heartbeat, profile, provider, permission, browser and voice tools; per-provider tool allow/deny policy, explicitly not a security boundary.

   Locator

   public-docs/mcp.md

   Retrieved

   2026-10-09

4. Paseo: CLI reference

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): CLI covers run/ls/attach/send/logs/wait/stop, projects, workspaces, terminals, scripts, plugins, schedules, permissions (paseo permit ls/allow/deny), agent modes and detach, daemon management, Hub commands, remote --host (including ssh://) and JSON/YAML output.

   Locator

   public-docs/cli.md

   Retrieved

   2026-10-09

5. Paseo: TypeScript SDK

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): @getpaseo/client drives a daemon from a program: create agents with provider/model, cwd and prompt, wait for finish, send follow-ups; agents created through the SDK appear in the Paseo app and persist after the program exits.

   Locator

   public-docs/sdk/index.md

   Retrieved

   2026-10-09

6. Paseo: Hub overview

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Hub registers daemons and starts agents from GitHub, Slack and Discord activity; triggers as code in .paseo/; records every accepted event and what ran; team visibility; self-hostable; hosted Free plan needs no card and does not expire.

   Locator

   public-docs/hub/index.md

   Retrieved

   2026-10-09

7. Paseo: How Hub works

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Connections, daemons, projects, environments, triggers, workflows and steps; triggers require a non-empty from_users allowlist; configuration revisions validated on sync with previous revision kept on failure; Hub does not sandbox agents.

   Locator

   public-docs/hub/concepts.md

   Retrieved

   2026-10-09

8. Paseo: Hub public API

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Hub API with OpenAPI 3.1 document; organization-scoped API keys with selectable scopes (projects:read, configuration:validate/install, runs:dispatch, daemons:enroll); keys do not grant dashboard access; API operations retain key attribution in audit evidence.

   Locator

   public-docs/hub/api.md

   Retrieved

   2026-10-09

9. Paseo: Daemon permissions

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Daemon authorizes principals via semantic permissions (daemon.read/manage, tunnel.manage, access.manage, workspace.read/write/manage, automation.manage, hub.execute); pairing invitations create principals and credentials with issuer-selected permissions.

   Locator

   docs/permissions.md

   Retrieved

   2026-10-09

paseo:ACC-06

Paseo documents a plugin system and passes through the provider CLI's own MCP servers and skills; it does not document a Paseo-level MCP client registry.

Checked

2026-10-09 · checked 1 month ago

Cross-check

cross-checked 2026-11-07

Plan

Not specified in this finding

Surface

Paseo daemon and APIs

Version

v0.11.1 release (tag ab10a6694); sources read at main d0bc188a5 (eight later commits)

• MCP client behavior is largely each provider's; permission scope of plugins beyond the trusted-local model was not documented.

1. Paseo: CHANGELOG.md

   Finding: Re-read 2026-10-09 at pinned CHANGELOG.md (d0bc188, identical to main). The file is unchanged between the v0.11.1 tag and d0bc188; its top entry is 0.11.1 (2026-10-07) and there is no Unreleased heading. Earlier finding: 0.11.0 adds the plugin registry, Muse Code and Antigravity providers, a Usage view of subscription quota windows, and OMP mid-turn steering; 0.11.1 adds Claude Haiku 5.5 support and fixes subagent status and Claude history after daemon restart. Earlier entries mention push notifications, GitLab/Gitea/Forgejo/Codeberg PR support and PR check summaries.

   Locator

   0.11.1 and 0.11.0 sections

   Retrieved

   2026-10-09

   Source date

   2026-10-07

2. Paseo: Why Paseo?

   Finding: Re-read 2026-10-09 at pinned d0bc188 (unchanged for the cited statements): Desktop app on macOS, Windows and Linux; daemon owns agents and workspaces; mobile, web and CLI clients connect to the same environment; runs agents with the user's own subscriptions, credentials, skills and MCP servers; Apache-2.0 with no telemetry, tracking or required Paseo account. The v0.11.1 tag text of this page is an earlier version; it says the daemon manages agents and clients connect locally or over a relay, and it also states no telemetry and Apache-2.0.

   Locator

   public-docs/why.md

   Retrieved

   2026-10-09

3. Paseo: Plugins

   Finding: Plugins add screens, sidebar items, panels, commands, themes, attachment sources, daemon RPCs and providers; client contributions run on every connected client including mobile; registry install via paseo plugin add owner/slug.

   Locator

   public-docs/plugins/index.md

   Retrieved

   2026-10-08

4. Paseo: Orchestration skills

   Finding: Installable /paseo, /paseo-handoff, /paseo-committee and /paseo-advisor skills for delegation, handoff and second opinions.

   Locator

   public-docs/skills.md

   Retrieved

   2026-10-08

5. Paseo: Supported providers

   Finding: Current stable guide covers native Claude Code, Codex, OpenCode, Pi, OMP, Antigravity and Muse plus ACP/custom routes; provider-specific permission, MCP and steering limits are explicit.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

6. env examples lines 56, 129 and 134; Multiple profiles line 118

   Finding: example config sets ANTHROPIC_API_KEY in provider env entries (lines 56, 129, 134); profiles bind different credentials per provider entry (Multiple profiles, line 118).

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

7. Paseo v0.15.3: public-docs/plugins/reference.md

   Finding: Plugins execute trusted local TypeScript on a daemon, inherit host authority, can use private-registry credentials; plugin log tails are bounded to 500 entries and 256 KiB in memory, 16 KiB per line.

   Locator

   Trust model; plugin sources; backend logging

   Retrieved

   2026-11-07

paseo:ACC-07

Paseo desktop is an Electron app; the mobile and web clients share an Expo / React Native app package.

Checked

2026-10-09 · checked 1 month ago

Cross-check

cross-checked 2026-10-09

Plan

Not specified in this finding

Surface

Paseo desktop; Paseo mobile; Paseo web

Version

v0.11.1 release (tag ab10a6694); sources read at main d0bc188a5 (eight later commits)

• Package manifests establish the frameworks, not their behavior; whether web, mobile and desktop share all screens was not verified.

1. Paseo homepage

   Finding: Re-read 2026-10-09 (live homepage): Download for Mac links to the v0.11.1 arm64 DMG; iOS App Store and Google Play listings; app.paseo.sh web app; headless daemon; CLI and TypeScript SDK; providers Claude Code, Codex, OpenCode, Pi, OMP, Cursor, Muse Code, Antigravity and about 33 more through ACP; Apache 2.0 and free and open source; no telemetry, tracking or forced login; optional end-to-end encrypted relay; Hub named for teams and triggers. The maintainer is described as one full-time person with no investors; the project is funded by sponsorship and Hub. No roadmap or coming-soon wording found.

   Locator

   Run it anywhere; providers; FAQ; sponsor section

   Retrieved

   2026-10-09

2. Paseo: packages/desktop/package.json

   Finding: Desktop package declares Electron 44.2.0 in devDependencies and an Apache-2.0 license, and depends on @getpaseo/server.

   Locator

   devDependencies.electron and license

   Retrieved

   2026-10-08

3. Paseo: packages/app/package.json

   Finding: App package declares Expo ^54.0.18, React Native 0.81.5, react-native-web ~0.21.0 and react-dom 19.1.0, with a build:web script that runs expo export --platform web; one package therefore serves the mobile and web clients.

   Locator

   dependencies.expo, dependencies.react-native, dependencies.react-native-web, dependencies.react-dom and scripts.build:web

   Retrieved

   2026-10-08

4. Paseo: Plugins

   Finding: Plugins add screens, sidebar items, panels, commands, themes, attachment sources, daemon RPCs and providers; client contributions run on every connected client including mobile; registry install via paseo plugin add owner/slug.

   Locator

   public-docs/plugins/index.md

   Retrieved

   2026-10-08

paseo:PLAN-01

Paseo is workspace- and session-based and is not documented as having a native task-tracker intake; agents start from prompts in the app, CLI, SDK, schedules and MCP, and from Hub triggers on GitHub, Slack and Discord events.

Checked

2026-10-09 · checked 1 month ago

Cross-check

cross-checked 2026-10-09

Plan

Not specified in this finding

Surface

Paseo Hub; Paseo daemon and APIs

Version

v0.11.1 release (tag ab10a6694); sources read at main d0bc188a5 (eight later commits)

• Issue import or tracker sync is not established. Hub docs describe event-to-run dispatch.

1. Paseo: Workspaces

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Project, workspace and session model; workspace isolation is Local (existing directory, shared files) or Worktree (managed git worktree and branch); workspaces can be created without an agent; any directory on a daemon host can be a project.

   Locator

   public-docs/workspaces.md

   Retrieved

   2026-10-09

2. Paseo: CLI reference

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): CLI covers run/ls/attach/send/logs/wait/stop, projects, workspaces, terminals, scripts, plugins, schedules, permissions (paseo permit ls/allow/deny), agent modes and detach, daemon management, Hub commands, remote --host (including ssh://) and JSON/YAML output.

   Locator

   public-docs/cli.md

   Retrieved

   2026-10-09

3. Paseo: TypeScript SDK

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): @getpaseo/client drives a daemon from a program: create agents with provider/model, cwd and prompt, wait for finish, send follow-ups; agents created through the SDK appear in the Paseo app and persist after the program exits.

   Locator

   public-docs/sdk/index.md

   Retrieved

   2026-10-09

4. Paseo: Hub overview

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Hub registers daemons and starts agents from GitHub, Slack and Discord activity; triggers as code in .paseo/; records every accepted event and what ran; team visibility; self-hostable; hosted Free plan needs no card and does not expire.

   Locator

   public-docs/hub/index.md

   Retrieved

   2026-10-09

5. Paseo: How Hub works

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Connections, daemons, projects, environments, triggers, workflows and steps; triggers require a non-empty from_users allowlist; configuration revisions validated on sync with previous revision kept on failure; Hub does not sandbox agents.

   Locator

   public-docs/hub/concepts.md

   Retrieved

   2026-10-09

paseo:PLAN-02

Paseo documents plan mode as a session mode and persists agent timelines; a durable task plan or acceptance-criteria object is not established by its documentation.

Checked

2026-10-09 · checked 1 month ago

Cross-check

cross-checked 2026-10-09

Plan

Not specified in this finding

Surface

Paseo daemon and APIs; Paseo CLI and TypeScript SDK

Version

v0.11.1 release (tag ab10a6694); sources read at main d0bc188a5 (eight later commits)

• Plan mode is a provider/session setting; no plan document store was found.

1. Paseo: CLI reference

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): CLI covers run/ls/attach/send/logs/wait/stop, projects, workspaces, terminals, scripts, plugins, schedules, permissions (paseo permit ls/allow/deny), agent modes and detach, daemon management, Hub commands, remote --host (including ssh://) and JSON/YAML output.

   Locator

   public-docs/cli.md

   Retrieved

   2026-10-09

2. Paseo: Agent lifecycle

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Agent states initializing/idle/running/error/closed; closed agents keep identity, timeline and persistence handle and resume under the same ID; a runtime that dies between turns can leave an idle-looking agent until reported; cancellation and permission notifications to parent agents.

   Locator

   docs/agent-lifecycle.md

   Retrieved

   2026-10-09

paseo:PLAN-03

Paseo models parentage between agents (subagents, detach) and workspaces; epics, blockers and readiness states are not established by its documentation.

Checked

2026-10-09 · checked 1 month ago

Cross-check

cross-checked 2026-11-10

Plan

Not specified in this finding

Surface

Paseo daemon and APIs; Paseo Hub

Version

v0.11.1 release (tag ab10a6694) docs at d0bc188a5; Hub workflows doc at v0.15.3 (d91ae138cb931447635e94296023414a58bedcc5)

• Parentage is agent-to-agent, not a task hierarchy with dependencies.

1. Paseo: public-docs/orchestration-workflows.md

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Recipes: fan-out research (workers share files), parallel edits in separate worktrees, implement-then-review, prompt another agent by ID, redirect/cancel a worker, remote-host CLI, heartbeats. Distinguishes interactive Paseo subagents from read-only native provider subagent timelines.

   Locator

   public-docs/orchestration-workflows.md

   Retrieved

   2026-10-09

2. Paseo: Agent lifecycle

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Agent states initializing/idle/running/error/closed; closed agents keep identity, timeline and persistence handle and resume under the same ID; a runtime that dies between turns can leave an idle-looking agent until reported; cancellation and permission notifications to parent agents.

   Locator

   docs/agent-lifecycle.md

   Retrieved

   2026-10-09

3. Paseo: public-docs/orchestration.md

   Finding: Agents can launch other agents across providers and models, prompt them by ID, check progress, cancel, create workspaces/worktrees, use the CLI against remote hosts, create schedules and heartbeats. Paseo tool injection is off by default; workers appear in a Subagents track and completion notifies the parent.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

4. Paseo v0.15.3: public-docs/hub/workflows.md

   Finding: Hub workflows run ordered steps with unique IDs, prior-step structured outputs, finite classifier-selected environments/agents, conditional skipping, and workflow/step idle/runtime limits. Timeouts fail the run and stop later steps.

   Locator

   Conditions and ordered output; Deadlines; Choose an agent

   Retrieved

   2026-11-07

paseo:PLAN-04

Paseo relies on each provider CLI's instructions, skills and memory; it adds installable orchestration skills and agent profiles. Shared project memory of its own is not established by its documentation.

Checked

2026-10-09 · checked 1 month ago

Cross-check

cross-checked 2026-10-09

Plan

Not specified in this finding

Surface

Paseo daemon and APIs

Version

v0.11.1 release (tag ab10a6694); sources read at main d0bc188a5 (eight later commits)

• Memory scope, provenance and deletion semantics belong to the underlying provider CLI.

1. Paseo: Why Paseo?

   Finding: Re-read 2026-10-09 at pinned d0bc188 (unchanged for the cited statements): Desktop app on macOS, Windows and Linux; daemon owns agents and workspaces; mobile, web and CLI clients connect to the same environment; runs agents with the user's own subscriptions, credentials, skills and MCP servers; Apache-2.0 with no telemetry, tracking or required Paseo account. The v0.11.1 tag text of this page is an earlier version; it says the daemon manages agents and clients connect locally or over a relay, and it also states no telemetry and Apache-2.0.

   Locator

   public-docs/why.md

   Retrieved

   2026-10-09

2. Paseo: Agent profiles

   Finding: Named profiles store provider, model, mode, thinking level and features with When-to-use notes that orchestrating agents read via list_profiles.

   Locator

   public-docs/agent-profiles.md

   Retrieved

   2026-10-08

3. Paseo: Orchestration skills

   Finding: Installable /paseo, /paseo-handoff, /paseo-committee and /paseo-advisor skills for delegation, handoff and second opinions.

   Locator

   public-docs/skills.md

   Retrieved

   2026-10-08

paseo:PLAN-05

Paseo documents file browsing, a built-in browser and screenshot tools; code search, indexing and retrieval are not established by its documentation.

Checked

2026-10-09 · checked 1 month ago

Cross-check

cross-checked 2026-10-09

Plan

Not specified in this finding

Surface

Paseo desktop; Paseo daemon and APIs

Version

v0.11.1 release (tag ab10a6694); sources read at main d0bc188a5 (eight later commits)

• Code search quality, indexing and citations are provider behavior.

1. Paseo: Supported providers

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Native: Claude Code, Codex, OpenCode, Pi, Antigravity (agy CLI, Full access only, no Paseo MCP tools or steering), Muse Code. ACP catalog lists about 35 more agents (for example Cursor, Gemini CLI, GitHub Copilot, Junie, Amp, Cline, goose); anything else can be added manually.

   Locator

   public-docs/supported-providers.md

   Retrieved

   2026-10-09

2. Paseo: CLI reference

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): CLI covers run/ls/attach/send/logs/wait/stop, projects, workspaces, terminals, scripts, plugins, schedules, permissions (paseo permit ls/allow/deny), agent modes and detach, daemon management, Hub commands, remote --host (including ssh://) and JSON/YAML output.

   Locator

   public-docs/cli.md

   Retrieved

   2026-10-09

3. Paseo: Run parallel tasks

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Desktop walkthrough: separate worktree workspaces run agents concurrently, Changes tab for diffs, Files, terminals and built-in browser tabs; commit and PR via the user's usual git workflow or the agent; processes still share machine ports.

   Locator

   public-docs/parallel-development.md

   Retrieved

   2026-10-09

paseo:PLAN-06

The inspected release exposes agent workspaces and provider task displays, but no native issue tracker. The FileTaskStore utility is not connected to an accessible product action.

Checked

2026-11-13 · checked 2 days ago

Plan

Not specified in this finding

Surface

Paseo desktop; Paseo mobile; Paseo web; Paseo daemon and APIs; Paseo Hub; Paseo CLI and TypeScript SDK

Version

Paseo v0.15.4 and public Hub commit 61e51c56f8756e40c55a30982160ce000f2aa177; inspected 2026-11-13

• Documentation and pinned source inspection only; no hands-on scenario was run.
• Other atomic questions remain unestablished: edit, discuss, prioritize, label, assign, search, filter, archive, reopen, project_epic_views, idea_parking, explicit_dispatch, metadata, external_tracker_requirement.

1. Paseo: packages/server/src/tasks/task-store.ts

   Finding: The source contains a standalone FileTaskStore library with task states, but it is not imported into a shipped daemon route, app action or CLI command. Inspection of the app, daemon, CLI and public Hub routes/schema found provider task displays, agent workspaces and execution runs rather than an accessible product-owned issue tracker. External GitHub and Linear issues remain external.

   Locator

   FileTaskStore; types.ts; references across packages/server, packages/cli and packages/app; Hub routes and schema

   Retrieved

   2026-11-13

paseo:COORD-01

Paseo runs multiple agents and workspaces concurrently, each in its own worktree if wanted; documented recipes cover parallel research and parallel edits.

Checked

2026-10-09 · checked 1 month ago

Cross-check

cross-checked 2026-10-09

Plan

Not specified in this finding

Surface

Paseo desktop; Paseo daemon and APIs; Paseo CLI and TypeScript SDK

Version

v0.11.1 release (tag ab10a6694); sources read at main d0bc188a5 (eight later commits)

• No concurrency quota or observed concurrency measurement documented; research workers in one workspace share files.

1. Paseo: CHANGELOG.md

   Finding: Re-read 2026-10-09 at pinned CHANGELOG.md (d0bc188, identical to main). The file is unchanged between the v0.11.1 tag and d0bc188; its top entry is 0.11.1 (2026-10-07) and there is no Unreleased heading. Earlier finding: 0.11.0 adds the plugin registry, Muse Code and Antigravity providers, a Usage view of subscription quota windows, and OMP mid-turn steering; 0.11.1 adds Claude Haiku 5.5 support and fixes subagent status and Claude history after daemon restart. Earlier entries mention push notifications, GitLab/Gitea/Forgejo/Codeberg PR support and PR check summaries.

   Locator

   0.11.1 and 0.11.0 sections

   Retrieved

   2026-10-09

   Source date

   2026-10-07

2. Paseo: public-docs/orchestration-workflows.md

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Recipes: fan-out research (workers share files), parallel edits in separate worktrees, implement-then-review, prompt another agent by ID, redirect/cancel a worker, remote-host CLI, heartbeats. Distinguishes interactive Paseo subagents from read-only native provider subagent timelines.

   Locator

   public-docs/orchestration-workflows.md

   Retrieved

   2026-10-09

3. Paseo: Workspaces

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Project, workspace and session model; workspace isolation is Local (existing directory, shared files) or Worktree (managed git worktree and branch); workspaces can be created without an agent; any directory on a daemon host can be a project.

   Locator

   public-docs/workspaces.md

   Retrieved

   2026-10-09

4. Paseo: CLI reference

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): CLI covers run/ls/attach/send/logs/wait/stop, projects, workspaces, terminals, scripts, plugins, schedules, permissions (paseo permit ls/allow/deny), agent modes and detach, daemon management, Hub commands, remote --host (including ssh://) and JSON/YAML output.

   Locator

   public-docs/cli.md

   Retrieved

   2026-10-09

5. Paseo: Run parallel tasks

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Desktop walkthrough: separate worktree workspaces run agents concurrently, Changes tab for diffs, Files, terminals and built-in browser tabs; commit and PR via the user's usual git workflow or the agent; processes still share machine ports.

   Locator

   public-docs/parallel-development.md

   Retrieved

   2026-10-09

paseo:COORD-02

Paseo documents agent parentage and per-agent addressing; human assignment, agent claims and queue routing are not established by its documentation.

Checked

2026-10-09 · checked 1 month ago

Cross-check

cross-checked 2026-10-09

Plan

Not specified in this finding

Surface

Paseo daemon and APIs

Version

v0.11.1 release (tag ab10a6694); sources read at main d0bc188a5 (eight later commits)

• Hub routes events by trigger filters to a named daemon, not by ownership.

1. Paseo: How Hub works

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Connections, daemons, projects, environments, triggers, workflows and steps; triggers require a non-empty from_users allowlist; configuration revisions validated on sync with previous revision kept on failure; Hub does not sandbox agents.

   Locator

   public-docs/hub/concepts.md

   Retrieved

   2026-10-09

2. Paseo: Agent profiles

   Finding: Named profiles store provider, model, mode, thinking level and features with When-to-use notes that orchestrating agents read via list_profiles.

   Locator

   public-docs/agent-profiles.md

   Retrieved

   2026-10-08

paseo:COORD-03

Agents can launch, prompt, inspect and cancel other agents of any provider; workers are retained as inspectable subagent sessions with notifications back to the parent.

Checked

2026-10-09 · checked 1 month ago

Cross-check

cross-checked 2026-10-09

Plan

Not specified in this finding

Surface

Paseo desktop; Paseo daemon and APIs; Paseo CLI and TypeScript SDK

Version

v0.11.1 release (tag ab10a6694); sources read at main d0bc188a5 (eight later commits)

• Paseo tool injection is off by default; Antigravity lacks Paseo tools; native provider subagents are read-only timelines.
• No hands-on delegation scenario run.

1. Paseo: public-docs/orchestration.md

   Finding: Agents can launch other agents across providers and models, prompt them by ID, check progress, cancel, create workspaces/worktrees, use the CLI against remote hosts, create schedules and heartbeats. Paseo tool injection is off by default; workers appear in a Subagents track and completion notifies the parent.

   Locator

   public-docs/orchestration.md

   Retrieved

   2026-10-08

2. Paseo: public-docs/orchestration-workflows.md

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Recipes: fan-out research (workers share files), parallel edits in separate worktrees, implement-then-review, prompt another agent by ID, redirect/cancel a worker, remote-host CLI, heartbeats. Distinguishes interactive Paseo subagents from read-only native provider subagent timelines.

   Locator

   public-docs/orchestration-workflows.md

   Retrieved

   2026-10-09

3. Paseo: MCP reference

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Paseo MCP server on the daemon (enabled by default; injection into agents off by default) exposing agent, workspace, workspace-script, terminal, schedule/heartbeat, profile, provider, permission, browser and voice tools; per-provider tool allow/deny policy, explicitly not a security boundary.

   Locator

   public-docs/mcp.md

   Retrieved

   2026-10-09

4. Paseo: CLI reference

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): CLI covers run/ls/attach/send/logs/wait/stop, projects, workspaces, terminals, scripts, plugins, schedules, permissions (paseo permit ls/allow/deny), agent modes and detach, daemon management, Hub commands, remote --host (including ssh://) and JSON/YAML output.

   Locator

   public-docs/cli.md

   Retrieved

   2026-10-09

5. Paseo: Agent lifecycle

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Agent states initializing/idle/running/error/closed; closed agents keep identity, timeline and persistence handle and resume under the same ID; a runtime that dies between turns can leave an idle-looking agent until reported; cancellation and permission notifications to parent agents.

   Locator

   docs/agent-lifecycle.md

   Retrieved

   2026-10-09

6. Paseo: Agent profiles

   Finding: Named profiles store provider, model, mode, thinking level and features with When-to-use notes that orchestrating agents read via list_profiles.

   Locator

   public-docs/agent-profiles.md

   Retrieved

   2026-10-08

7. Paseo: Orchestration skills

   Finding: Installable /paseo, /paseo-handoff, /paseo-committee and /paseo-advisor skills for delegation, handoff and second opinions.

   Locator

   public-docs/skills.md

   Retrieved

   2026-10-08

paseo:COORD-04

Paseo schedules start new agents on a cron cadence (with run and expiry limits) and heartbeats re-prompt an existing agent; Hub starts workflows from GitHub, Slack and Discord events.

Checked

2026-10-09 · checked 1 month ago

Cross-check

cross-checked 2026-10-09

Plan

Not specified in this finding

Surface

Paseo daemon and APIs; Paseo Hub; Paseo CLI and TypeScript SDK

Version

v0.11.1 release (tag ab10a6694); sources read at main d0bc188a5 (eight later commits)

• Schedules run on the daemon, so the daemon must be up; Hub does not queue events and does not retry an offline dispatch; overlap behavior was not documented.

1. Paseo: public-docs/orchestration-workflows.md

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Recipes: fan-out research (workers share files), parallel edits in separate worktrees, implement-then-review, prompt another agent by ID, redirect/cancel a worker, remote-host CLI, heartbeats. Distinguishes interactive Paseo subagents from read-only native provider subagent timelines.

   Locator

   public-docs/orchestration-workflows.md

   Retrieved

   2026-10-09

2. Paseo: Why Paseo?

   Finding: Re-read 2026-10-09 at pinned d0bc188 (unchanged for the cited statements): Desktop app on macOS, Windows and Linux; daemon owns agents and workspaces; mobile, web and CLI clients connect to the same environment; runs agents with the user's own subscriptions, credentials, skills and MCP servers; Apache-2.0 with no telemetry, tracking or required Paseo account. The v0.11.1 tag text of this page is an earlier version; it says the daemon manages agents and clients connect locally or over a relay, and it also states no telemetry and Apache-2.0.

   Locator

   public-docs/why.md

   Retrieved

   2026-10-09

3. Paseo: Schedules

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Schedules start a new agent per run on a cron cadence; heartbeats prompt one existing agent; both can be created in the app, from chat, via CLI or MCP; inspect, pause, resume, run once, update, delete.

   Locator

   public-docs/schedules.md

   Retrieved

   2026-10-09

4. Paseo: Schedules from the CLI

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): paseo schedule create with --every/--cron, --timezone, --max-runs, --expires-in, --run-now, --provider, --cwd; ls/inspect/logs/pause/resume/run-once/update/delete; heartbeats via paseo heartbeat; remote daemons via --host.

   Locator

   public-docs/schedules-cli.md

   Retrieved

   2026-10-09

5. Paseo: How Hub works

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Connections, daemons, projects, environments, triggers, workflows and steps; triggers require a non-empty from_users allowlist; configuration revisions validated on sync with previous revision kept on failure; Hub does not sandbox agents.

   Locator

   public-docs/hub/concepts.md

   Retrieved

   2026-10-09

6. Paseo: Daemons in Hub

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Daemon enrollment via paseo hub login/connect; hub.execute grant defaults to no; Hub resends the same create intent with the same execution id after restart or lost response; offline daemon fails dispatch with daemon_not_connected and nothing is queued; revoke from Hub.

   Locator

   public-docs/hub/daemons.md

   Retrieved

   2026-10-09

7. Paseo: Hub activity

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Every accepted event is recorded with a bounded unrouted reason; project Activity lists trigger runs and execution state; nothing is retried or queued.

   Locator

   public-docs/hub/activity.md

   Retrieved

   2026-10-09

8. Paseo: Hub FAQ

   Finding: Hub is optional; configuration can be edited in the dashboard with a manual source or read-only from a GitHub source; only from_users can trigger; offline daemon dispatch fails and is not queued; agents reply to Slack/Discord via hub.reply.

   Locator

   public-docs/hub/faq.md

   Retrieved

   2026-10-08

paseo:COORD-05

Users and parent agents can cancel a turn, stop or kill an agent, send follow-ups, change mode, and answer permission requests from app, CLI or MCP; some providers support mid-turn steering.

Checked

2026-10-09 · checked 1 month ago

Cross-check

cross-checked 2026-10-09

Plan

Not specified in this finding

Surface

Paseo desktop; Paseo mobile; Paseo daemon and APIs; Paseo CLI and TypeScript SDK

Version

v0.11.1 release (tag ab10a6694); sources read at main d0bc188a5 (eight later commits)

• Pause/resume is provider-dependent; steering absent for Antigravity; notification channels not fully documented.

1. Paseo: CHANGELOG.md

   Finding: Re-read 2026-10-09 at pinned CHANGELOG.md (d0bc188, identical to main). The file is unchanged between the v0.11.1 tag and d0bc188; its top entry is 0.11.1 (2026-10-07) and there is no Unreleased heading. Earlier finding: 0.11.0 adds the plugin registry, Muse Code and Antigravity providers, a Usage view of subscription quota windows, and OMP mid-turn steering; 0.11.1 adds Claude Haiku 5.5 support and fixes subagent status and Claude history after daemon restart. Earlier entries mention push notifications, GitLab/Gitea/Forgejo/Codeberg PR support and PR check summaries.

   Locator

   0.11.1 and 0.11.0 sections

   Retrieved

   2026-10-09

   Source date

   2026-10-07

2. Paseo: public-docs/orchestration.md

   Finding: Agents can launch other agents across providers and models, prompt them by ID, check progress, cancel, create workspaces/worktrees, use the CLI against remote hosts, create schedules and heartbeats. Paseo tool injection is off by default; workers appear in a Subagents track and completion notifies the parent.

   Locator

   public-docs/orchestration.md

   Retrieved

   2026-10-08

3. Paseo: public-docs/orchestration-workflows.md

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Recipes: fan-out research (workers share files), parallel edits in separate worktrees, implement-then-review, prompt another agent by ID, redirect/cancel a worker, remote-host CLI, heartbeats. Distinguishes interactive Paseo subagents from read-only native provider subagent timelines.

   Locator

   public-docs/orchestration-workflows.md

   Retrieved

   2026-10-09

4. Paseo: Supported providers

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Native: Claude Code, Codex, OpenCode, Pi, Antigravity (agy CLI, Full access only, no Paseo MCP tools or steering), Muse Code. ACP catalog lists about 35 more agents (for example Cursor, Gemini CLI, GitHub Copilot, Junie, Amp, Cline, goose); anything else can be added manually.

   Locator

   public-docs/supported-providers.md

   Retrieved

   2026-10-09

5. Paseo: MCP reference

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Paseo MCP server on the daemon (enabled by default; injection into agents off by default) exposing agent, workspace, workspace-script, terminal, schedule/heartbeat, profile, provider, permission, browser and voice tools; per-provider tool allow/deny policy, explicitly not a security boundary.

   Locator

   public-docs/mcp.md

   Retrieved

   2026-10-09

6. Paseo: CLI reference

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): CLI covers run/ls/attach/send/logs/wait/stop, projects, workspaces, terminals, scripts, plugins, schedules, permissions (paseo permit ls/allow/deny), agent modes and detach, daemon management, Hub commands, remote --host (including ssh://) and JSON/YAML output.

   Locator

   public-docs/cli.md

   Retrieved

   2026-10-09

7. Paseo: Agent lifecycle

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Agent states initializing/idle/running/error/closed; closed agents keep identity, timeline and persistence handle and resume under the same ID; a runtime that dies between turns can leave an idle-looking agent until reported; cancellation and permission notifications to parent agents.

   Locator

   docs/agent-lifecycle.md

   Retrieved

   2026-10-09

paseo:COORD-06

Paseo has a project/workspace sidebar and Subagents track but a fleet board with dependencies and workload views was not documented.

Checked

2026-10-09 · checked 1 month ago

Cross-check

cross-checked 2026-10-09

Plan

Not specified in this finding

Surface

Paseo desktop

Version

v0.11.1 release (tag ab10a6694); sources read at main d0bc188a5 (eight later commits)

• Documentation and source-level pass of Paseo v0.11.1; no hands-on scenario was run and unknown sub-questions remain unknown.

1. Paseo: public-docs/orchestration-workflows.md

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Recipes: fan-out research (workers share files), parallel edits in separate worktrees, implement-then-review, prompt another agent by ID, redirect/cancel a worker, remote-host CLI, heartbeats. Distinguishes interactive Paseo subagents from read-only native provider subagent timelines.

   Locator

   public-docs/orchestration-workflows.md

   Retrieved

   2026-10-09

2. Paseo: Workspaces

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Project, workspace and session model; workspace isolation is Local (existing directory, shared files) or Worktree (managed git worktree and branch); workspaces can be created without an agent; any directory on a daemon host can be a project.

   Locator

   public-docs/workspaces.md

   Retrieved

   2026-10-09

paseo:COORD-07

Paseo offers profiles, skills and natural-language orchestration; richer workflow flexibility questions are unestablished.

Checked

2026-10-09 · checked 1 month ago

Cross-check

cross-checked 2026-10-09

Plan

Not specified in this finding

Surface

Paseo desktop; Paseo daemon and APIs

Version

v0.11.1 release (tag ab10a6694); sources read at main d0bc188a5 (eight later commits)

• Documentation and source-level pass of Paseo v0.11.1; no hands-on scenario was run and unknown sub-questions remain unknown.

1. Paseo: public-docs/orchestration.md

   Finding: Agents can launch other agents across providers and models, prompt them by ID, check progress, cancel, create workspaces/worktrees, use the CLI against remote hosts, create schedules and heartbeats. Paseo tool injection is off by default; workers appear in a Subagents track and completion notifies the parent.

   Locator

   public-docs/orchestration.md

   Retrieved

   2026-10-08

2. Paseo: CLI reference

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): CLI covers run/ls/attach/send/logs/wait/stop, projects, workspaces, terminals, scripts, plugins, schedules, permissions (paseo permit ls/allow/deny), agent modes and detach, daemon management, Hub commands, remote --host (including ssh://) and JSON/YAML output.

   Locator

   public-docs/cli.md

   Retrieved

   2026-10-09

3. Paseo: TypeScript SDK

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): @getpaseo/client drives a daemon from a program: create agents with provider/model, cwd and prompt, wait for finish, send follow-ups; agents created through the SDK appear in the Paseo app and persist after the program exits.

   Locator

   public-docs/sdk/index.md

   Retrieved

   2026-10-09

4. Paseo: Agent profiles

   Finding: Named profiles store provider, model, mode, thinking level and features with When-to-use notes that orchestrating agents read via list_profiles.

   Locator

   public-docs/agent-profiles.md

   Retrieved

   2026-10-08

5. Paseo: Orchestration skills

   Finding: Installable /paseo, /paseo-handoff, /paseo-committee and /paseo-advisor skills for delegation, handoff and second opinions.

   Locator

   public-docs/skills.md

   Retrieved

   2026-10-08

6. Built-in Paseo tools (MCP) lines 31 to 37; CLI route line 48; skills line 44

   Finding: Re-read 2026-10-09 at tag ab10a6694: the MCP route needs Enable Paseo tools, which is off by default (line 36). "This route does not require enabling tool injection" for the CLI route (line 48). Orchestration skills are optional (line 44).

   Locator

   Built-in Paseo tools (MCP) lines 31 to 37; CLI route line 48; skills line 44

   Retrieved

   2026-10-09

paseo:RUN-01

Paseo runs agents on operator-owned local or server daemon machines. Clients attach independently, while hosted Hub only dispatches to connected user daemons and does not provide agent compute.

Checked

2026-11-13 · checked 2 days ago

Plan

Not specified in this finding

Surface

Paseo daemon and APIs; Paseo desktop; Paseo mobile; Paseo web; Paseo CLI and TypeScript SDK

Version

Paseo v0.15.4 at 1c00b365c9e0b74c1580eba33d905d693125ae21 and current Hub page; checked 2026-11-13

• Documentation and pinned source inspection only; no hands-on scenario was run.
• Other atomic questions remain unestablished: resources, region, expiry.

1. Paseo homepage

   Finding: Re-read 2026-10-09 (live homepage): Download for Mac links to the v0.11.1 arm64 DMG; iOS App Store and Google Play listings; app.paseo.sh web app; headless daemon; CLI and TypeScript SDK; providers Claude Code, Codex, OpenCode, Pi, OMP, Cursor, Muse Code, Antigravity and about 33 more through ACP; Apache 2.0 and free and open source; no telemetry, tracking or forced login; optional end-to-end encrypted relay; Hub named for teams and triggers. The maintainer is described as one full-time person with no investors; the project is funded by sponsorship and Hub. No roadmap or coming-soon wording found.

   Locator

   Run it anywhere; providers; FAQ; sponsor section

   Retrieved

   2026-10-09

2. Paseo: public-docs/orchestration-workflows.md

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Recipes: fan-out research (workers share files), parallel edits in separate worktrees, implement-then-review, prompt another agent by ID, redirect/cancel a worker, remote-host CLI, heartbeats. Distinguishes interactive Paseo subagents from read-only native provider subagent timelines.

   Locator

   public-docs/orchestration-workflows.md

   Retrieved

   2026-10-09

3. Paseo: Getting started

   Finding: Desktop app bundles its own daemon; Linux .deb/.rpm/AppImage; headless install via npm i -g @getpaseo/cli; Docker image; at least one provider CLI must be installed by the user; gh CLI recommended for PR-aware worktrees.

   Locator

   public-docs/index.md

   Retrieved

   2026-10-08

4. Paseo: Why Paseo?

   Finding: Re-read 2026-10-09 at pinned d0bc188 (unchanged for the cited statements): Desktop app on macOS, Windows and Linux; daemon owns agents and workspaces; mobile, web and CLI clients connect to the same environment; runs agents with the user's own subscriptions, credentials, skills and MCP servers; Apache-2.0 with no telemetry, tracking or required Paseo account. The v0.11.1 tag text of this page is an earlier version; it says the daemon manages agents and clients connect locally or over a relay, and it also states no telemetry and Apache-2.0.

   Locator

   public-docs/why.md

   Retrieved

   2026-10-09

5. Paseo: Connectivity

   Finding: Client-to-daemon transports: SSH (desktop and CLI, daemon must already run), optional end-to-end encrypted relay (disabled until enabled), Tailscale/direct TCP with optional password.

   Locator

   public-docs/connectivity.md

   Retrieved

   2026-10-08

6. Paseo: Security

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Daemon on user hardware; relay is E2E encrypted (Curve25519/NaCl box) and off by default; optional bcrypt-hashed password for direct connections; DNS-rebinding host allowlist; Paseo never stores or transmits provider API keys; agents run in the user's context; Docker image runs as non-root but mounts are the boundary; Hub identities are separate from daemon identities.

   Locator

   public-docs/security.md

   Retrieved

   2026-10-09

7. Paseo: Docker

   Finding: Official image ghcr.io/getpaseo/paseo runs the daemon and bundled web UI as non-root user; does not bundle agent CLIs; PASEO_PASSWORD recommended before publishing the port; state under /home/paseo.

   Locator

   public-docs/docker.md

   Retrieved

   2026-10-08

8. Paseo: Claude Code provider

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Runs the official claude CLI via the Claude Agent SDK; usage counts against the user's normal Claude plan limits with no separate Agent SDK credit pool; a Claude plan including Claude Code is required.

   Locator

   public-docs/claude-code.md

   Retrieved

   2026-10-09

9. Paseo: Related projects

   Finding: Lists community-built projects (not first-party): a VS Code extension, a VS Code Web plugin, a macOS menu-bar status app, cross-daemon comms, Docker packaging, GCP devbox provisioning, and the paseo.cafe plugin directory; states they are not endorsed.

   Locator

   public-docs/community.md

   Retrieved

   2026-10-08

10. Paseo: Self-hosting the web UI

    Finding: Daemon can serve the full browser UI from its own address (off by default, features.webUi.enabled); password and TLS reverse proxy guidance.

    Locator

    public-docs/web-ui.md

    Retrieved

    2026-10-08

11. Paseo: Hub FAQ Can the Hub run code on my machines; plan list

    Finding: The first-party Hub page says agents run on connected user daemons and nowhere else. Both Hosted Free and Pro specify that daemons run on the user machines. Hosted Hub does not provision agent compute.

    Locator

    Hub FAQ Can the Hub run code on my machines; plan list

    Retrieved

    2026-11-13

12. Paseo: public-docs/why.md

    Finding: The current pinned release documents automatic local daemon management, with the daemon owning running agents/workspaces and separate desktop/mobile/web/CLI clients. It explicitly supports running the environment on a server and continuing from other devices; client-laptop disconnect does not move execution off that operator daemon host.

    Locator

    Develop in one workspace; Continue from another device

    Retrieved

    2026-11-13

13. Paseo: public-docs/connectivity.md

    Finding: The pinned release explicitly supports a daemon on the user computer or server. Desktop and CLI attach through SSH to an already-running remote daemon, while mobile can use relay/Tailscale; this is an operator-owned execution host rather than a vendor compute service.

    Locator

    SSH setup and Tailscale daemon listen configuration

    Retrieved

    2026-11-13

paseo:RUN-02

Paseo isolates file changes with optional git worktrees per workspace; same-workspace agents share files. Paseo documents no per-task process sandbox: Hub states it does not sandbox provider processes, provider-native sandbox settings apply, and network isolation is unknown.

Checked

2026-10-09 · checked 1 month ago

Cross-check

cross-checked 2026-11-10

Plan

Not specified in this finding

Surface

Paseo desktop; Paseo daemon and APIs; Paseo Hub

Version

v0.11.1 release (tag ab10a6694); sources read at main d0bc188a5 (eight later commits)

• Docker image is a deployment option, not per-task isolation; Hub explicitly states it does not sandbox the agent; provider-native sandbox options exist per provider.

1. Paseo: Workspaces

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Project, workspace and session model; workspace isolation is Local (existing directory, shared files) or Worktree (managed git worktree and branch); workspaces can be created without an agent; any directory on a daemon host can be a project.

   Locator

   public-docs/workspaces.md

   Retrieved

   2026-10-09

2. Paseo: Git worktrees

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Worktrees under $PASEO_HOME/worktrees; branch-off, checkout-branch and checkout-pr modes; paseo.json setup/teardown hooks, scripts, supervised services with per-worktree ports, port ranges or external allocator, reverse proxy hostnames, auto-opened terminals.

   Locator

   public-docs/worktrees.md

   Retrieved

   2026-10-09

3. Paseo: Security

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Daemon on user hardware; relay is E2E encrypted (Curve25519/NaCl box) and off by default; optional bcrypt-hashed password for direct connections; DNS-rebinding host allowlist; Paseo never stores or transmits provider API keys; agents run in the user's context; Docker image runs as non-root but mounts are the boundary; Hub identities are separate from daemon identities.

   Locator

   public-docs/security.md

   Retrieved

   2026-10-09

4. Paseo: MCP reference

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Paseo MCP server on the daemon (enabled by default; injection into agents off by default) exposing agent, workspace, workspace-script, terminal, schedule/heartbeat, profile, provider, permission, browser and voice tools; per-provider tool allow/deny policy, explicitly not a security boundary.

   Locator

   public-docs/mcp.md

   Retrieved

   2026-10-09

5. Paseo: Hub security

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Hub does not sandbox provider processes; hub.execute permission on a daemon is separate from enrollment; provider-native sandbox options per named agent; protect the configuration repository; narrow from_users filters.

   Locator

   public-docs/hub/security.md

   Retrieved

   2026-10-09

6. Paseo: GitHub access

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): A step holds GitHub authority only through a github block with declared repositories, permissions and a token lifetime up to 1h; git/gh run with an installation token and App bot identity.

   Locator

   public-docs/hub/github.md

   Retrieved

   2026-10-09

7. Paseo: Docker

   Finding: Official image ghcr.io/getpaseo/paseo runs the daemon and bundled web UI as non-root user; does not bundle agent CLIs; PASEO_PASSWORD recommended before publishing the port; state under /home/paseo.

   Locator

   public-docs/docker.md

   Retrieved

   2026-10-08

8. Paseo: Run parallel tasks

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Desktop walkthrough: separate worktree workspaces run agents concurrently, Changes tab for diffs, Files, terminals and built-in browser tabs; commit and PR via the user's usual git workflow or the agent; processes still share machine ports.

   Locator

   public-docs/parallel-development.md

   Retrieved

   2026-10-09

9. Paseo v0.15.3: public-docs/hub/security.md

   Finding: Hub does not sandbox agent processes. For stronger host containment it recommends an OS user, container or VM; named Codex options can deny network_access and choose writable roots, with provider/OS enforcement remaining separate.

   Locator

   Protect configuration authority; Provider-native controls

   Retrieved

   2026-11-07

10. Paseo v0.15.3: public-docs/docker.md

    Finding: Official stable Docker image runs daemon and launched agents as non-root paseo with explicit code/home mounts; this is host deployment, not one container per task. Agent CLIs are installed in a child image.

    Locator

    What the image includes; Volumes; Security

    Retrieved

    2026-11-07

paseo:RUN-03

Paseo persists agent records and timelines and resumes closed agents under the same ID. Since 0.15.0 daemon restarts keep terminal programs running, but interrupted running agents resume in their existing conversations only when the opt-in agent recovery setting (agents.resumeOnStartup, off by default) is on; the troubleshooting page's broader 'running agents keep going' wording is not reconciled with this. Documented gaps include runtime death between turns and the Antigravity transcript reset.

Checked

2026-10-09 · checked 1 month ago

Cross-check

cross-checked 2026-11-10

Plan

Not specified in this finding

Surface

Paseo daemon and APIs; Paseo Hub

Version

Paseo v0.15.3 (d91ae138cb931447635e94296023414a58bedcc5) lifecycle doc and changelog; earlier v0.11.1 (ab10a6694) docs read at d0bc188a5

• Documented behavior only; no crash or restart test was run.
• client_disconnect rests on the main-branch wording of doc-why at d0bc188 (unchanged at v0.15.3).
• Restart behaviour differs by source: troubleshooting says running agents keep going after Restart daemon, while the v0.15.3 lifecycle doc and 0.15.0 changelog make agent resumption after a restart opt-in (off by default).

1. Paseo: CHANGELOG.md

   Finding: Re-read 2026-10-09 at pinned CHANGELOG.md (d0bc188, identical to main). The file is unchanged between the v0.11.1 tag and d0bc188; its top entry is 0.11.1 (2026-10-07) and there is no Unreleased heading. Earlier finding: 0.11.0 adds the plugin registry, Muse Code and Antigravity providers, a Usage view of subscription quota windows, and OMP mid-turn steering; 0.11.1 adds Claude Haiku 5.5 support and fixes subagent status and Claude history after daemon restart. Earlier entries mention push notifications, GitLab/Gitea/Forgejo/Codeberg PR support and PR check summaries.

   Locator

   0.11.1 and 0.11.0 sections

   Retrieved

   2026-10-09

   Source date

   2026-10-07

2. Paseo: Why Paseo?

   Finding: Re-read 2026-10-09 at pinned d0bc188 (unchanged for the cited statements): Desktop app on macOS, Windows and Linux; daemon owns agents and workspaces; mobile, web and CLI clients connect to the same environment; runs agents with the user's own subscriptions, credentials, skills and MCP servers; Apache-2.0 with no telemetry, tracking or required Paseo account. The v0.11.1 tag text of this page is an earlier version; it says the daemon manages agents and clients connect locally or over a relay, and it also states no telemetry and Apache-2.0.

   Locator

   public-docs/why.md

   Retrieved

   2026-10-09

3. Paseo: Supported providers

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Native: Claude Code, Codex, OpenCode, Pi, Antigravity (agy CLI, Full access only, no Paseo MCP tools or steering), Muse Code. ACP catalog lists about 35 more agents (for example Cursor, Gemini CLI, GitHub Copilot, Junie, Amp, Cline, goose); anything else can be added manually.

   Locator

   public-docs/supported-providers.md

   Retrieved

   2026-10-09

4. Paseo: Daemons in Hub

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Daemon enrollment via paseo hub login/connect; hub.execute grant defaults to no; Hub resends the same create intent with the same execution id after restart or lost response; offline daemon fails dispatch with daemon_not_connected and nothing is queued; revoke from Hub.

   Locator

   public-docs/hub/daemons.md

   Retrieved

   2026-10-09

5. Paseo: Agent lifecycle

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Agent states initializing/idle/running/error/closed; closed agents keep identity, timeline and persistence handle and resume under the same ID; a runtime that dies between turns can leave an idle-looking agent until reported; cancellation and permission notifications to parent agents.

   Locator

   docs/agent-lifecycle.md

   Retrieved

   2026-10-09

6. Paseo: Troubleshooting

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Desktop and daemon log locations (daemon.log under PASEO_HOME, main.log per OS); restarting the daemon keeps running agents and clients reconnect automatically; login-shell PATH resolution on macOS/Linux only.

   Locator

   public-docs/troubleshooting.md

   Retrieved

   2026-10-09

7. Paseo v0.15.3: docs/agent-lifecycle.md

   Finding: Restart recovery is opt-in resumeOnStartup and reopens saved conversation/settings with a configurable Resume working prompt; best-effort recovery can lose or repeat continuation, no exactly-once/retry loop. Idle runtimes close after one hour while identity/timeline persist; background work can die with a provider.

   Locator

   Daemon restart recovery; Runtime residency; Limitations; Storage

   Retrieved

   2026-11-07

paseo:RUN-04

Paseo worktree setup hooks, scripts and supervised services with port allocation address environment setup; caching, snapshots and automatic repair are not documented.

Checked

2026-10-09 · checked 1 month ago

Cross-check

cross-checked 2026-10-09

Plan

Not specified in this finding

Surface

Paseo desktop; Paseo daemon and APIs

Version

v0.11.1 release (tag ab10a6694); sources read at main d0bc188a5 (eight later commits)

• Setup is user-authored shell; worktrees start without dependencies or ignored files such as .env.

1. Paseo: Git worktrees

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Worktrees under $PASEO_HOME/worktrees; branch-off, checkout-branch and checkout-pr modes; paseo.json setup/teardown hooks, scripts, supervised services with per-worktree ports, port ranges or external allocator, reverse proxy hostnames, auto-opened terminals.

   Locator

   public-docs/worktrees.md

   Retrieved

   2026-10-09

2. Paseo: MCP reference

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Paseo MCP server on the daemon (enabled by default; injection into agents off by default) exposing agent, workspace, workspace-script, terminal, schedule/heartbeat, profile, provider, permission, browser and voice tools; per-provider tool allow/deny policy, explicitly not a security boundary.

   Locator

   public-docs/mcp.md

   Retrieved

   2026-10-09

3. Paseo: Run parallel tasks

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Desktop walkthrough: separate worktree workspaces run agents concurrently, Changes tab for diffs, Files, terminals and built-in browser tabs; commit and PR via the user's usual git workflow or the agent; processes still share machine ports.

   Locator

   public-docs/parallel-development.md

   Retrieved

   2026-10-09

paseo:RUN-05

Paseo documents run counts and expiry on schedules and max_runtime / idle_timeout on Hub steps; token, spend and turn limits were not documented by Paseo.

Checked

2026-10-09 · checked 1 month ago

Cross-check

cross-checked 2026-10-09

Plan

Not specified in this finding

Surface

Paseo daemon and APIs; Paseo Hub

Version

v0.11.1 release (tag ab10a6694); sources read at main d0bc188a5 (eight later commits)

• Documentation and source-level pass of Paseo v0.11.1; no hands-on scenario was run and unknown sub-questions remain unknown.

1. Paseo: public-docs/orchestration-workflows.md

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Recipes: fan-out research (workers share files), parallel edits in separate worktrees, implement-then-review, prompt another agent by ID, redirect/cancel a worker, remote-host CLI, heartbeats. Distinguishes interactive Paseo subagents from read-only native provider subagent timelines.

   Locator

   public-docs/orchestration-workflows.md

   Retrieved

   2026-10-09

2. Paseo: Schedules from the CLI

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): paseo schedule create with --every/--cron, --timezone, --max-runs, --expires-in, --run-now, --provider, --cwd; ls/inspect/logs/pause/resume/run-once/update/delete; heartbeats via paseo heartbeat; remote daemons via --host.

   Locator

   public-docs/schedules-cli.md

   Retrieved

   2026-10-09

3. Paseo: Daemons in Hub

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Daemon enrollment via paseo hub login/connect; hub.execute grant defaults to no; Hub resends the same create intent with the same execution id after restart or lost response; offline daemon fails dispatch with daemon_not_connected and nothing is queued; revoke from Hub.

   Locator

   public-docs/hub/daemons.md

   Retrieved

   2026-10-09

4. Paseo: GitHub access

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): A step holds GitHub authority only through a github block with declared repositories, permissions and a token lifetime up to 1h; git/gh run with an installation token and App bot identity.

   Locator

   public-docs/hub/github.md

   Retrieved

   2026-10-09

5. Paseo: Hub activity

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Every accepted event is recorded with a bounded unrouted reason; project Activity lists trigger runs and execution state; nothing is retried or queued.

   Locator

   public-docs/hub/activity.md

   Retrieved

   2026-10-09

paseo:RUN-06

Paseo provides agent timelines (paseo logs), daemon and desktop logs, a Usage view of subscription quota windows and Hub Activity records; cost, performance and per-project statistics were not documented.

Checked

2026-11-07 · checked 1 week ago

Cross-check

cross-checked 2026-11-07

Plan

Not specified in this finding

Surface

Paseo desktop; Paseo daemon and APIs; Paseo Hub; Paseo CLI and TypeScript SDK

Version

Paseo v0.15.3 at d91ae138cb931447635e94296023414a58bedcc5; hosted Hub page reread 2026-11-07

• Documentation and source-level pass of Paseo v0.15.3; no hands-on scenario was run and unknown sub-questions remain unknown.

1. Paseo: CHANGELOG.md

   Finding: Current stable changelog starts 0.15.3, November 6, 2026, and describes stable changes since the older v0.11.1 source pass.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

   Source date

   2026-11-06

2. Paseo: MCP reference

   Finding: Paseo MCP server on the daemon (enabled by default; injection into agents off by default) exposing agent, workspace, workspace-script, terminal, schedule/heartbeat, profile, provider, permission, browser and voice tools; per-provider tool allow/deny policy, explicitly not a security boundary.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

3. Paseo: CLI reference

   Finding: CLI covers run/ls/attach/send/logs/wait/stop, projects, workspaces, terminals, scripts, plugins, schedules, permissions (paseo permit ls/allow/deny), agent modes and detach, daemon management, Hub commands, remote --host (including ssh://) and JSON/YAML output.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

4. Paseo: Hub activity

   Finding: Every accepted event is recorded with a bounded unrouted reason; project Activity lists trigger runs and execution state; nothing is retried or queued.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

5. Paseo: Agent lifecycle

   Finding: Agent states initializing/idle/running/error/closed; closed agents keep identity, timeline and persistence handle and resume under the same ID; a runtime that dies between turns can leave an idle-looking agent until reported; cancellation and permission notifications to parent agents.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

6. Paseo: Troubleshooting

   Finding: Desktop and daemon log locations (daemon.log under PASEO_HOME, main.log per OS); restarting the daemon keeps running agents and clients reconnect automatically; login-shell PATH resolution on macOS/Linux only.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

paseo:RUN-07

Paseo shows each subscription account's quota windows and context-window usage; per-task or per-epic dollar cost, token reconciliation and alerts were not documented.

Checked

2026-10-09 · checked 1 month ago

Cross-check

cross-checked 2026-10-09

Plan

Not specified in this finding

Surface

Paseo desktop; Paseo mobile

Version

v0.11.1 release (tag ab10a6694); sources read at main d0bc188a5 (eight later commits)

• Usage view reflects account quota windows, not task cost.

1. Paseo: CHANGELOG.md

   Finding: Re-read 2026-10-09 at pinned CHANGELOG.md (d0bc188, identical to main). The file is unchanged between the v0.11.1 tag and d0bc188; its top entry is 0.11.1 (2026-10-07) and there is no Unreleased heading. Earlier finding: 0.11.0 adds the plugin registry, Muse Code and Antigravity providers, a Usage view of subscription quota windows, and OMP mid-turn steering; 0.11.1 adds Claude Haiku 5.5 support and fixes subagent status and Claude history after daemon restart. Earlier entries mention push notifications, GitLab/Gitea/Forgejo/Codeberg PR support and PR check summaries.

   Locator

   0.11.1 and 0.11.0 sections

   Retrieved

   2026-10-09

   Source date

   2026-10-07

paseo:RUN-08

Paseo documents no compute-aware scheduling; Hub dispatch is not queued and agents are launched on demand.

Checked

2026-10-09 · checked 1 month ago

Cross-check

cross-checked 2026-10-09

Plan

Not specified in this finding

Surface

Paseo daemon and APIs; Paseo Hub

Version

v0.11.1 release (tag ab10a6694); sources read at main d0bc188a5 (eight later commits)

• Documentation and source-level pass of Paseo v0.11.1; no hands-on scenario was run and unknown sub-questions remain unknown.

1. Paseo: Git worktrees

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Worktrees under $PASEO_HOME/worktrees; branch-off, checkout-branch and checkout-pr modes; paseo.json setup/teardown hooks, scripts, supervised services with per-worktree ports, port ranges or external allocator, reverse proxy hostnames, auto-opened terminals.

   Locator

   public-docs/worktrees.md

   Retrieved

   2026-10-09

2. Paseo: MCP reference

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Paseo MCP server on the daemon (enabled by default; injection into agents off by default) exposing agent, workspace, workspace-script, terminal, schedule/heartbeat, profile, provider, permission, browser and voice tools; per-provider tool allow/deny policy, explicitly not a security boundary.

   Locator

   public-docs/mcp.md

   Retrieved

   2026-10-09

3. Paseo: Daemons in Hub

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Daemon enrollment via paseo hub login/connect; hub.execute grant defaults to no; Hub resends the same create intent with the same execution id after restart or lost response; offline daemon fails dispatch with daemon_not_connected and nothing is queued; revoke from Hub.

   Locator

   public-docs/hub/daemons.md

   Retrieved

   2026-10-09

4. Paseo: Hub activity

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Every accepted event is recorded with a bounded unrouted reason; project Activity lists trigger runs and execution state; nothing is retried or queued.

   Locator

   public-docs/hub/activity.md

   Retrieved

   2026-10-09

paseo:TEAM-01

In self-hosted Paseo Hub, distinct permitted Slack users can send instructions to one daemon agent by enabling Same conversation continuity for a Slack trigger. Generic daemon-principal pairing alone does not establish distinct human collaboration.

Checked

2026-11-07 · checked 1 week ago

Plan

Self-hosted early-development Paseo Hub; Slack trigger Agent continuity = Same conversation; explicit hub.execute grant

Surface

Paseo Hub; Paseo daemon and APIs

Availability

beta

Version

Paseo v0.15.4 at 1c00b365c9e0b74c1580eba33d905d693125ae21; Hub source 61e51c56f8756e40c55a30982160ce000f2aa177; checked 2026-11-13

• Documentation and pinned source inspection only; no hands-on scenario was run.
• Other atomic questions remain unestablished: discussion, comments, presence, ordering, conflicts.

1. Paseo Hub plans and pricing

   Finding: Re-read 2026-10-09 (live pricing page): self-hosted Hub is free and open source; Free is $0 per month with 50 agent runs a month and 1 seat; Pro is $15 per seat per month with unlimited runs and seats. Seats are Hub members plus pending invitations; people who only trigger agents through GitHub, Slack or Discord do not count. No card, trial, expiry, SSO, retention or compliance terms are stated on the page. Planned items are listed as "Not built yet" with no dates: provisioning daemons for a team, sharing settings and skills across a team, more integrations.

   Locator

   Plans section

   Retrieved

   2026-11-07

2. Paseo: Hub overview

   Finding: Hub registers daemons and starts agents from GitHub, Slack and Discord activity; triggers as code in .paseo/; records every accepted event and what ran; team visibility; self-hostable; hosted Free plan needs no card and does not expire.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

3. Paseo: Hosted Hub

   Finding: Managed service at hub.paseo.sh; organizations start on Free (one seat, monthly run allowance, no card, no expiry); Pro for unlimited runs, more seats and invitations; self-hosted Hub has no plans or billing.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

4. Paseo: GitHub access

   Finding: A step holds GitHub authority only through a github block with declared repositories, permissions and a token lifetime up to 1h; git/gh run with an installation token and App bot identity.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

5. Paseo: Hub public API

   Finding: Hub API with OpenAPI 3.1 document; organization-scoped API keys with selectable scopes (projects:read, configuration:validate/install, runs:dispatch, daemons:enroll); keys do not grant dashboard access; API operations retain key attribution in audit evidence.

   Locator

   Current stable v0.15.3 file; named headings and operations

   Retrieved

   2026-11-07

6. Paseo v0.15.3: docs/permissions.md

   Finding: Pairing invitations issue credentials to principals with issuer-selected semantic permissions including workspace.read/write/manage, daemon/access administration and hub.execute. This is daemon access policy, not documented named team roles.

   Locator

   Principals, pairing and semantic permission names

   Retrieved

   2026-11-07

7. Paseo: packages/server/src/server/authorization/operation-permissions.ts

   Finding: Pairing issues separate principals with workspace.write permission, which authorizes prompts and agent control. The send-agent-message handler addresses a daemon agent by ID and sends or queues the prompt through its shared agent manager, with no per-human session owner restriction in that handler. Authorized principals on the same daemon can instruct the same agent; team presence and per-human attribution are not established.

   Locator

   send_agent_message_request permission; docs/permissions.md; session.ts handleSendAgentMessage around lines 8305-8425

   Retrieved

   2026-11-13

8. Paseo: src/triggers/slack/match.ts

   Finding: The Hub Slack trigger independently checks each real Slack author ID or username against from_users (or an explicit wildcard); bot messages are excluded. This establishes distinct permitted human Slack identities rather than shared daemon-owner bearer principals.

   Locator

   matchesFilters from_users; events.ts normalized author ID

   Retrieved

   2026-11-13

9. Paseo: src/triggers/slack/provider.ts

   Finding: The first-party Agent continuity control offers Same conversation to continue the same agent for a conversation. Slack conversation keys contain team, channel and root thread timestamp, excluding author ID. Multiple permitted Slack humans in one thread therefore resolve to one continuation key. Custom key is also available; New agent remains separate.

   Locator

   Accepted match conversation key; triggers/panel.tsx Agent continuity control; triggers/continuation.ts

   Retrieved

   2026-11-13

10. Paseo: src/agent-sessions/index.ts

    Finding: The Hub selects/persists one agent session per project plus conversation continuation key and delivers each arriving request to that stored agent ID through connection.send. It does not create a fresh agent for each human message when Same conversation is selected. The UI continuity setting is product-owned and publicly configurable.

    Locator

    AgentSessions.dispatch findAgentSessionByKey and deliver; workflows/engine.ts continuationKey

    Retrieved

    2026-11-13

11. Paseo: docs/hub.md

    Finding: The released Paseo daemon documents opt-in Hub connection and hub.execute permission for ordinary agent creation, messaging, observation and recovery. Hub owns conversation routing and maps it to workspace/agent IDs; send_agent_message_request reaches the existing provider session with its native steer/queue behavior.

    Locator

    Connection and authority; Session grants and agent operations

    Retrieved

    2026-11-13

12. Paseo: public preview availability

    Finding: The first-party Hub README describes early development and breaking changes, while documenting public npm startup and a published Docker image with self-hosted setup. The scoped Hub collaboration and human-access features are publicly enableable preview functionality, not generally available stable features.

    Locator

    Early development notice; Quick start; Run with Docker Compose

    Retrieved

    2026-11-13

paseo:TEAM-02

Paseo Hub has owner, admin and member organization roles with enforced management permissions. Its public authentication composition has no enterprise SSO; daemon grants remain separate.

Checked

2026-11-13 · checked 2 days ago

Plan

Not specified in this finding

Surface

Paseo daemon and APIs; Paseo Hub

Availability

beta

Version

Public Hub source commit 61e51c56f8756e40c55a30982160ce000f2aa177; inspected 2026-11-13

• Documentation and pinned source inspection only; no hands-on scenario was run.
• Other atomic questions remain unestablished: project_roles, provisioning, plan_scope.

1. Paseo Hub plans and pricing

   Finding: Re-read 2026-10-09 (live pricing page): self-hosted Hub is free and open source; Free is $0 per month with 50 agent runs a month and 1 seat; Pro is $15 per seat per month with unlimited runs and seats. Seats are Hub members plus pending invitations; people who only trigger agents through GitHub, Slack or Discord do not count. No card, trial, expiry, SSO, retention or compliance terms are stated on the page. Planned items are listed as "Not built yet" with no dates: provisioning daemons for a team, sharing settings and skills across a team, more integrations.

   Locator

   Plans section

   Retrieved

   2026-10-09

2. Paseo: Security

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Daemon on user hardware; relay is E2E encrypted (Curve25519/NaCl box) and off by default; optional bcrypt-hashed password for direct connections; DNS-rebinding host allowlist; Paseo never stores or transmits provider API keys; agents run in the user's context; Docker image runs as non-root but mounts are the boundary; Hub identities are separate from daemon identities.

   Locator

   public-docs/security.md

   Retrieved

   2026-10-09

3. Paseo: How Hub works

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Connections, daemons, projects, environments, triggers, workflows and steps; triggers require a non-empty from_users allowlist; configuration revisions validated on sync with previous revision kept on failure; Hub does not sandbox agents.

   Locator

   public-docs/hub/concepts.md

   Retrieved

   2026-10-09

4. Paseo: Daemons in Hub

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Daemon enrollment via paseo hub login/connect; hub.execute grant defaults to no; Hub resends the same create intent with the same execution id after restart or lost response; offline daemon fails dispatch with daemon_not_connected and nothing is queued; revoke from Hub.

   Locator

   public-docs/hub/daemons.md

   Retrieved

   2026-10-09

5. Paseo: Hub public API

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Hub API with OpenAPI 3.1 document; organization-scoped API keys with selectable scopes (projects:read, configuration:validate/install, runs:dispatch, daemons:enroll); keys do not grant dashboard access; API operations retain key attribution in audit evidence.

   Locator

   public-docs/hub/api.md

   Retrieved

   2026-10-09

6. Paseo: Daemon permissions

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Daemon authorizes principals via semantic permissions (daemon.read/manage, tunnel.manage, access.manage, workspace.read/write/manage, automation.manage, hub.execute); pairing invitations create principals and credentials with issuer-selected permissions.

   Locator

   docs/permissions.md

   Retrieved

   2026-10-09

7. Paseo: src/auth/organization-policy.ts

   Finding: Paseo Hub defines owner, admin and member roles. Owners manage members, owners and resources; admins manage members and resources but not owners; members can view but cannot manage them. Organization access and member-role mutation handlers enforce these capabilities.

   Locator

   ROLE_CAPABILITIES; organization-contract.ts ORGANIZATION_ROLES; organization-access.ts role mutations

   Retrieved

   2026-11-13

8. Paseo: src/auth/server.ts

   Finding: The public Hub authentication composition enables email/password and the organization plugin. Inspection of src/auth, routes, schema and dependencies for SAML, OIDC, SSO and single sign-on found no enterprise SSO implementation. Provider app OAuth connections are workflow integrations, not enterprise user SSO.

   Locator

   createAuthServer emailAndPassword and plugins; src/auth; package.json

   Retrieved

   2026-11-13

9. Paseo: public preview availability

   Finding: The first-party Hub README describes early development and breaking changes, while documenting public npm startup and a published Docker image with self-hosted setup. The scoped Hub collaboration and human-access features are publicly enableable preview functionality, not generally available stable features.

   Locator

   Early development notice; Quick start; Run with Docker Compose

   Retrieved

   2026-11-13

paseo:TEAM-03

Paseo routes provider permission prompts to the app, CLI and MCP; Hub runs use the provider permission modes set on each named agent (Hub docs say provider modes can bypass approval prompts), and GitHub tokens are declared and time-boxed per step. Approver identity and audited approvals were not documented.

Checked

2026-10-09 · checked 1 month ago

Cross-check

cross-checked 2026-10-09

Plan

Not specified in this finding

Surface

Paseo desktop; Paseo daemon and APIs; Paseo Hub

Version

v0.11.1 release (tag ab10a6694); sources read at main d0bc188a5 (eight later commits)

• Antigravity always runs in Full access; Hub relies on provider-native permission modes and does not sandbox provider processes.

1. Paseo: Supported providers

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Native: Claude Code, Codex, OpenCode, Pi, Antigravity (agy CLI, Full access only, no Paseo MCP tools or steering), Muse Code. ACP catalog lists about 35 more agents (for example Cursor, Gemini CLI, GitHub Copilot, Junie, Amp, Cline, goose); anything else can be added manually.

   Locator

   public-docs/supported-providers.md

   Retrieved

   2026-10-09

2. Paseo: MCP reference

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Paseo MCP server on the daemon (enabled by default; injection into agents off by default) exposing agent, workspace, workspace-script, terminal, schedule/heartbeat, profile, provider, permission, browser and voice tools; per-provider tool allow/deny policy, explicitly not a security boundary.

   Locator

   public-docs/mcp.md

   Retrieved

   2026-10-09

3. Paseo: CLI reference

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): CLI covers run/ls/attach/send/logs/wait/stop, projects, workspaces, terminals, scripts, plugins, schedules, permissions (paseo permit ls/allow/deny), agent modes and detach, daemon management, Hub commands, remote --host (including ssh://) and JSON/YAML output.

   Locator

   public-docs/cli.md

   Retrieved

   2026-10-09

4. Paseo: Hub security

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Hub does not sandbox provider processes; hub.execute permission on a daemon is separate from enrollment; provider-native sandbox options per named agent; protect the configuration repository; narrow from_users filters.

   Locator

   public-docs/hub/security.md

   Retrieved

   2026-10-09

5. Paseo: GitHub access

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): A step holds GitHub authority only through a github block with declared repositories, permissions and a token lifetime up to 1h; git/gh run with an installation token and App bot identity.

   Locator

   public-docs/hub/github.md

   Retrieved

   2026-10-09

6. Paseo: Agent lifecycle

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Agent states initializing/idle/running/error/closed; closed agents keep identity, timeline and persistence handle and resume under the same ID; a runtime that dies between turns can leave an idle-looking agent until reported; cancellation and permission notifications to parent agents.

   Locator

   docs/agent-lifecycle.md

   Retrieved

   2026-10-09

paseo:TEAM-04

Paseo persists agent timelines and Hub records every accepted event and run; export, retention and integrity guarantees were not documented.

Checked

2026-10-09 · checked 1 month ago

Cross-check

cross-checked 2026-10-09

Plan

Not specified in this finding

Surface

Paseo Hub; Paseo daemon and APIs

Version

v0.11.1 release (tag ab10a6694); sources read at main d0bc188a5 (eight later commits)

• Documentation and source-level pass of Paseo v0.11.1; no hands-on scenario was run and unknown sub-questions remain unknown.

1. Paseo: Hub activity

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Every accepted event is recorded with a bounded unrouted reason; project Activity lists trigger runs and execution state; nothing is retried or queued.

   Locator

   public-docs/hub/activity.md

   Retrieved

   2026-10-09

2. Paseo: Agent lifecycle

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Agent states initializing/idle/running/error/closed; closed agents keep identity, timeline and persistence handle and resume under the same ID; a runtime that dies between turns can leave an idle-looking agent until reported; cancellation and permission notifications to parent agents.

   Locator

   docs/agent-lifecycle.md

   Retrieved

   2026-10-09

paseo:TEAM-05

Paseo provides a Changes (diff) tab, Files, PR panels with check summaries and split panes; a pending-review queue and structured request-changes flow were not documented.

Checked

2026-10-09 · checked 1 month ago

Cross-check

cross-checked 2026-10-09

Plan

Not specified in this finding

Surface

Paseo desktop; Paseo mobile

Version

v0.11.1 release (tag ab10a6694); sources read at main d0bc188a5 (eight later commits)

• Documentation and source-level pass of Paseo v0.11.1; no hands-on scenario was run and unknown sub-questions remain unknown.

1. Paseo: CHANGELOG.md

   Finding: Re-read 2026-10-09 at pinned CHANGELOG.md (d0bc188, identical to main). The file is unchanged between the v0.11.1 tag and d0bc188; its top entry is 0.11.1 (2026-10-07) and there is no Unreleased heading. Earlier finding: 0.11.0 adds the plugin registry, Muse Code and Antigravity providers, a Usage view of subscription quota windows, and OMP mid-turn steering; 0.11.1 adds Claude Haiku 5.5 support and fixes subagent status and Claude history after daemon restart. Earlier entries mention push notifications, GitLab/Gitea/Forgejo/Codeberg PR support and PR check summaries.

   Locator

   0.11.1 and 0.11.0 sections

   Retrieved

   2026-10-09

   Source date

   2026-10-07

2. Paseo: Why Paseo?

   Finding: Re-read 2026-10-09 at pinned d0bc188 (unchanged for the cited statements): Desktop app on macOS, Windows and Linux; daemon owns agents and workspaces; mobile, web and CLI clients connect to the same environment; runs agents with the user's own subscriptions, credentials, skills and MCP servers; Apache-2.0 with no telemetry, tracking or required Paseo account. The v0.11.1 tag text of this page is an earlier version; it says the daemon manages agents and clients connect locally or over a relay, and it also states no telemetry and Apache-2.0.

   Locator

   public-docs/why.md

   Retrieved

   2026-10-09

3. Paseo: Run parallel tasks

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Desktop walkthrough: separate worktree workspaces run agents concurrently, Changes tab for diffs, Files, terminals and built-in browser tabs; commit and PR via the user's usual git workflow or the agent; processes still share machine ports.

   Locator

   public-docs/parallel-development.md

   Retrieved

   2026-10-09

paseo:TEAM-06

Another user with pairing credentials can connect to the same daemon and, with workspace.read, see its workspaces and timelines; formal takeover, ownership and attribution semantics were not documented.

Checked

2026-10-09 · checked 1 month ago

Cross-check

cross-checked 2026-10-09

Plan

Not specified in this finding

Surface

Paseo daemon and APIs

Version

v0.11.1 release (tag ab10a6694); sources read at main d0bc188a5 (eight later commits)

• Documentation and source-level pass of Paseo v0.11.1; no hands-on scenario was run and unknown sub-questions remain unknown.

1. Paseo: Daemon permissions

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Daemon authorizes principals via semantic permissions (daemon.read/manage, tunnel.manage, access.manage, workspace.read/write/manage, automation.manage, hub.execute); pairing invitations create principals and credentials with issuer-selected permissions.

   Locator

   docs/permissions.md

   Retrieved

   2026-10-09

2. Paseo: Agent lifecycle

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Agent states initializing/idle/running/error/closed; closed agents keep identity, timeline and persistence handle and resume under the same ID; a runtime that dies between turns can leave an idle-looking agent until reported; cancellation and permission notifications to parent agents.

   Locator

   docs/agent-lifecycle.md

   Retrieved

   2026-10-09

3. Paseo: Orchestration skills

   Finding: Installable /paseo, /paseo-handoff, /paseo-committee and /paseo-advisor skills for delegation, handoff and second opinions.

   Locator

   public-docs/skills.md

   Retrieved

   2026-10-08

paseo:SHIP-01

Paseo shows workspace diffs and files, previews apps in built-in browser tabs and service proxy URLs, and browser automation on the desktop app can take screenshots; a gallery or revision-linked artifact store was not documented.

Checked

2026-10-09 · checked 1 month ago

Cross-check

cross-checked 2026-10-09

Plan

Not specified in this finding

Surface

Paseo desktop

Version

v0.11.1 release (tag ab10a6694); sources read at main d0bc188a5 (eight later commits)

• Documentation and source-level pass of Paseo v0.11.1; no hands-on scenario was run and unknown sub-questions remain unknown.

1. Paseo: Git worktrees

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Worktrees under $PASEO_HOME/worktrees; branch-off, checkout-branch and checkout-pr modes; paseo.json setup/teardown hooks, scripts, supervised services with per-worktree ports, port ranges or external allocator, reverse proxy hostnames, auto-opened terminals.

   Locator

   public-docs/worktrees.md

   Retrieved

   2026-10-09

2. Paseo: Run parallel tasks

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Desktop walkthrough: separate worktree workspaces run agents concurrently, Changes tab for diffs, Files, terminals and built-in browser tabs; commit and PR via the user's usual git workflow or the agent; processes still share machine ports.

   Locator

   public-docs/parallel-development.md

   Retrieved

   2026-10-09

3. Paseo: Agent lifecycle

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Agent states initializing/idle/running/error/closed; closed agents keep identity, timeline and persistence handle and resume under the same ID; a runtime that dies between turns can leave an idle-looking agent until reported; cancellation and permission notifications to parent agents.

   Locator

   docs/agent-lifecycle.md

   Retrieved

   2026-10-09

paseo:SHIP-02

Paseo lets users define named workspace scripts (tests, lint) and run them from app, CLI or agents; required checks, spec gates and enforced policy were not documented.

Checked

2026-10-09 · checked 1 month ago

Cross-check

cross-checked 2026-10-09

Plan

Not specified in this finding

Surface

Paseo desktop; Paseo daemon and APIs

Version

v0.11.1 release (tag ab10a6694); sources read at main d0bc188a5 (eight later commits)

• Documentation and source-level pass of Paseo v0.11.1; no hands-on scenario was run and unknown sub-questions remain unknown.

1. Paseo: CHANGELOG.md

   Finding: Re-read 2026-10-09 at pinned CHANGELOG.md (d0bc188, identical to main). The file is unchanged between the v0.11.1 tag and d0bc188; its top entry is 0.11.1 (2026-10-07) and there is no Unreleased heading. Earlier finding: 0.11.0 adds the plugin registry, Muse Code and Antigravity providers, a Usage view of subscription quota windows, and OMP mid-turn steering; 0.11.1 adds Claude Haiku 5.5 support and fixes subagent status and Claude history after daemon restart. Earlier entries mention push notifications, GitLab/Gitea/Forgejo/Codeberg PR support and PR check summaries.

   Locator

   0.11.1 and 0.11.0 sections

   Retrieved

   2026-10-09

   Source date

   2026-10-07

2. Paseo: public-docs/orchestration-workflows.md

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Recipes: fan-out research (workers share files), parallel edits in separate worktrees, implement-then-review, prompt another agent by ID, redirect/cancel a worker, remote-host CLI, heartbeats. Distinguishes interactive Paseo subagents from read-only native provider subagent timelines.

   Locator

   public-docs/orchestration-workflows.md

   Retrieved

   2026-10-09

3. Paseo: Git worktrees

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Worktrees under $PASEO_HOME/worktrees; branch-off, checkout-branch and checkout-pr modes; paseo.json setup/teardown hooks, scripts, supervised services with per-worktree ports, port ranges or external allocator, reverse proxy hostnames, auto-opened terminals.

   Locator

   public-docs/worktrees.md

   Retrieved

   2026-10-09

4. Paseo: Schedules

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Schedules start a new agent per run on a cron cadence; heartbeats prompt one existing agent; both can be created in the app, from chat, via CLI or MCP; inspect, pause, resume, run once, update, delete.

   Locator

   public-docs/schedules.md

   Retrieved

   2026-10-09

paseo:SHIP-03

Paseo creates worktrees and branches, drafts commit messages and PR text, opens PR workspaces and detects linked PRs; the changelog records pull and merge request support for GitLab, Gitea, Forgejo and Codeberg as well as GitHub. Merge and conflict handling are not documented as Paseo features; git runs through the user or agent.

Checked

2026-10-09 · checked 1 month ago

Cross-check

cross-checked 2026-10-09

Plan

Not specified in this finding

Surface

Paseo desktop; Paseo daemon and APIs

Version

v0.11.1 release (tag ab10a6694); sources read at main d0bc188a5 (eight later commits)

• Commit and PR actions are done by the user or agent through normal git; no merge automation documented.

1. Paseo: CHANGELOG.md

   Finding: Re-read 2026-10-09 at pinned CHANGELOG.md (d0bc188, identical to main). The file is unchanged between the v0.11.1 tag and d0bc188; its top entry is 0.11.1 (2026-10-07) and there is no Unreleased heading. Earlier finding: 0.11.0 adds the plugin registry, Muse Code and Antigravity providers, a Usage view of subscription quota windows, and OMP mid-turn steering; 0.11.1 adds Claude Haiku 5.5 support and fixes subagent status and Claude history after daemon restart. Earlier entries mention push notifications, GitLab/Gitea/Forgejo/Codeberg PR support and PR check summaries.

   Locator

   0.11.1 and 0.11.0 sections

   Retrieved

   2026-10-09

   Source date

   2026-10-07

2. Paseo: Git worktrees

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Worktrees under $PASEO_HOME/worktrees; branch-off, checkout-branch and checkout-pr modes; paseo.json setup/teardown hooks, scripts, supervised services with per-worktree ports, port ranges or external allocator, reverse proxy hostnames, auto-opened terminals.

   Locator

   public-docs/worktrees.md

   Retrieved

   2026-10-09

3. Paseo: Schedules

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Schedules start a new agent per run on a cron cadence; heartbeats prompt one existing agent; both can be created in the app, from chat, via CLI or MCP; inspect, pause, resume, run once, update, delete.

   Locator

   public-docs/schedules.md

   Retrieved

   2026-10-09

4. Paseo: Run parallel tasks

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Desktop walkthrough: separate worktree workspaces run agents concurrently, Changes tab for diffs, Files, terminals and built-in browser tabs; commit and PR via the user's usual git workflow or the agent; processes still share machine ports.

   Locator

   public-docs/parallel-development.md

   Retrieved

   2026-10-09

5. Paseo: Metadata generation

   Finding: Re-read 2026-10-09 at pinned d0bc188 (content unchanged): Background model calls generate workspace titles, branch names, commit messages and PR titles/bodies from the diff.

   Locator

   public-docs/metadata-generation.md

   Retrieved

   2026-10-09