podium

Paseo

47 of 51 criteria have a sourced finding; 42 were also cross-checked by a second agent. Every comparison that includes Paseo links here for scope, limitations, atomic answers and sources.

Humans approve the rubric, templates and prototype; they do not review every finding. An agent source cross-check is not a hands-on product test. A missing sourced finding is not evidence that a capability is absent.

Rubric
0.3 · 51 criteria
Source checks
2026-10-09 to 2026-11-13
Agent cross-checked
42 criteria
Comparisons
1

Access and agent choice

ACC-01

Client access

Sourced partial

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

Scope
Surfaces: 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 · Plan: Not specified · OS: macOS, Windows, Linux, iOS, Android · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
Not separately cross-checked
  • Documentation and pinned source inspection only; no hands-on scenario was run.
9 atomic answers
  • Desktop os [supported] Docs state the desktop app is available on macOS, Windows and Linux (Linux .deb, .rpm, AppImage); homepage download button targets Mac. Sources: paseo:doc-why-nov07, paseo:doc-index-nov07, paseo:website-nov07.
  • Mobile apps [supported] 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. Sources: paseo:website-nov07, paseo:doc-updates-nov07.
  • Browser [supported] Hosted web app at app.paseo.sh and a daemon-served web UI (off by default). Sources: paseo:website-nov07, paseo:doc-web-ui-nov07.
  • Mobile browser [supported] The browser app implements a mobile visual viewport and compact mobile panel layout. Sources: paseo:gaps-mobile-web.
  • Cli [supported] npm i -g @getpaseo/cli installs the CLI and daemon; TypeScript SDK @getpaseo/client. Sources: paseo:doc-index-nov07, paseo:doc-cli-nov07, paseo:doc-sdk-nov07.
  • Editor extensions [partial] No first-party editor extension documented; docs list a community VS Code extension and a VS Code Web plugin as third-party projects. Sources: paseo:doc-community-nov07.
  • Task actions [partial] Tagged claude-code.md documents terminal use from desktop, web or mobile with workspace and Git-change access. Tagged why.md says mobile, web and CLI clients connect to the same environment. Per-action parity across clients is unverified. Sources: paseo:claude-code-tag-mobile-nov07, paseo:why-tag-nov07, paseo:why-main-nov07.
  • Notifications [partial] Changelog records push notifications (a fix for removed hosts still receiving them) and desktop notification sounds; delivery channels and per-client coverage are not documented. Sources: paseo:changelog-nov07.
  • Cross device continuity [partial] Docs: the daemon owns running agents so mobile, web and CLI clients continue in the same environment. No transition test. Sources: paseo:doc-why-nov07, paseo:website-nov07.

Sources: paseo:doc-why-nov07, paseo:doc-index-nov07, paseo:website-nov07, paseo:doc-updates-nov07, paseo:doc-web-ui-nov07, paseo:doc-cli-nov07, paseo:doc-sdk-nov07, paseo:doc-community-nov07, paseo:changelog-nov07, paseo:why-tag-nov07, paseo:why-main-nov07, paseo:claude-code-tag-mobile-nov07, paseo:gaps-mobile-web

Agent cross-checked partial

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.

Scope
Surfaces: 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). · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-10
  • 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.
5 atomic answers
  • Harnesses [supported] 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. Sources: paseo:gap07-provider-catalog, paseo:doc-providers-nov07, paseo:agy-release-1.
  • Model providers [partial] 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. Sources: paseo:doc-providers-nov07, paseo:doc-custom-providers-nov07.
  • Custom adapters [supported] Custom providers via config (extends, ACP agents, binary override) and provider plugins. Sources: paseo:doc-custom-providers-nov07, paseo:doc-plugins-nov07.
  • Session integration [partial] Existing provider sessions can be imported (Import session on the New workspace screen, paseo import); provider coverage differs (Pi/OMP named in changelog). Sources: paseo:changelog-nov07.
  • Mixed harness operation [supported] Orchestration docs: agents can launch workers on any configured provider and model, including different providers in one task. Sources: paseo:orchestration-nov07, paseo:workflows-nov07.

Sources: paseo:doc-providers-nov07, paseo:website-nov07, paseo:changelog-nov07, paseo:doc-custom-providers-nov07, paseo:doc-plugins-nov07, paseo:orchestration-nov07, paseo:workflows-nov07, paseo:supported-providers-tag-nov07, paseo:paseo-homepage-faq-nov07, paseo:gap07-provider-catalog, paseo:agy-release-1

Agent cross-checked partial

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.

Scope
Surfaces: Paseo daemon and APIs, Paseo desktop · Version: Paseo v0.15.3 at d91ae138cb931447635e94296023414a58bedcc5; hosted Hub page reread 2026-11-07 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
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.
7 atomic answers

Sources: paseo:doc-claude-code-nov07, paseo:doc-codex-nov07, paseo:doc-security-nov07, paseo:doc-custom-providers-nov07, paseo:changelog-nov07, paseo:doc-why-nov07, paseo:doc-index-nov07, paseo:paseo-custom-providers-tag-nov07, paseo:paseo-voice-tag-nov07

Agent cross-checked partial

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.

Scope
Surfaces: Paseo desktop, Paseo daemon and APIs · Version: v0.11.1 release (tag ab10a6694); sources read at main d0bc188a5 (eight later commits) · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-10-09 (44 days old)
Agent cross-check
2026-10-09
  • Onboarding steps are documented, not tested. Managed cloud setup is not established: the docs describe user-supplied machines and Hub dispatch to them.
7 atomic answers
  • First task setup [supported] Install the desktop app, ensure a provider CLI is authenticated, choose a project and agent; desktop auto-starts its daemon. Sources: paseo:doc-index, paseo:doc-why.
  • No git [supported] A project can be any directory; Local isolation uses the directory as is. Sources: paseo:doc-workspaces.
  • Local git without remote [partial] Worktree branch-off uses a base ref such as origin/main in docs; behavior without any remote was not documented. Sources: paseo:doc-worktrees.
  • Hosted git [partial] GitHub via gh for PR-aware worktrees; changelog records GitLab, Gitea, Forgejo and Codeberg PR support. Sources: paseo:doc-index, paseo:changelog.
  • Prerequisite guidance [supported] Docs state at least one provider CLI must be installed and gh is recommended; Linux sandbox and AppImage FUSE guidance; troubleshooting for PATH. Sources: paseo:doc-index, paseo:doc-troubleshooting.
  • Managed cloud setup [unknown] Docs describe agents running on user machines and hosted Hub dispatching to them; no statement either way on a Paseo-operated runtime, so absence is not asserted.
  • Byo vps onboarding [supported] Headless install (npm i -g @getpaseo/cli), Docker image, SSH and relay connection guides. Sources: paseo:doc-index, paseo:doc-docker, paseo:doc-connectivity.

Sources: paseo:doc-index, paseo:doc-why, paseo:doc-workspaces, paseo:doc-worktrees, paseo:changelog, paseo:doc-troubleshooting, paseo:doc-docker, paseo:doc-connectivity

Agent cross-checked partial

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.

Scope
Surfaces: 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) · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-10-09 (44 days old)
Agent cross-check
2026-10-09
  • MCP tool injection is off by default; stability or versioning guarantees were not found; Hub API only covers triggers, projects and daemons.
8 atomic answers
  • Cli [supported] CLI covers agents, workspaces, terminals, scripts, schedules, permissions, plugins, daemon and Hub; JSON/YAML output. Sources: paseo:doc-cli.
  • Api [supported] Hub public API with OpenAPI 3.1 and organization API keys; daemon speaks a WebSocket protocol used by the SDK. Sources: paseo:doc-hub-api, paseo:doc-sdk.
  • Sdk [supported] @getpaseo/client TypeScript SDK creates agents, awaits finish and sends follow-ups. Sources: paseo:doc-sdk.
  • Mcp server [supported] Daemon MCP server on by default; injection into agents opt-in with per-provider tool policy. Sources: paseo:doc-mcp, paseo:orchestration.
  • Webhooks [partial] Hub ingests GitHub and Slack webhooks and a Discord gateway to start agents; Paseo does not document outbound webhooks. Sources: paseo:doc-hub, paseo:doc-hub-concepts.
  • Operations [supported] MCP and CLI create/prompt/cancel/kill/archive agents, manage workspaces, terminals, scripts, schedules and answer permissions; Hub API validates/installs configuration and dispatches manual triggers. Sources: paseo:doc-mcp, paseo:doc-hub-api.
  • Authentication [supported] Daemon password (Bearer), E2E pairing, semantic principal permissions; Hub scoped API keys and CLI login. Sources: paseo:doc-security, paseo:doc-permissions, paseo:doc-hub-api.
  • Stability [unknown] Stability: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.

Sources: paseo:doc-cli, paseo:doc-hub-api, paseo:doc-sdk, paseo:doc-mcp, paseo:orchestration, paseo:doc-hub, paseo:doc-hub-concepts, paseo:doc-security, paseo:doc-permissions

Agent cross-checked partial

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.

Scope
Surfaces: Paseo daemon and APIs · Version: v0.11.1 release (tag ab10a6694); sources read at main d0bc188a5 (eight later commits) · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-10-09 (44 days old)
Agent cross-check
2026-11-07
  • MCP client behavior is largely each provider's; permission scope of plugins beyond the trusted-local model was not documented.
7 atomic answers
  • Mcp client [partial] Paseo runs installed agents with the user's MCP servers; for Hub runs, named-agent options and MCP servers for OMP schedules are configurable. No Paseo MCP-client manager documented. Sources: paseo:doc-why, paseo:changelog.
  • Plugins [supported] Plugin SDK with registry install, screens, panels, commands, providers and daemon RPC; community directory exists. Sources: paseo:doc-plugins, paseo:changelog.
  • Custom tools [supported] Plugins add slash commands and daemon-side RPCs; skills installable via npx skills add. Sources: paseo:doc-plugins, paseo:doc-skills.
  • Instructions import [partial] Agents keep their own instruction files and skills; Paseo installs its orchestration skills but documents no import of other tools' instructions. Sources: paseo:doc-why, paseo:doc-skills.
  • Authentication [partial] Plugin acquisition supports private-registry credentials; installed plugins are trusted local code, while agent MCP authentication remains configured in the underlying provider. Sources: paseo:gap07-plugin-trust, paseo:paseo-custom-providers-tag-nov07.
  • Permission scope [partial] Plugin update shows a proposed npm or Git revision and asks for approval (--yes approves without a prompt); installing a plugin means trusting its codebase. Plugins are trusted, unsandboxed code gated by a per-daemon Enable plugins switch. Sources: paseo:doc-plugins.
  • Integration owner [partial] Paseo owns its plugin runtime and provider adapters; each external CLI retains its own MCP servers, credentials and configuration. Sources: paseo:gap07-plugin-trust, paseo:doc-providers-nov07.

Sources: paseo:doc-why, paseo:changelog, paseo:doc-plugins, paseo:doc-skills, paseo:gap07-plugin-trust, paseo:paseo-custom-providers-tag-nov07, paseo:doc-providers-nov07

Agent cross-checked partial

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

Scope
Surfaces: Paseo desktop, Paseo mobile, Paseo web · Version: v0.11.1 release (tag ab10a6694); sources read at main d0bc188a5 (eight later commits) · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-10-09 (44 days old)
Agent cross-check
2026-10-09
  • Package manifests establish the frameworks, not their behavior; whether web, mobile and desktop share all screens was not verified.
4 atomic answers

Sources: paseo:desktop-package, paseo:mobile-package, paseo:website, paseo:doc-plugins

Planning and context

Agent cross-checked partial

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.

Scope
Surfaces: Paseo Hub, Paseo daemon and APIs · Version: v0.11.1 release (tag ab10a6694); sources read at main d0bc188a5 (eight later commits) · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-10-09 (44 days old)
Agent cross-check
2026-10-09
  • Issue import or tracker sync is not established. Hub docs describe event-to-run dispatch.
9 atomic answers
  • Local creation [partial] Tasks are agent sessions in workspaces; no separate task object documented. Sources: paseo:doc-workspaces.
  • Prompt intake [supported] Prompts start agents from app, CLI, SDK, schedules and MCP. Sources: paseo:doc-cli, paseo:doc-sdk.
  • External import [unknown] Hub docs describe event-to-run dispatch; no issue import or tracker sync is described, which is not an explicit restriction.
  • Chat git triggers [supported] Hub triggers start workflows from GitHub issue/PR comments, Slack mentions and Discord mentions with a from_users allowlist. Sources: paseo:doc-hub, paseo:doc-hub-concepts.
  • Authoritative tracker [unknown] Authoritative tracker: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Stable ids [unknown] Stable ids: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Sync [unknown] Sync: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Supported edits [unknown] Supported edits: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • External roundtrips [unknown] External roundtrips: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.

Sources: paseo:doc-workspaces, paseo:doc-cli, paseo:doc-sdk, paseo:doc-hub, paseo:doc-hub-concepts

Agent cross-checked partial

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.

Scope
Surfaces: 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: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-10-09 (44 days old)
Agent cross-check
2026-10-09
  • Plan mode is a provider/session setting; no plan document store was found.
7 atomic answers
  • Plans [partial] CLI documents a plan agent mode; no persistent plan artifact documented. Sources: paseo:doc-cli.
  • Acceptance criteria [unknown] Acceptance criteria: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Editors [unknown] Editors: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Revisions [unknown] Revisions: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Amendment [unknown] Amendment: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Restart persistence [supported] Agent records, timelines and workspace links persist and closed agents resume under the same ID. Sources: paseo:doc-lifecycle.

Sources: paseo:doc-cli, paseo:doc-lifecycle

Agent cross-checked partial

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

Scope
Surfaces: Paseo daemon and APIs, Paseo Hub · Version: v0.11.1 release (tag ab10a6694) docs at d0bc188a5; Hub workflows doc at v0.15.3 (d91ae138cb931447635e94296023414a58bedcc5) · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-10-09 (44 days old)
Agent cross-check
2026-11-10
  • Parentage is agent-to-agent, not a task hierarchy with dependencies.
9 atomic answers
  • Epics [unknown] Epics: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Hierarchy [partial] Subagents have a parent and appear in a Subagents track; detach makes one top-level. Sources: paseo:workflows, paseo:doc-lifecycle.
  • Blockers [partial] Hub workflow steps can depend on a prior step output and condition; task/epic blockers are not established. Sources: paseo:gap07-workflow-order.
  • Readiness [partial] A false step condition skips it; later steps can read only prior outputs, within one configured workflow. Sources: paseo:gap07-workflow-order.
  • Enforcement [partial] Step order and max_runtime/idle_timeout are enforced by Hub; a timeout fails the run and stops later steps. Arbitrary issue dependency enforcement is not established. Sources: paseo:gap07-workflow-order.
  • State propagation [unknown] State propagation: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Task to epic [unknown] Task to epic: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Identity retention [supported] Agents retain Paseo agent ID through close and resume. Sources: paseo:doc-lifecycle.
  • Workflow constraints [partial] Hub requires authored trigger/ordered-step files and complete named agents/environments; agents outside Hub can coordinate conversationally without that workflow. Sources: paseo:gap07-workflow-order, paseo:orchestration-nov07.

Sources: paseo:workflows, paseo:doc-lifecycle, paseo:gap07-workflow-order, paseo:orchestration-nov07

Agent cross-checked partial

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.

Scope
Surfaces: Paseo daemon and APIs · Version: v0.11.1 release (tag ab10a6694); sources read at main d0bc188a5 (eight later commits) · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-10-09 (44 days old)
Agent cross-check
2026-10-09
  • Memory scope, provenance and deletion semantics belong to the underlying provider CLI.
10 atomic answers
  • Instructions [partial] Agents run in the user's environment with their own instruction files; profiles carry delegation notes. Sources: paseo:doc-why, paseo:doc-profiles.
  • Skills [supported] Orchestration skills (/paseo, handoff, committee, advisor) installable per host. Sources: paseo:doc-skills.
  • Project docs [unknown] Project docs: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Memory [unknown] Memory: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Scope [unknown] Scope: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Provenance [unknown] Provenance: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Correction [unknown] Correction: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Deletion [unknown] Deletion: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Freshness [unknown] Freshness: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Takeover continuity [partial] /paseo-handoff transfers a task and context to another agent. Sources: paseo:doc-skills.

Sources: paseo:doc-why, paseo:doc-profiles, paseo:doc-skills

Agent cross-checked partial

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

Scope
Surfaces: Paseo desktop, Paseo daemon and APIs · Version: v0.11.1 release (tag ab10a6694); sources read at main d0bc188a5 (eight later commits) · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-10-09 (44 days old)
Agent cross-check
2026-10-09
  • Code search quality, indexing and citations are provider behavior.
10 atomic answers
  • Indexing [unknown] Indexing: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • External knowledge [unknown] External knowledge: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Multimodal inputs [supported] CLI send accepts images; Antigravity gets image file references; browser tools capture screenshots. Sources: paseo:doc-cli, paseo:doc-providers, paseo:doc-parallel.
  • Freshness [unknown] Freshness: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Access scope [unknown] Access scope: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Api retrieval [unknown] Api retrieval: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Citations [unknown] Citations: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Conflict detection [unknown] Conflict detection: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Review enforcement [unknown] Review enforcement: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.

Sources: paseo:doc-cli, paseo:doc-providers, paseo:doc-parallel

Sourced partial

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.

Scope
Surfaces: 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 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
Not separately cross-checked
  • 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.
17 atomic answers
  • Create [unsupported] No native issue-create action is wired into the daemon, app, CLI or Hub. Sources: paseo:gaps-native-tasks.
  • Edit [unknown] Edit: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Discuss [unknown] Discuss: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Prioritize [unknown] Prioritize: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Label [unknown] Label: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Assign [unknown] Assign: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Filter [unknown] Filter: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Archive [unknown] Archive: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Reopen [unknown] Reopen: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Project epic views [unknown] Project epic views: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Idea parking [unknown] Idea parking: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Explicit dispatch [unknown] Explicit dispatch: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Task session separation [unsupported] The standalone task-store library has no product entrypoint in the inspected release; external trackers remain separate. Sources: paseo:gaps-native-tasks.
  • Metadata [unknown] Metadata: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Durable states [unsupported] Durable state in the accessible product belongs to agent workspaces or workflow runs, not independent native issues. Sources: paseo:gaps-native-tasks.
  • External tracker requirement [unknown] External tracker requirement: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.

Sources: paseo:gaps-native-tasks

No sourced public finding not-published

No publishable sourced finding is available for this criterion. This does not mean the product lacks the capability.

No sourced public finding not-published

No publishable sourced finding is available for this criterion. This does not mean the product lacks the capability.

Coordination and automation

COORD-01

Parallel work

Agent cross-checked partial

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

Scope
Surfaces: 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) · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-10-09 (44 days old)
Agent cross-check
2026-10-09
  • No concurrency quota or observed concurrency measurement documented; research workers in one workspace share files.
5 atomic answers
  • Concurrent sessions [supported] A workspace can run multiple agent sessions, terminals and browsers at once. Sources: paseo:doc-workspaces.
  • Concurrent tasks [supported] Parallel-development guide runs agents in separate worktree workspaces concurrently. Sources: paseo:doc-parallel, paseo:workflows.
  • Quotas [unknown] Quotas: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Observed concurrency [unknown] Observed concurrency: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Status visibility [partial] Sidebar workspaces show activity/attention; Subagents track shows delegated workers; paseo ls lists agents. Sources: paseo:workflows, paseo:doc-cli, paseo:changelog.

Sources: paseo:doc-workspaces, paseo:doc-parallel, paseo:workflows, paseo:doc-cli, paseo:changelog

Agent cross-checked partial

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

Scope
Surfaces: Paseo daemon and APIs · Version: v0.11.1 release (tag ab10a6694); sources read at main d0bc188a5 (eight later commits) · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-10-09 (44 days old)
Agent cross-check
2026-10-09
  • Hub routes events by trigger filters to a named daemon, not by ownership.
7 atomic answers
  • Human assignment [unknown] Human assignment: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Agent assignment [unknown] Agent assignment: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Claims [unknown] Claims: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Queues [unknown] Queues: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Routing [partial] Hub triggers route events to environments and named agents via filters; MCP profiles guide which agent an orchestrator picks. Sources: paseo:doc-hub-concepts, paseo:doc-profiles.
  • Duplicate prevention [unknown] Duplicate prevention: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Ownership enforcement [unknown] Ownership enforcement: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.

Sources: paseo:doc-hub-concepts, paseo:doc-profiles

Agent cross-checked partial

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.

Scope
Surfaces: 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) · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-10-09 (44 days old)
Agent cross-check
2026-10-09
  • Paseo tool injection is off by default; Antigravity lacks Paseo tools; native provider subagents are read-only timelines.
  • No hands-on delegation scenario run.
12 atomic answers
  • Roles [partial] Agent profiles carry When-to-use notes; roles are conventions rather than enforced. Sources: paseo:doc-profiles.
  • Model harness effort [supported] create_agent takes provider/model; profiles store thinking level and mode. Sources: paseo:doc-mcp, paseo:doc-profiles.
  • Messages [supported] send_agent_prompt and paseo send address agents by ID, including across workspaces on a host. Sources: paseo:workflows, paseo:doc-cli.
  • Results return [supported] Parent receives a notification when a worker finishes; paseo wait and get_agent_activity collect results; --output-schema yields structured output. Sources: paseo:orchestration, paseo:doc-cli, paseo:doc-mcp.
  • Cross harness [supported] Workers can use a different provider than the parent. Sources: paseo:orchestration.
  • Orchestration owner [supported] Parentage records which agent owns delegated work. Sources: paseo:doc-mcp.
  • Activation [supported] Settings > Agents > Enable Paseo tools, off by default; CLI route needs no injection. Sources: paseo:orchestration.
  • Authentication [partial] MCP and CLI act with the daemon's access; per-provider tool policy is explicitly not a security boundary. Sources: paseo:doc-mcp.
  • Live progress [supported] Subagents track and attach/logs follow worker output. Sources: paseo:orchestration, paseo:doc-cli.
  • Retained results [supported] Subagent conversations persist as sessions; closed agents resume. Sources: paseo:workflows, paseo:doc-lifecycle.
  • Followup [supported] Workers continue in their existing conversation after follow-up prompts. Sources: paseo:workflows.
  • Invocation [supported] Natural-language request, MCP tools, CLI or skills. Sources: paseo:orchestration, paseo:doc-skills.

Sources: paseo:doc-profiles, paseo:doc-mcp, paseo:workflows, paseo:doc-cli, paseo:orchestration, paseo:doc-lifecycle, paseo:doc-skills

Agent cross-checked partial

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.

Scope
Surfaces: 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) · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-10-09 (44 days old)
Agent cross-check
2026-10-09
  • 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.
8 atomic answers
  • Schedules [supported] Cron schedules with timezone, run-now, pause/resume/run-once. Sources: paseo:doc-schedules, paseo:doc-schedules-cli.
  • Events [supported] Hub triggers from GitHub, Slack, Discord and manual API dispatch. Sources: paseo:doc-hub-concepts.
  • Recurring tasks [supported] Schedules and heartbeats are recurring. Sources: paseo:doc-schedules.
  • Completion conditions [partial] Schedules carry --max-runs and --expires-in; heartbeats can expire; Hub steps require agents to call hub.finish_execution. Sources: paseo:doc-schedules-cli, paseo:workflows, paseo:doc-hub-activity.
  • Scheduler location [supported] Schedules are managed by the daemon on the user's host; Hub holds triggers and dispatches to daemons. Sources: paseo:doc-schedules, paseo:doc-hub-daemons.
  • Overlaps [unknown] Overlaps: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Retries [unsupported] Hub docs say a dispatch that fails, for example because the daemon is offline, is not retried or queued and must be triggered again. Hub does resend the same create intent with the same execution ID after a lost response or daemon restart. Sources: paseo:doc-hub-activity, paseo:doc-hub-faq.
  • Client independence [partial] The daemon manages schedules and heartbeats and keeps running agents without a connected client; the schedule docs do not state no-client behavior explicitly. Sources: paseo:doc-why, paseo:doc-schedules.

Sources: paseo:doc-schedules, paseo:doc-schedules-cli, paseo:doc-hub-concepts, paseo:workflows, paseo:doc-hub-activity, paseo:doc-hub-daemons, paseo:doc-hub-faq

Agent cross-checked partial

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.

Scope
Surfaces: 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) · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-10-09 (44 days old)
Agent cross-check
2026-10-09
  • Pause/resume is provider-dependent; steering absent for Antigravity; notification channels not fully documented.
10 atomic answers
  • Pause [unknown] Pause: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Stop [supported] cancel_agent aborts the current run, kill_agent terminates; paseo stop. Sources: paseo:doc-mcp, paseo:doc-cli.
  • Resume [supported] Closed agents resume under the same ID. Sources: paseo:doc-lifecycle.
  • Steer [partial] Follow-up prompts to a running worker; mid-turn steering added for OMP; Antigravity steering unavailable. Sources: paseo:workflows, paseo:changelog, paseo:doc-providers.
  • Notifications [partial] Parents are notified of child completion and permission requests; push notifications recorded in changelog. Sources: paseo:orchestration, paseo:doc-lifecycle, paseo:changelog.
  • Pending decisions [supported] list_pending_permissions / respond_to_permission and paseo permit ls/allow/deny. Sources: paseo:doc-mcp, paseo:doc-cli.
  • Escalation [unknown] Escalation: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Visible errors [partial] Agent states include error; runtime death between turns is reported as a turn failure for Claude and OMP. Sources: paseo:doc-lifecycle.
  • Chat terminal parity [unknown] Chat terminal parity: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Retained history [supported] Timelines persist and paseo logs shows them. Sources: paseo:doc-lifecycle, paseo:doc-cli.

Sources: paseo:doc-mcp, paseo:doc-cli, paseo:doc-lifecycle, paseo:workflows, paseo:changelog, paseo:doc-providers, paseo:orchestration

Agent cross-checked partial

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

Scope
Surfaces: Paseo desktop · Version: v0.11.1 release (tag ab10a6694); sources read at main d0bc188a5 (eight later commits) · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-10-09 (44 days old)
Agent cross-check
2026-10-09
  • Documentation and source-level pass of Paseo v0.11.1; no hands-on scenario was run and unknown sub-questions remain unknown.
8 atomic answers
  • Fleet fixture [unknown] Fleet fixture: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Parent child [partial] Subagents track groups workers under their parent. Sources: paseo:workflows.
  • Dependencies [unknown] Dependencies: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Attention [unknown] Attention: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • History [unknown] History: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Workload [unknown] Workload: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Navigation errors [unknown] Navigation errors: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Fixture mode [unknown] Fixture mode: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.

Sources: paseo:workflows, paseo:doc-workspaces

Agent cross-checked partial

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

Scope
Surfaces: Paseo desktop, Paseo daemon and APIs · Version: v0.11.1 release (tag ab10a6694); sources read at main d0bc188a5 (eight later commits) · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-10-09 (44 days old)
Agent cross-check
2026-10-09
  • Documentation and source-level pass of Paseo v0.11.1; no hands-on scenario was run and unknown sub-questions remain unknown.
10 atomic answers
  • Quick task [supported] A single prompt starts an agent from app, CLI or SDK. Sources: paseo:doc-cli, paseo:doc-sdk.
  • Growing epic [unknown] Growing epic: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Presets [supported] Agent profiles save provider, model, mode and thinking level. Sources: paseo:doc-profiles.
  • Natural language [supported] Orchestration can be requested in plain language through the MCP route once Paseo tools are enabled, or through the CLI route without tool injection (orchestration docs, tag ab10a6694). Sources: paseo:orchestration.
  • Agent configuration [supported] Profiles and provider options per agent. Sources: paseo:doc-profiles.
  • In run changes [unknown] In run changes: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Live roles [unknown] Live roles: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Retained relationships [unknown] Retained relationships: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Discoverability [partial] The MCP route needs Enable Paseo tools, which is off by default. The CLI route needs no tool injection. Orchestration skills are optional reusable workflows (orchestration docs, tag ab10a6694). Sources: paseo:orchestration, paseo:doc-skills, paseo:paseo-orchestration-tag.
  • Auth friction [unknown] Auth friction: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.

Sources: paseo:doc-cli, paseo:doc-sdk, paseo:doc-profiles, paseo:orchestration, paseo:doc-skills, paseo:paseo-orchestration-tag

Execution and reliability

Sourced partial

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.

Scope
Surfaces: 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 · Plan: Not specified · OS: Not specified · Execution modes: local, user-remote, self-hosted · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
Not separately cross-checked
  • Documentation and pinned source inspection only; no hands-on scenario was run.
  • Other atomic questions remain unestablished: resources, region, expiry.
12 atomic answers
  • Local [supported] The desktop app starts/manages a local daemon and agents use files/tools on that machine. Sources: paseo:gaps-host-architecture-current.
  • Byo remote [supported] The guide deliberately supports running the environment on a server and remote SSH/Tailscale client attachment. Sources: paseo:gaps-host-architecture-current, paseo:gaps-remote-transport-current.
  • Self hosted [supported] npm CLI, Docker image and daemon-served web UI. Sources: paseo:doc-index, paseo:doc-docker, paseo:doc-web-ui.
  • Managed cloud [unsupported] The current Hub offering executes agents on connected user daemons and nowhere else. Sources: paseo:gaps-execution-hosts.
  • Hybrid [supported] One client can connect to several hosts; CLI --host targets remote daemons. Sources: paseo:doc-connectivity, paseo:workflows.
  • Provisioning [partial] User provisions machines; a community project provisions per-developer GCP devboxes. Sources: paseo:doc-community.
  • Payer [supported] User pays their machines and provider plans; Paseo app is free. Sources: paseo:website, paseo:doc-claude-code.
  • Resources [unknown] Resources: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Region [unknown] Region: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Expiry [unknown] Expiry: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Client disconnect [supported] The daemon owns running agents/workspaces independently of its thin clients; the separately hosted daemon must stay running. Sources: paseo:gaps-host-architecture-current, paseo:gaps-remote-transport-current.
  • Other device continuation [supported] Another device can connect to the same daemon. Sources: paseo:doc-why.

Sources: paseo:doc-index, paseo:doc-security, paseo:doc-connectivity, paseo:doc-docker, paseo:doc-web-ui, paseo:workflows, paseo:doc-community, paseo:website, paseo:doc-claude-code, paseo:doc-why, paseo:gaps-execution-hosts, paseo:gaps-host-architecture-current, paseo:gaps-remote-transport-current

Agent cross-checked partial

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.

Scope
Surfaces: Paseo desktop, Paseo daemon and APIs, Paseo Hub · Version: v0.11.1 release (tag ab10a6694); sources read at main d0bc188a5 (eight later commits) · Plan: Not specified · OS: Not specified · Execution modes: local, worktree · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-10-09 (44 days old)
Agent cross-check
2026-11-10
  • 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.
12 atomic answers
  • Checkout [supported] Local isolation uses an existing directory. Sources: paseo:doc-workspaces.
  • Branch [supported] Worktree workspaces get a branch (branch-off, checkout-branch, checkout-pr). Sources: paseo:doc-worktrees.
  • Worktree [supported] Managed git worktrees per workspace with setup/teardown hooks. Sources: paseo:doc-worktrees.
  • Container [partial] 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. Sources: paseo:gap07-docker.
  • Vm [partial] Hub recommends an operator-supplied VM when stronger host isolation is needed; Paseo does not provision a VM for each task. Sources: paseo:gap07-host-isolation.
  • Os sandbox [partial] Sandbox settings are the provider's own (Codex sandbox_mode, Claude sandbox); Paseo recommends a dedicated OS user, container or VM when stronger isolation is needed. Sources: paseo:doc-hub-security.
  • Filesystem [partial] Worktrees separate files; agents in one workspace share its directory; Docker mounts define reachable paths. Sources: paseo:doc-workspaces, paseo:doc-security.
  • Process [partial] Services get per-worktree ports; processes still share machine ports unless configured. Sources: paseo:doc-worktrees, paseo:doc-parallel.
  • Network [partial] Hub carries the selected provider native network policy, such as Codex network_access false; OS/network isolation remains the operator responsibility. Sources: paseo:gap07-host-isolation.
  • Secrets [partial] Provider credentials stay in the user's home; Docker /home/paseo can contain credentials; Hub steps get tokens only via explicit blocks. Sources: paseo:doc-security, paseo:doc-hub-github.
  • Code separation [partial] Docker mounts bound reachable repositories and credentials; all agents in that daemon share the mounted environment unless the operator isolates hosts. Sources: paseo:gap07-docker.
  • Security boundary [unsupported] Hub security docs state Hub does not sandbox the provider process; MCP tool policy is not a security boundary. Sources: paseo:doc-hub-security, paseo:doc-mcp.

Sources: paseo:doc-workspaces, paseo:doc-worktrees, paseo:doc-docker, paseo:doc-hub-security, paseo:doc-security, paseo:doc-parallel, paseo:doc-hub-github, paseo:doc-mcp, paseo:gap07-host-isolation, paseo:gap07-docker

Agent cross-checked partial

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.

Scope
Surfaces: 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 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-10-09 (44 days old)
Agent cross-check
2026-11-10
  • 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).
12 atomic answers
  • Client disconnect [supported] Agents continue under the daemon without clients. Sources: paseo:doc-why.
  • Worker crash [partial] A provider runtime dying between turns can look idle until reported; Claude and OMP report such exits as turn failures; OMP relaunches from its session file. Sources: paseo:doc-lifecycle.
  • Service restart [partial] Optional agents.resumeOnStartup reopens running agents after graceful shutdown or crash using their saved provider conversation/settings and sends a configurable continuation. Default is off; idle/initializing and Hub executions follow separate lifecycle. Sources: paseo:gap07-lifecycle-recovery.
  • Expiry [partial] Resumable idle processes are released after one hour, with provider safety vetoes and host-wide disable setting; next prompt resumes the retained session. This is process cleanup, not deletion of the conversation. Sources: paseo:gap07-lifecycle-recovery.
  • Transcript reload [partial] Timelines persist; Antigravity transcript starts fresh after daemon restart; changelog fixed Claude history after restart in some cases. Sources: paseo:doc-lifecycle, paseo:doc-providers, paseo:changelog.
  • Process reconnect [partial] Closed runtimes are replaced by resuming their durable provider conversation under the same Paseo ID; live process attachment across replacement is not promised. Sources: paseo:gap07-lifecycle-recovery.
  • Task resume [supported] Closed agents resume the durable provider session under the same Paseo ID. Sources: paseo:doc-lifecycle.
  • State reconstruction [partial] Reopen retains identity, timeline, workspace, labels, usage, attention and parentage; explicit creation environment overrides are reapplied. This does not restore arbitrary detached process state. Sources: paseo:gap07-lifecycle-recovery.
  • Context loss [partial] Provider resume owns conversation restoration. A provider crash can lose background shells/watches; queued in-memory prompts can be lost, and best-effort startup continuation may be lost or repeated. Sources: paseo:gap07-lifecycle-recovery.
  • Duplicate actions [supported] Hub dispatch uses a stable execution ID so the daemon returns the existing agent instead of rerunning. Sources: paseo:doc-hub-daemons.
  • Manual repair [partial] Failed reopen is logged with no recovery retry loop. Once old runtime closure succeeds a failed resume remains closed and retryable; ambiguous close failures block replacement. Sources: paseo:gap07-lifecycle-recovery.
  • Multi day continuity [unknown] Multi day continuity: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.

Sources: paseo:doc-why, paseo:doc-lifecycle, paseo:doc-troubleshooting, paseo:doc-hub-daemons, paseo:doc-providers, paseo:changelog, paseo:gap07-lifecycle-recovery

Agent cross-checked partial

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

Scope
Surfaces: Paseo desktop, Paseo daemon and APIs · Version: v0.11.1 release (tag ab10a6694); sources read at main d0bc188a5 (eight later commits) · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-10-09 (44 days old)
Agent cross-check
2026-10-09
  • Setup is user-authored shell; worktrees start without dependencies or ignored files such as .env.
10 atomic answers
  • Dependencies [partial] worktree.setup in paseo.json runs install commands after worktree creation. Sources: paseo:doc-worktrees.
  • Caches [unknown] Caches: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Snapshots [unknown] Snapshots: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Services [supported] Services are supervised with terminals and health metadata via UI, CLI and MCP. Sources: paseo:doc-worktrees, paseo:doc-mcp.
  • Ports [supported] Per-service PASEO_PORT, configurable ranges or an external port script, plus deterministic proxy hostnames. Sources: paseo:doc-worktrees.
  • Secrets [partial] Setup can copy .env from $PASEO_SOURCE_CHECKOUT_PATH. Sources: paseo:doc-worktrees.
  • Duplicate installs [unknown] Duplicate installs: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Collisions [partial] Distinct ports per worktree; docs warn plain processes share machine ports. Sources: paseo:doc-worktrees, paseo:doc-parallel.
  • Remote setup [partial] paseo.json is read from the committed base branch on the daemon host. Sources: paseo:doc-worktrees.
  • Automatic repair [unknown] Automatic repair: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.

Sources: paseo:doc-worktrees, paseo:doc-mcp, paseo:doc-parallel

Agent cross-checked partial

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.

Scope
Surfaces: Paseo daemon and APIs, Paseo Hub · Version: v0.11.1 release (tag ab10a6694); sources read at main d0bc188a5 (eight later commits) · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-10-09 (44 days old)
Agent cross-check
2026-10-09
  • Documentation and source-level pass of Paseo v0.11.1; no hands-on scenario was run and unknown sub-questions remain unknown.
8 atomic answers
  • Time limits [supported] Schedules have --expires-in; heartbeats can expire; Hub steps and workflows declare max_runtime and idle_timeout. Sources: paseo:doc-schedules-cli, paseo:workflows, paseo:doc-hub-activity, paseo:doc-hub-github.
  • Turn limits [partial] Schedules carry --max-runs (runs, not turns). Sources: paseo:doc-schedules-cli.
  • Token limits [unknown] Token limits: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Spend limits [unknown] Spend limits: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Timeouts [unknown] Timeouts: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Retries [unsupported] Hub docs say a dispatch that fails, for example because the daemon is offline, is not retried or queued. Hub does resend the same create intent after a lost response or daemon restart. Sources: paseo:doc-hub-activity.
  • Provider failures [partial] Dispatch failures recorded in Activity with reasons such as daemon_not_connected. Sources: paseo:doc-hub-daemons, paseo:doc-hub-activity.
  • Enforcement [unknown] Enforcement: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.

Sources: paseo:doc-schedules-cli, paseo:workflows, paseo:doc-hub-activity, paseo:doc-hub-daemons, paseo:doc-hub-github

Agent cross-checked partial

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.

Scope
Surfaces: 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 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
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.
13 atomic answers
  • Logs [supported] paseo logs/attach for timelines; daemon.log and main.log files; schedule_logs. Sources: paseo:doc-cli-nov07, paseo:doc-troubleshooting-nov07, paseo:doc-mcp-nov07.
  • Traces [unknown] Traces: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Failure reasons [partial] Hub records bounded unrouted-event reasons and execution state; agent errors appear as an error state. Sources: paseo:doc-hub-activity-nov07, paseo:doc-lifecycle-nov07.
  • Usage export [partial] Usage dialog shows quota windows with Refresh; export not documented. Sources: paseo:changelog-nov07.
  • Task stats [unknown] Task stats: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Agent stats [unknown] Agent stats: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Project stats [unknown] Project stats: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Time stats [unknown] Time stats: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Failure status [supported] Agent states include error; schedules and Hub executions record run state. Sources: paseo:doc-lifecycle-nov07, paseo:doc-hub-activity-nov07.
  • Approval status [supported] Pending permissions listed across agents. Sources: paseo:doc-mcp-nov07.
  • Reconnect consistency [partial] Changelog records open chats kept subscribed across reconnects and a fix for subagents that finished while the app was disconnected; reconnect consistency beyond these entries is not documented. Sources: paseo:changelog-nov07.
  • Performance method [unknown] Performance method: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Responsiveness [unknown] Responsiveness: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.

Sources: paseo:doc-cli-nov07, paseo:doc-troubleshooting-nov07, paseo:doc-mcp-nov07, paseo:doc-hub-activity-nov07, paseo:doc-lifecycle-nov07, paseo:changelog-nov07

Agent cross-checked partial

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.

Scope
Surfaces: Paseo desktop, Paseo mobile · Version: v0.11.1 release (tag ab10a6694); sources read at main d0bc188a5 (eight later commits) · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-10-09 (44 days old)
Agent cross-check
2026-10-09
  • Usage view reflects account quota windows, not task cost.
14 atomic answers
  • Task cost [unknown] Task cost: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Session cost [unknown] No per-session cost figure found in Paseo docs or changelog.
  • Child cost [unknown] Child cost: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Epic cost [unknown] Epic cost: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Harness aggregation [unknown] Harness aggregation: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Billed vs estimated [unknown] Billed vs estimated: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Tokens [partial] Context window meter shows usage for an agent's account; token totals per task not documented. Sources: paseo:changelog.
  • Subscription allowance [partial] Usage dialog or sheet shows quota windows for Claude, ChatGPT, OpenCode Go and others the daemon can discover. Sources: paseo:changelog.
  • Provider reconciliation [unknown] Provider reconciliation: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Compute cost [unknown] Compute cost: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Refresh delay [unknown] Refresh delay: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Alerts [unknown] Alerts: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Export [unknown] Export: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Drilldown [unknown] Drilldown: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.

Sources: paseo:changelog

Agent cross-checked partial

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

Scope
Surfaces: Paseo daemon and APIs, Paseo Hub · Version: v0.11.1 release (tag ab10a6694); sources read at main d0bc188a5 (eight later commits) · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-10-09 (44 days old)
Agent cross-check
2026-10-09
  • Documentation and source-level pass of Paseo v0.11.1; no hands-on scenario was run and unknown sub-questions remain unknown.
12 atomic answers
  • Concurrency [unknown] Concurrency: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Queues [unsupported] Hub docs: events are not queued when a daemon is offline. Sources: paseo:doc-hub-daemons, paseo:doc-hub-activity.
  • Cpu ram [unknown] Cpu ram: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Backpressure [unknown] Backpressure: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Host awareness [unknown] Host awareness: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Check reuse [unknown] Check reuse: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Check deduplication [unknown] Check deduplication: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Bounded tests [unknown] Workspace scripts run named commands in supervised terminals (doc-worktrees). A bounded capacity test or queue was not documented, so bounded capacity is not established. Sources: paseo:doc-worktrees.
  • Cancellation [supported] Agents can be cancelled or killed. Sources: paseo:doc-mcp.
  • Fairness [unknown] Fairness: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Recovery [unknown] Recovery: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Shared limits [unknown] Shared limits: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.

Sources: paseo:doc-hub-daemons, paseo:doc-hub-activity, paseo:doc-worktrees, paseo:doc-mcp

Human collaboration and control

Sourced partial

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.

Scope
Surfaces: Paseo Hub, Paseo daemon and APIs · Version: Paseo v0.15.4 at 1c00b365c9e0b74c1580eba33d905d693125ae21; Hub source 61e51c56f8756e40c55a30982160ce000f2aa177; checked 2026-11-13 · Plan: Self-hosted early-development Paseo Hub; Slack trigger Agent continuity = Same conversation; explicit hub.execute grant · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
Not separately cross-checked
  • Documentation and pinned source inspection only; no hands-on scenario was run.
  • Other atomic questions remain unestablished: discussion, comments, presence, ordering, conflicts.
11 atomic answers
  • Visibility [partial] Hub gives one place for a team to see triggers, events and runs. Sources: paseo:doc-hub-nov07.
  • Discussion [unknown] Discussion: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Comments [unknown] Comments: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Presence [unknown] Presence: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Coprompting [supported] 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. Sources: paseo:gaps-hub-human-intake, paseo:gaps-hub-thread-continuity, paseo:gaps-hub-session-delivery, paseo:gaps-hub-message-contract.
  • Ordering [unknown] Ordering: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Conflicts [unknown] Conflicts: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Attribution [partial] Hub API operations retain API-key attribution in audit evidence; GitHub commits use the App bot identity. Sources: paseo:doc-hub-api-nov07, paseo:doc-hub-github-nov07.
  • Permissions [supported] The Slack trigger independently filters human authors, and the daemon owner explicitly grants Hub hub.execute authority. Sources: paseo:gaps-hub-human-intake, paseo:gaps-hub-message-contract.
  • Plan restrictions [supported] Hub Free: one seat; Pro: unlimited seats, invitations count as seats. Sources: paseo:hub-pricing-nov07, paseo:doc-hub-hosted-nov07.
  • Owner online [supported] The running self-hosted Hub and daemon deliver allowed Slack messages without a desktop-owner client connection. Sources: paseo:gaps-hub-session-delivery, paseo:gaps-hub-message-contract.

Sources: paseo:doc-hub-nov07, paseo:doc-hub-api-nov07, paseo:doc-hub-github-nov07, paseo:hub-pricing-nov07, paseo:doc-hub-hosted-nov07, paseo:gap07-principal-permissions, paseo:gaps-shared-prompts, paseo:gaps-hub-human-intake, paseo:gaps-hub-thread-continuity, paseo:gaps-hub-session-delivery, paseo:gaps-hub-message-contract, paseo:gaps-hub-public-preview

Sourced partial

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.

Scope
Surfaces: Paseo daemon and APIs, Paseo Hub · Version: Public Hub source commit 61e51c56f8756e40c55a30982160ce000f2aa177; inspected 2026-11-13 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
beta
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
Not separately cross-checked
  • Documentation and pinned source inspection only; no hands-on scenario was run.
  • Other atomic questions remain unestablished: project_roles, provisioning, plan_scope.
9 atomic answers
  • Organization roles [supported] Hub defines owner/admin/member roles and enforces separate member, owner and resource management capabilities. Sources: paseo:gaps-hub-roles.
  • Project roles [unknown] Project roles: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Task roles [partial] Daemon principals carry grants like workspace.read/write/manage. Sources: paseo:doc-permissions.
  • Membership [partial] Hub Pro allows invitations; pending invitations count as seats. Sources: paseo:hub-pricing.
  • Sso [unsupported] Hub enables email/password and organization membership without an enterprise SAML/OIDC SSO plugin. Sources: paseo:gaps-hub-auth.
  • Provisioning [unknown] Provisioning: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Unauthorized access [supported] Daemon password returns 401; relay needs handshake; Hub from_users allowlist is required. Sources: paseo:doc-security, paseo:doc-hub-concepts.
  • Revocation [supported] Daemons can be revoked from Hub; API keys are revocable; CLI login is revocable independently. Sources: paseo:doc-hub-daemons, paseo:doc-hub-api.
  • Plan scope [unknown] Plan scope: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.

Sources: paseo:doc-hub-concepts, paseo:doc-hub-api, paseo:doc-permissions, paseo:hub-pricing, paseo:doc-security, paseo:doc-hub-daemons, paseo:gaps-hub-roles, paseo:gaps-hub-auth, paseo:gaps-hub-public-preview

Agent cross-checked partial

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.

Scope
Surfaces: Paseo desktop, Paseo daemon and APIs, Paseo Hub · Version: v0.11.1 release (tag ab10a6694); sources read at main d0bc188a5 (eight later commits) · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-10-09 (44 days old)
Agent cross-check
2026-10-09
  • Antigravity always runs in Full access; Hub relies on provider-native permission modes and does not sandbox provider processes.
14 atomic answers
  • Command [partial] Provider modes (such as plan and bypass) set via paseo agent mode; approvals answered per request. Sources: paseo:doc-cli, paseo:doc-mcp.
  • Tool [unknown] Tool: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Network [unknown] Network: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Secret [unknown] Secret: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Delivery [supported] Permission requests surface in app, CLI and as parent notifications. Sources: paseo:doc-cli, paseo:doc-lifecycle.
  • Approver identity [unknown] Approver identity: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Lifetime [partial] Hub GitHub token duration up to 1h. Sources: paseo:doc-hub-github.
  • Allow [supported] respond_to_permission allow/deny; paseo permit allow. Sources: paseo:doc-mcp, paseo:doc-cli.
  • Deny [supported] paseo permit deny. Sources: paseo:doc-cli.
  • Revoke [unknown] Revoke: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Tunnels [unknown] Tunnels: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Defaults [partial] Antigravity is Full access only; Hub-run agents take approval behavior from their named-agent options, for example approval_policy: never in Hub docs examples. Sources: paseo:doc-providers, paseo:doc-hub-security.
  • Safer modes [partial] Provider-native read-only sandbox options can be set per named agent in Hub. Sources: paseo:doc-hub-security.
  • Enforcement [unknown] Enforcement: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.

Sources: paseo:doc-cli, paseo:doc-mcp, paseo:doc-lifecycle, paseo:doc-hub-github, paseo:doc-providers, paseo:doc-hub-security

Agent cross-checked partial

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

Scope
Surfaces: Paseo Hub, Paseo daemon and APIs · Version: v0.11.1 release (tag ab10a6694); sources read at main d0bc188a5 (eight later commits) · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-10-09 (44 days old)
Agent cross-check
2026-10-09
  • Documentation and source-level pass of Paseo v0.11.1; no hands-on scenario was run and unknown sub-questions remain unknown.
11 atomic answers
  • Actions [supported] Hub Activity lists routed events and execution state; unrouted events keep a bounded reason. Sources: paseo:doc-hub-activity.
  • Approvals [unknown] No audit log of approvals found.
  • Edits [unknown] Edits: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Discussion [unknown] Discussion: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Decisions [unknown] Decisions: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Cross user persistence [unknown] Cross user persistence: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Cross session persistence [supported] Agent timelines persist across sessions. Sources: paseo:doc-lifecycle.
  • Export [unknown] Export: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Mutability [unknown] Mutability: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Retention [unknown] Retention: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Integrity [unknown] Integrity: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.

Sources: paseo:doc-hub-activity, paseo:doc-lifecycle

Agent cross-checked partial

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.

Scope
Surfaces: Paseo desktop, Paseo mobile · Version: v0.11.1 release (tag ab10a6694); sources read at main d0bc188a5 (eight later commits) · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-10-09 (44 days old)
Agent cross-check
2026-10-09
  • Documentation and source-level pass of Paseo v0.11.1; no hands-on scenario was run and unknown sub-questions remain unknown.
13 atomic answers
  • Pending reviews [unknown] Pending reviews: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Change understanding [supported] Changes view shows diffs per workspace; PR status and check summaries with failure-first grouping appear in changelog. Sources: paseo:doc-parallel, paseo:changelog.
  • Evidence navigation [unknown] Evidence navigation: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Comments [partial] Corrections are sent to the workspace agent as prompts; inline review comments not documented. Sources: paseo:doc-parallel.
  • Request changes [unknown] Request changes: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Shipping guidance [unknown] Shipping guidance: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Effort [unknown] Effort: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Missed evidence [unknown] Missed evidence: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Keyboard [unknown] Keyboard: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Narrow screen [partial] Mobile app offers files, terminals and diffs. Sources: paseo:doc-why.
  • Context switching [supported] Workspaces and split panes switch between tasks. Sources: paseo:doc-parallel.
  • Roles [unknown] Roles: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Retained context [unknown] Retained context: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.

Sources: paseo:doc-parallel, paseo:changelog, paseo:doc-why

Agent cross-checked partial

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.

Scope
Surfaces: Paseo daemon and APIs · Version: v0.11.1 release (tag ab10a6694); sources read at main d0bc188a5 (eight later commits) · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-10-09 (44 days old)
Agent cross-check
2026-10-09
  • Documentation and source-level pass of Paseo v0.11.1; no hands-on scenario was run and unknown sub-questions remain unknown.
12 atomic answers
  • Ongoing takeover [unknown] Ongoing takeover: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Same task [unknown] Same task: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Session history [supported] Timelines persist on the daemon and are readable by any client with workspace.read. Sources: paseo:doc-lifecycle, paseo:doc-permissions.
  • Decisions [unknown] Decisions: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Artifacts [unknown] Artifacts: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Permissions [supported] Pairing invitations create principals with issuer-selected permissions. Sources: paseo:doc-permissions.
  • Runtime context [unknown] Runtime context: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Owner disconnect [unknown] Owner disconnect: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Ownership [unknown] Ownership: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Attribution [unknown] Attribution: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Context loss [unknown] Context loss: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Harness transfer [partial] /paseo-handoff skill transfers a task and context to another agent. Sources: paseo:doc-skills.

Sources: paseo:doc-lifecycle, paseo:doc-permissions, paseo:doc-skills

Verification and delivery

Agent cross-checked partial

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.

Scope
Surfaces: Paseo desktop · Version: v0.11.1 release (tag ab10a6694); sources read at main d0bc188a5 (eight later commits) · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-10-09 (44 days old)
Agent cross-check
2026-10-09
  • Documentation and source-level pass of Paseo v0.11.1; no hands-on scenario was run and unknown sub-questions remain unknown.
13 atomic answers
  • Diffs [supported] Changes tab shows workspace diffs. Sources: paseo:doc-parallel.
  • Documents [unknown] Documents: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Screenshots [partial] Browser automation can take screenshots on the desktop app. Sources: paseo:doc-parallel.
  • Recordings [unknown] Recordings: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Previews [supported] Built-in browser tabs and service proxy URLs preview workspace apps. Sources: paseo:doc-parallel, paseo:doc-worktrees.
  • Test outputs [unknown] Test outputs: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Reviewer outputs [unknown] Reviewer outputs: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Persistence [partial] Agent timelines persist; artifact retention not documented. Sources: paseo:doc-lifecycle.
  • Child findings [unknown] Child findings: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Prompt leakage [unknown] Prompt leakage: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.

Sources: paseo:doc-parallel, paseo:doc-worktrees, paseo:doc-lifecycle

Agent cross-checked partial

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.

Scope
Surfaces: Paseo desktop, Paseo daemon and APIs · Version: v0.11.1 release (tag ab10a6694); sources read at main d0bc188a5 (eight later commits) · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-10-09 (44 days old)
Agent cross-check
2026-10-09
  • Documentation and source-level pass of Paseo v0.11.1; no hands-on scenario was run and unknown sub-questions remain unknown.
11 atomic answers
  • Tests [partial] Scripts like test and lint can be defined and run on demand. Sources: paseo:doc-worktrees.
  • Lint [partial] Same script mechanism. Sources: paseo:doc-worktrees.
  • Types [unknown] Types: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Ci [partial] PR check summaries appear in the PR panel; build babysitting via schedules. Sources: paseo:changelog, paseo:doc-schedules.
  • Independent review [supported] Implement-then-review recipe launches an independent reviewer agent in the same workspace. Sources: paseo:workflows.
  • Spec checks [unknown] Spec checks: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Required checks [unknown] Required checks: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Failure blocking [unknown] Failure blocking: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Requirement conflicts [unknown] Requirement conflicts: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Configured policy [unknown] Configured policy: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Enforced policy [unknown] Enforced policy: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.

Sources: paseo:doc-worktrees, paseo:changelog, paseo:doc-schedules, paseo:workflows

Agent cross-checked partial

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.

Scope
Surfaces: Paseo desktop, Paseo daemon and APIs · Version: v0.11.1 release (tag ab10a6694); sources read at main d0bc188a5 (eight later commits) · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-10-09 (44 days old)
Agent cross-check
2026-10-09
  • Commit and PR actions are done by the user or agent through normal git; no merge automation documented.
9 atomic answers
  • Branches [supported] Branch-off, checkout-branch and checkout-pr modes. Sources: paseo:doc-worktrees.
  • Worktrees [supported] Managed worktrees per workspace. Sources: paseo:doc-worktrees.
  • Commits [partial] Commit messages are generated for changes being committed; agent or user runs git. Sources: paseo:doc-metadata, paseo:doc-parallel.
  • Pull requests [supported] PR title and body drafted from the diff; PR workspaces and PR detection; the changelog records forge support beyond GitHub (GitLab, Gitea, Forgejo, Codeberg). Sources: paseo:doc-metadata, paseo:changelog.
  • Comments [unknown] Comments: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Ci response [partial] Check summaries in PR panel; schedules can babysit builds. Sources: paseo:changelog, paseo:doc-schedules.
  • Rebase [unknown] Rebase: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Conflicts [unknown] Conflicts: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Product state [partial] Workspace auto-archive after a merged PR appears in changelog fixes. Sources: paseo:changelog.

Sources: paseo:doc-worktrees, paseo:doc-metadata, paseo:doc-parallel, paseo:changelog, paseo:doc-schedules

Agent cross-checked partial

Merge and deployment authority are not documented by Paseo; Hub steps limit GitHub authority via declared repositories and permissions within the GitHub App installation.

Scope
Surfaces: Paseo Hub · Version: v0.11.1 release (tag ab10a6694); sources read at main d0bc188a5 (eight later commits) · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-10-09 (44 days old)
Agent cross-check
2026-10-09
  • Documentation and source-level pass of Paseo v0.11.1; no hands-on scenario was run and unknown sub-questions remain unknown.
6 atomic answers
  • Approve [unknown] Approve: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Merge [unknown] Merge: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Release [unknown] Release: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Deploy [unknown] Deploy: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Exact revision [unknown] Exact revision: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Authority enforcement [partial] Hub step github block bounds repositories and permissions (default contents: read, token up to 1h) within the App installation. Sources: paseo:doc-hub-github.

Sources: paseo:doc-hub-github

Agent cross-checked partial

Paseo documents PR links for workspaces; commit, build and deployment links, completion evidence and code rollback are not documented. Hub keeps the previous active configuration revision when a new one fails activation.

Scope
Surfaces: Paseo Hub · Version: v0.11.1 release (tag ab10a6694); sources read at main d0bc188a5 (eight later commits) · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-10-09 (44 days old)
Agent cross-check
2026-10-09
  • Documentation and source-level pass of Paseo v0.11.1; no hands-on scenario was run and unknown sub-questions remain unknown.
9 atomic answers
  • Delivery status [unknown] Delivery status: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Retained evidence [unknown] Retained evidence: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Rollback [unknown] Rollback: no explicit rollback action is documented for Hub configuration or code. Hub keeps the previous active revision when a new revision fails activation. Sources: paseo:doc-hub-concepts.
  • Revert [unknown] Revert: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Stale approval invalidation [unknown] Stale approval invalidation: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.

Sources: paseo:changelog, paseo:doc-hub-concepts

No sourced public finding not-published

No publishable sourced finding is available for this criterion. This does not mean the product lacks the capability.

Ownership, privacy and economics

Agent cross-checked partial

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.

Scope
Surfaces: Paseo desktop, Paseo daemon and APIs, Paseo Hub, Paseo CLI and TypeScript SDK · Version: v0.15.3 at d91ae138cb931447635e94296023414a58bedcc5 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
  • 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.
6 atomic answers

Sources: paseo:license-chk2-nov07, paseo:desktop-license-chk2-nov07, paseo:security-chk2-nov07, paseo:hub-selfhost-chk2-nov07, paseo:release-chk2-nov07

Agent cross-checked partial

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

Scope
Surfaces: Paseo daemon and APIs, Paseo Hub · Version: v0.11.1 release (tag ab10a6694); sources read at main d0bc188a5 (eight later commits) · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-10-09 (44 days old)
Agent cross-check
2026-10-09
  • Documentation and source-level pass of Paseo v0.11.1; no hands-on scenario was run and unknown sub-questions remain unknown.
8 atomic answers
  • Self hosting [supported] Daemon via desktop, npm or Docker; Hub via npx @getpaseo/hub with embedded or PostgreSQL storage. Sources: paseo:doc-index, paseo:doc-docker, paseo:doc-hub-selfhost.
  • Vendor dependencies [supported] Relay and Hub are optional; direct, SSH and Tailscale paths avoid them; hosted web app optional because the daemon can serve the UI. Sources: paseo:doc-connectivity, paseo:doc-web-ui, paseo:doc-hub-faq.
  • Export [unknown] Export: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Import [unknown] Import: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Formats [unknown] Formats: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Cancellation [unknown] Cancellation: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Account independence [supported] No Paseo account is required for the core app. Sources: paseo:doc-why.
  • History portability [unknown] History portability: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.

Sources: paseo:doc-index, paseo:doc-docker, paseo:doc-hub-selfhost, paseo:doc-connectivity, paseo:doc-web-ui, paseo:doc-hub-faq, paseo:doc-why

Agent cross-checked partial

Stable v0.15.3 states no telemetry, tracking or required Paseo account for the local app. Code and daemon state remain on the host, relay traffic is end-to-end encrypted, and provider authentication/data handling are separate. Hosted Hub retention and a telemetry disable control remain unestablished.

Scope
Surfaces: Paseo desktop, Paseo daemon and APIs, Paseo Hub · Version: Paseo v0.15.3 (d91ae138cb931447635e94296023414a58bedcc5) why.md; security, custom-provider and voice docs at v0.11.1 (ab10a6694) and d0bc188a5; homepage read 2026-11-07 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-10-09 (44 days old)
Agent cross-check
2026-11-17
  • The no-telemetry statement is vendor documentation; network behavior was not independently tested. Providers' own data handling is separate.
15 atomic answers
  • Code data [supported] Docs: code never leaves the machine; agents call their own APIs. Sources: paseo:doc-security, paseo:website.
  • Prompts [unknown] Prompts: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Credentials [partial] Paseo does not store provider login credentials on the normal path. Optional custom-provider env entries and speech provider keys are written to Paseo config (custom-providers and voice docs at tag ab10a6694). Hub credentials are separate and stored under PASEO_HOME. Sources: paseo:doc-security, paseo:paseo-custom-providers-tag, paseo:paseo-voice-tag.
  • Logs [partial] Logs stay local (daemon.log, main.log). Sources: paseo:doc-troubleshooting.
  • Artifacts [unknown] Artifacts: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Retention [unknown] Retention: the cited plugin documentation at v0.15.3 states no log or transcript retention limits; hosted Hub retention is not established.
  • Deletion [unknown] Deletion: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Training [unknown] Training: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Residency [unknown] Residency: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Subprocessors [unknown] Subprocessors: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Telemetry disclosure [supported] The stable v0.15.3 Why Paseo guide states no telemetry, tracking or required Paseo account for the local app. Hosted Hub and model-provider policies remain separate. Sources: paseo:why-tag-nov07.
  • Telemetry defaults [partial] The local app guide states no telemetry or tracking; no explicit telemetry disable control or consent behavior was established. Hosted Hub policy is separate. Sources: paseo:why-tag-nov07.
  • Telemetry controls [unsupported] No app telemetry exists so there is no disable control; the only analytics script is Plausible on the marketing website package. Sources: paseo:d80-why, paseo:d80-negtree.
  • Provider separation [supported] Provider CLIs handle their own authentication and data flows. Sources: paseo:doc-security.

Sources: paseo:doc-security, paseo:website, paseo:doc-troubleshooting, paseo:doc-why, paseo:why-tag, paseo:why-main, paseo:paseo-custom-providers-tag, paseo:paseo-voice-tag, paseo:why-tag-nov07, paseo:d80-why, paseo:d80-negtree

Agent cross-checked partial

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.

Scope
Surfaces: Paseo Hub · Version: Paseo v0.15.3 at d91ae138cb931447635e94296023414a58bedcc5; hosted Hub page reread 2026-11-07 · Plan: Hub Free / Pro; self-hosted · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
  • Currency is shown as $ without naming it; taxes, trial and overage terms not stated; prices read from the vendor pricing page.
12 atomic answers
  • Currency [partial] Price shown with $ symbol; currency not named. Sources: paseo:hub-pricing-nov07.
  • Interval [supported] Monthly. Sources: paseo:hub-pricing-nov07.
  • Seats [supported] Pro $15 per seat; Free 1 seat; trigger-only users do not count; invitations count. Sources: paseo:hub-pricing-nov07.
  • Seat minimum [unknown] Seat minimum: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Workspace fees [unknown] Workspace fees: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Included usage [supported] Free: 50 agent runs per month; Pro unlimited runs. Sources: paseo:hub-pricing-nov07, paseo:doc-hub-hosted-nov07.
  • Credits [unknown] Credits: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Trial [unknown] Trial: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Overages [unknown] Overages: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Taxes [unknown] Taxes: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Model cost [supported] Provider usage is billed by the provider plan or API account; Paseo adds no charge for Claude Code or Codex. Sources: paseo:doc-claude-code-nov07, paseo:doc-codex-nov07.
  • Compute cost [supported] Agents run on user machines; user bears compute. Sources: paseo:website-nov07, paseo:doc-hub-security-nov07.

Sources: paseo:hub-pricing-nov07, paseo:doc-hub-hosted-nov07, paseo:doc-claude-code-nov07, paseo:doc-codex-nov07, paseo:website-nov07, paseo:doc-hub-security-nov07

Agent cross-checked partial

Fixed hosted Hub examples: one Free seat $0 for 50 runs/month; two Pro seats $30/month; five $75/month. Local app is free; model and machine workload costs remain separate.

Scope
Surfaces: Paseo Hub · Version: Hosted Hub public offer reread 2026-11-07 · Plan: Free one-seat scenario versus Pro multi-seat; excludes model/compute · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
  • No workload, billing or authenticated client test was performed; unestablished details remain unknown.
11 atomic answers
  • One person [partial] Hub Free $0, one seat and 50 runs/month. Sources: paseo:hub-pricing-nov07.
  • Two people [partial] Two Pro seats at $15 each are $30/month; unlimited Hub runs. Sources: paseo:hub-pricing-nov07.
  • Five people [partial] Five Pro seats are $75/month; unlimited Hub runs. Sources: paseo:hub-pricing-nov07.
  • Task assumptions [unknown] Not established by the first-party sources reread November 7; no configured or authenticated scenario was tested.
  • Concurrency [unknown] Not established by the first-party sources reread November 7; no configured or authenticated scenario was tested.
  • Tokens [unknown] Not established by the first-party sources reread November 7; no configured or authenticated scenario was tested.
  • Compute hours [unknown] Not established by the first-party sources reread November 7; no configured or authenticated scenario was tested.
  • Fixed cost [partial] App/daemon/CLI/SDK free; hosted Hub Pro $15/seat/month. Pending invitations count as seats. Sources: paseo:hub-pricing-nov07.
  • Variable cost [partial] User provider accounts and execution machines are separate; no measured token/compute workload. Sources: paseo:doc-codex-nov07, paseo:doc-claude-code-nov07.
  • Included cost [unknown] Not established by the first-party sources reread November 7; no configured or authenticated scenario was tested.
  • Unknown cost [unknown] Not established by the first-party sources reread November 7; no configured or authenticated scenario was tested.

Sources: paseo:hub-pricing-nov07, paseo:doc-codex-nov07, paseo:doc-claude-code-nov07

Agent cross-checked partial

Current stable is v0.15.3 on November 6, with separate Beta channel and gradual desktop rollout. Hosted Hub still uses beta access language; support-response commitments remain unestablished.

Scope
Surfaces: Paseo desktop, Paseo daemon and APIs, Paseo Hub · Version: Paseo v0.15.3 at d91ae138cb931447635e94296023414a58bedcc5; hosted Hub page reread 2026-11-07 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-10
  • Documentation and source-level pass of Paseo v0.15.3; no hands-on scenario was run and unknown sub-questions remain unknown.
8 atomic answers
  • Release stage [supported] Stable and Beta channels; v0.x versioning. Sources: paseo:doc-updates-nov07, paseo:releases-nov07.
  • Access restrictions [partial] App stores can lag desktop releases and get no beta builds. The Hub page FAQ describes Hub access as a beta that 'stays small and trusted', while also offering self-hosting and a free hosted account. Sources: paseo:doc-updates-nov07, paseo:hub-page-faq-chk1.
  • Support [partial] GitHub issues and community links; no support SLA documented. Sources: paseo:github-metadata-nov07, paseo:issues-count-2026-10-09-nov07.
  • Response commitments [unknown] Response commitments: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Release activity [supported] GitHub latest and release body identify stable v0.15.3 November 6; stable desktop rollout is documented as 36 hours. Sources: paseo:release-current-nov07, paseo:doc-updates-nov07.
  • Status history [unknown] Status history: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Deprecation [unknown] Deprecation: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Export options [unknown] Export options: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.

Sources: paseo:doc-updates-nov07, paseo:releases-nov07, paseo:github-metadata-nov07, paseo:issues-count-2026-10-09-nov07, paseo:release-current-nov07, paseo:hub-page-faq-chk1

No sourced public finding not-published

No publishable sourced finding is available for this criterion. This does not mean the product lacks the capability.

Agent cross-checked partial

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.

Scope
Surfaces: Paseo desktop, Paseo Hub · Version: Paseo v0.15.3 at d91ae138cb931447635e94296023414a58bedcc5; hosted Hub page reread 2026-11-07 · Plan: Free · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
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.
10 atomic answers
  • Ongoing free [supported] Core app is free; Hub Free needs no card and does not expire. Sources: paseo:website-nov07, paseo:doc-hub-hosted-nov07.
  • Trial [unknown] Hub pricing page: no trial terms stated. Sources: paseo:hub-pricing-nov07.
  • Credits trial [unknown] Credits trial: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Self host cost [supported] Self-hosted Hub is free and open source (user infrastructure). Sources: paseo:hub-pricing-nov07, paseo:doc-hub-selfhost-nov07.
  • Paid only [supported] Core app is not paid-gated; Hub Pro adds unlimited runs and seats. Sources: paseo:hub-pricing-nov07.
  • Early access [unknown] Early access: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Free scenarios [unknown] Free scenarios: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Card required [supported] Hub Free requires no card. Sources: paseo:doc-hub-hosted-nov07.
  • Usage caps [supported] Hub Free: 50 agent runs per month and one seat. Sources: paseo:hub-pricing-nov07.
  • Paid evaluation [unknown] Paid evaluation: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.

Sources: paseo:website-nov07, paseo:doc-hub-hosted-nov07, paseo:hub-pricing-nov07, paseo:doc-hub-selfhost-nov07, paseo:hub-live-faq-nov07

Agent cross-checked partial

Hub pricing lists the unit (seat), included runs and the seat definition; Paseo documents no model or compute charge of its own (Claude Code and Codex are billed by their providers, and agents run on user machines). Minimum commitment, overage and cancellation terms were not stated.

Scope
Surfaces: Paseo Hub · Version: Paseo v0.15.3 at d91ae138cb931447635e94296023414a58bedcc5; hosted Hub page reread 2026-11-07 · Plan: Hub Free / Pro (hosted) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
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.
9 atomic answers
  • Units [supported] Per seat per month; runs capped on Free. Sources: paseo:hub-pricing-nov07.
  • Included limits [supported] 50 runs/month and 1 seat on Free. Sources: paseo:hub-pricing-nov07.
  • Overages [unknown] Overages: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Compute markup [partial] Paseo does not provide compute; agents run on user machines. Sources: paseo:website-nov07, paseo:doc-hub-security-nov07.
  • Model markup [partial] Paseo adds no charge for Claude Code or Codex usage. Sources: paseo:doc-claude-code-nov07, paseo:doc-codex-nov07.
  • Minimum commitment [unknown] Minimum commitment: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Cancellation [unknown] Cancellation: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Sales only unknowns [unknown] Sales only unknowns: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.
  • Transparency classification [unknown] Transparency classification: Searched Paseo public docs, changelog and repository at the pinned commit (v0.11.1) and the homepage/Hub pricing page; no statement answers this question. Unknown, not negative evidence.

Sources: paseo:hub-pricing-nov07, paseo:website-nov07, paseo:doc-hub-security-nov07, paseo:doc-claude-code-nov07, paseo:doc-codex-nov07

Sources

paseo:website-nov07

Paseo homepage

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.

Kind
vendor-claimed
Locator
Run it anywhere; providers; FAQ; sponsor section
Source date
Not stated
Retrieved
2026-11-07
paseo:changelog-nov07

Paseo: CHANGELOG.md

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

Kind
documented
Locator
Current stable v0.15.3 file; named headings and operations
Source date
2026-11-06
Retrieved
2026-11-07
paseo:doc-index-nov07

Paseo: Getting started

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.

Kind
documented
Locator
Current stable v0.15.3 file; named headings and operations
Source date
Not stated
Retrieved
2026-11-07
paseo:doc-why-nov07

Paseo: Why Paseo?

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.

Kind
documented
Locator
Current stable v0.15.3 file; named headings and operations
Source date
Not stated
Retrieved
2026-11-07
paseo:doc-cli-nov07

Paseo: CLI reference

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.

Kind
documented
Locator
Current stable v0.15.3 file; named headings and operations
Source date
Not stated
Retrieved
2026-11-07
paseo:doc-sdk-nov07

Paseo: TypeScript SDK

@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.

Kind
documented
Locator
Current stable v0.15.3 file; named headings and operations
Source date
Not stated
Retrieved
2026-11-07
paseo:doc-community-nov07

Paseo: Related projects

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.

Kind
documented
Locator
Current stable v0.15.3 file; named headings and operations
Source date
Not stated
Retrieved
2026-11-07
paseo:doc-updates-nov07

Paseo: Updates

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.

Kind
documented
Locator
Current stable v0.15.3 file; named headings and operations
Source date
Not stated
Retrieved
2026-11-07
paseo:doc-web-ui-nov07

Paseo: Self-hosting the web UI

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

Kind
documented
Locator
Current stable v0.15.3 file; named headings and operations
Source date
Not stated
Retrieved
2026-11-07
paseo:why-tag-nov07

public-docs/why.md, line 23

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.

Kind
source-inspected
Locator
Current stable v0.15.3 file; named headings and operations
Source date
Not stated
Retrieved
2026-11-07
Commit
d91ae138cb931447635e94296023414a58bedcc5
Path
public-docs/why.md
paseo:why-main-nov07

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

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

Kind
source-inspected
Locator
Current stable v0.15.3 file; named headings and operations
Source date
Not stated
Retrieved
2026-11-07
Commit
d91ae138cb931447635e94296023414a58bedcc5
Path
public-docs/why.md
paseo:claude-code-tag-mobile-nov07

Paseo v0.11.1 Claude Code terminal access

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.

Kind
documented
Locator
Current stable v0.15.3 file; named headings and operations
Source date
Not stated
Retrieved
2026-11-07
paseo:gaps-mobile-web

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

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.

Kind
source-inspected
Locator
Mobile browser visible viewport; packages/app/src/app/_layout.tsx compact/mobile panel routing; public-docs/web-ui.md
Source date
Not stated
Retrieved
2026-11-13
Commit
1c00b365c9e0b74c1580eba33d905d693125ae21
Path
packages/app/src/composer/dock/internal/fullscreen.tsx
paseo:orchestration-nov07

Paseo: public-docs/orchestration.md

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.

Kind
documented
Locator
Current stable v0.15.3 file; named headings and operations
Source date
Not stated
Retrieved
2026-11-07
paseo:workflows-nov07

Paseo: public-docs/orchestration-workflows.md

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.

Kind
documented
Locator
Current stable v0.15.3 file; named headings and operations
Source date
Not stated
Retrieved
2026-11-07
paseo:doc-providers-nov07

Paseo: Supported providers

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.

Kind
documented
Locator
Current stable v0.15.3 file; named headings and operations
Source date
Not stated
Retrieved
2026-11-07
paseo:doc-plugins-nov07

Paseo: Plugins

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.

Kind
documented
Locator
Current stable v0.15.3 file; named headings and operations
Source date
Not stated
Retrieved
2026-11-07
paseo:doc-custom-providers-nov07

Paseo: Custom providers

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

Kind
documented
Locator
Current stable v0.15.3 file; named headings and operations
Source date
Not stated
Retrieved
2026-11-07
paseo:supported-providers-tag-nov07

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

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.

Kind
source-inspected
Locator
Current stable v0.15.3 file; named headings and operations
Source date
Not stated
Retrieved
2026-11-07
Commit
d91ae138cb931447635e94296023414a58bedcc5
Path
public-docs/supported-providers.md
paseo:paseo-homepage-faq-nov07

Paseo homepage FAQ and integrations list

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

Kind
documented
Locator
Works with your tools list; FAQ native implementations
Source date
Not stated
Retrieved
2026-11-07
paseo:gap07-provider-catalog

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

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

Kind
documented
Locator
Native support and ACP catalog
Source date
Not stated
Retrieved
2026-11-07
paseo:agy-release-1

Paseo Antigravity support at v0.15.4

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

Kind
source-inspected
Locator
plugins/antigravity-provider/server/provider.ts lines 16-53, v0.15.4, commit 1c00b365c9e0b74c1580eba33d905d693125ae21
Source date
2026-11-10
Retrieved
2026-11-10
Commit
1c00b365c9e0b74c1580eba33d905d693125ae21
Path
plugins/antigravity-provider/server/provider.ts
paseo:doc-security-nov07

Paseo: Security

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.

Kind
documented
Locator
Current stable v0.15.3 file; named headings and operations
Source date
Not stated
Retrieved
2026-11-07
paseo:doc-claude-code-nov07

Paseo: Claude Code provider

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.

Kind
documented
Locator
Current stable v0.15.3 file; named headings and operations
Source date
Not stated
Retrieved
2026-11-07
paseo:doc-codex-nov07

Paseo: Codex provider

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

Kind
documented
Locator
Current stable v0.15.3 file; named headings and operations
Source date
Not stated
Retrieved
2026-11-07
paseo:paseo-custom-providers-tag-nov07

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

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).

Kind
source-inspected
Locator
Current stable v0.15.3 file; named headings and operations
Source date
Not stated
Retrieved
2026-11-07
Commit
d91ae138cb931447635e94296023414a58bedcc5
Path
public-docs/custom-providers.md
paseo:paseo-voice-tag-nov07

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

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).

Kind
source-inspected
Locator
Current stable v0.15.3 file; named headings and operations
Source date
Not stated
Retrieved
2026-11-07
Commit
d91ae138cb931447635e94296023414a58bedcc5
Path
public-docs/voice.md
paseo:changelog

Paseo: CHANGELOG.md

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.

Kind
documented
Locator
0.11.1 and 0.11.0 sections
Source date
2026-10-07
Retrieved
2026-10-09
paseo:doc-index

Paseo: Getting started

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.

Kind
documented
Locator
public-docs/index.md
Source date
Not stated
Retrieved
2026-10-08
paseo:doc-why

Paseo: Why Paseo?

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.

Kind
documented
Locator
public-docs/why.md
Source date
Not stated
Retrieved
2026-10-09
paseo:doc-workspaces

Paseo: Workspaces

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.

Kind
documented
Locator
public-docs/workspaces.md
Source date
Not stated
Retrieved
2026-10-09
paseo:doc-worktrees

Paseo: Git worktrees

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.

Kind
documented
Locator
public-docs/worktrees.md
Source date
Not stated
Retrieved
2026-10-09
paseo:doc-connectivity

Paseo: Connectivity

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.

Kind
documented
Locator
public-docs/connectivity.md
Source date
Not stated
Retrieved
2026-10-08
paseo:doc-docker

Paseo: Docker

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.

Kind
documented
Locator
public-docs/docker.md
Source date
Not stated
Retrieved
2026-10-08
paseo:doc-troubleshooting

Paseo: Troubleshooting

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.

Kind
documented
Locator
public-docs/troubleshooting.md
Source date
Not stated
Retrieved
2026-10-09
paseo:orchestration

Paseo: public-docs/orchestration.md

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.

Kind
documented
Locator
public-docs/orchestration.md
Source date
Not stated
Retrieved
2026-10-08
paseo:doc-security

Paseo: Security

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.

Kind
documented
Locator
public-docs/security.md
Source date
Not stated
Retrieved
2026-10-09
paseo:doc-mcp

Paseo: MCP reference

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.

Kind
documented
Locator
public-docs/mcp.md
Source date
Not stated
Retrieved
2026-10-09
paseo:doc-cli

Paseo: CLI reference

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.

Kind
documented
Locator
public-docs/cli.md
Source date
Not stated
Retrieved
2026-10-09
paseo:doc-sdk

Paseo: TypeScript SDK

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.

Kind
documented
Locator
public-docs/sdk/index.md
Source date
Not stated
Retrieved
2026-10-09
paseo:doc-hub

Paseo: Hub overview

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.

Kind
documented
Locator
public-docs/hub/index.md
Source date
Not stated
Retrieved
2026-10-09
paseo:doc-hub-concepts

Paseo: How Hub works

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.

Kind
documented
Locator
public-docs/hub/concepts.md
Source date
Not stated
Retrieved
2026-10-09
paseo:doc-hub-api

Paseo: Hub public API

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.

Kind
documented
Locator
public-docs/hub/api.md
Source date
Not stated
Retrieved
2026-10-09
paseo:doc-permissions

Paseo: Daemon permissions

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.

Kind
documented
Locator
docs/permissions.md
Source date
Not stated
Retrieved
2026-10-09
paseo:doc-plugins

Paseo: Plugins

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.

Kind
documented
Locator
public-docs/plugins/index.md
Source date
Not stated
Retrieved
2026-10-08
paseo:doc-skills

Paseo: Orchestration skills

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

Kind
documented
Locator
public-docs/skills.md
Source date
Not stated
Retrieved
2026-10-08
paseo:gap07-plugin-trust

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

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.

Kind
documented
Locator
Trust model; plugin sources; backend logging
Source date
Not stated
Retrieved
2026-11-07
paseo:website

Paseo homepage

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.

Kind
vendor-claimed
Locator
Run it anywhere; providers; FAQ; sponsor section
Source date
Not stated
Retrieved
2026-10-09
paseo:desktop-package

Paseo: packages/desktop/package.json

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

Kind
source-inspected
Locator
devDependencies.electron and license
Source date
Not stated
Retrieved
2026-10-08
Commit
d0bc188a5b1be72f170f7db850716b7006f12f7e
Path
packages/desktop/package.json
paseo:mobile-package

Paseo: packages/app/package.json

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.

Kind
source-inspected
Locator
dependencies.expo, dependencies.react-native, dependencies.react-native-web, dependencies.react-dom and scripts.build:web
Source date
Not stated
Retrieved
2026-10-08
Commit
d0bc188a5b1be72f170f7db850716b7006f12f7e
Path
packages/app/package.json
paseo:doc-lifecycle

Paseo: Agent lifecycle

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.

Kind
documented
Locator
docs/agent-lifecycle.md
Source date
Not stated
Retrieved
2026-10-09
paseo:workflows

Paseo: public-docs/orchestration-workflows.md

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.

Kind
documented
Locator
public-docs/orchestration-workflows.md
Source date
Not stated
Retrieved
2026-10-09
paseo:gap07-workflow-order

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

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.

Kind
documented
Locator
Conditions and ordered output; Deadlines; Choose an agent
Source date
Not stated
Retrieved
2026-11-07
paseo:doc-profiles

Paseo: Agent profiles

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

Kind
documented
Locator
public-docs/agent-profiles.md
Source date
Not stated
Retrieved
2026-10-08
paseo:doc-providers

Paseo: Supported providers

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.

Kind
documented
Locator
public-docs/supported-providers.md
Source date
Not stated
Retrieved
2026-10-09
paseo:doc-parallel

Paseo: Run parallel tasks

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.

Kind
documented
Locator
public-docs/parallel-development.md
Source date
Not stated
Retrieved
2026-10-09
paseo:gaps-native-tasks

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

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.

Kind
source-inspected
Locator
FileTaskStore; types.ts; references across packages/server, packages/cli and packages/app; Hub routes and schema
Source date
Not stated
Retrieved
2026-11-13
Commit
1c00b365c9e0b74c1580eba33d905d693125ae21
Path
packages/server/src/tasks/task-store.ts
paseo:doc-schedules

Paseo: Schedules

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.

Kind
documented
Locator
public-docs/schedules.md
Source date
Not stated
Retrieved
2026-10-09
paseo:doc-schedules-cli

Paseo: Schedules from the CLI

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.

Kind
documented
Locator
public-docs/schedules-cli.md
Source date
Not stated
Retrieved
2026-10-09
paseo:doc-hub-daemons

Paseo: Daemons in Hub

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.

Kind
documented
Locator
public-docs/hub/daemons.md
Source date
Not stated
Retrieved
2026-10-09
paseo:doc-hub-activity

Paseo: Hub activity

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.

Kind
documented
Locator
public-docs/hub/activity.md
Source date
Not stated
Retrieved
2026-10-09
paseo:doc-hub-faq

Paseo: Hub FAQ

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.

Kind
documented
Locator
public-docs/hub/faq.md
Source date
Not stated
Retrieved
2026-10-08
paseo:paseo-orchestration-tag

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

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).

Kind
source-inspected
Locator
Built-in Paseo tools (MCP) lines 31 to 37; CLI route line 48; skills line 44
Source date
Not stated
Retrieved
2026-10-09
Commit
ab10a6694
Path
public-docs/orchestration.md
paseo:doc-claude-code

Paseo: Claude Code provider

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.

Kind
documented
Locator
public-docs/claude-code.md
Source date
Not stated
Retrieved
2026-10-09
paseo:doc-community

Paseo: Related projects

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.

Kind
documented
Locator
public-docs/community.md
Source date
Not stated
Retrieved
2026-10-08
paseo:doc-web-ui

Paseo: Self-hosting the web UI

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

Kind
documented
Locator
public-docs/web-ui.md
Source date
Not stated
Retrieved
2026-10-08
paseo:gaps-execution-hosts

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

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.

Kind
documented
Locator
Hub FAQ Can the Hub run code on my machines; plan list
Source date
Not stated
Retrieved
2026-11-13
paseo:gaps-host-architecture-current

Paseo: public-docs/why.md

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.

Kind
documented
Locator
Develop in one workspace; Continue from another device
Source date
Not stated
Retrieved
2026-11-13
paseo:gaps-remote-transport-current

Paseo: public-docs/connectivity.md

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.

Kind
documented
Locator
SSH setup and Tailscale daemon listen configuration
Source date
Not stated
Retrieved
2026-11-13
paseo:doc-hub-security

Paseo: Hub security

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.

Kind
documented
Locator
public-docs/hub/security.md
Source date
Not stated
Retrieved
2026-10-09
paseo:doc-hub-github

Paseo: GitHub access

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.

Kind
documented
Locator
public-docs/hub/github.md
Source date
Not stated
Retrieved
2026-10-09
paseo:gap07-host-isolation

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

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.

Kind
documented
Locator
Protect configuration authority; Provider-native controls
Source date
Not stated
Retrieved
2026-11-07
paseo:gap07-docker

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

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.

Kind
documented
Locator
What the image includes; Volumes; Security
Source date
Not stated
Retrieved
2026-11-07
paseo:gap07-lifecycle-recovery

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

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.

Kind
documented
Locator
Daemon restart recovery; Runtime residency; Limitations; Storage
Source date
Not stated
Retrieved
2026-11-07
paseo:doc-mcp-nov07

Paseo: MCP reference

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.

Kind
documented
Locator
Current stable v0.15.3 file; named headings and operations
Source date
Not stated
Retrieved
2026-11-07
paseo:doc-hub-activity-nov07

Paseo: Hub activity

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

Kind
documented
Locator
Current stable v0.15.3 file; named headings and operations
Source date
Not stated
Retrieved
2026-11-07
paseo:doc-lifecycle-nov07

Paseo: Agent lifecycle

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.

Kind
documented
Locator
Current stable v0.15.3 file; named headings and operations
Source date
Not stated
Retrieved
2026-11-07
paseo:doc-troubleshooting-nov07

Paseo: Troubleshooting

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.

Kind
documented
Locator
Current stable v0.15.3 file; named headings and operations
Source date
Not stated
Retrieved
2026-11-07
paseo:hub-pricing-nov07

Paseo Hub plans and pricing

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.

Kind
vendor-claimed
Locator
Plans section
Source date
Not stated
Retrieved
2026-11-07
paseo:doc-hub-nov07

Paseo: Hub overview

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.

Kind
documented
Locator
Current stable v0.15.3 file; named headings and operations
Source date
Not stated
Retrieved
2026-11-07
paseo:doc-hub-hosted-nov07

Paseo: Hosted Hub

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.

Kind
documented
Locator
Current stable v0.15.3 file; named headings and operations
Source date
Not stated
Retrieved
2026-11-07
paseo:doc-hub-github-nov07

Paseo: GitHub access

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.

Kind
documented
Locator
Current stable v0.15.3 file; named headings and operations
Source date
Not stated
Retrieved
2026-11-07
paseo:doc-hub-api-nov07

Paseo: Hub public API

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.

Kind
documented
Locator
Current stable v0.15.3 file; named headings and operations
Source date
Not stated
Retrieved
2026-11-07
paseo:gap07-principal-permissions

Paseo v0.15.3: docs/permissions.md

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.

Kind
documented
Locator
Principals, pairing and semantic permission names
Source date
Not stated
Retrieved
2026-11-07
paseo:gaps-shared-prompts

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

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.

Kind
source-inspected
Locator
send_agent_message_request permission; docs/permissions.md; session.ts handleSendAgentMessage around lines 8305-8425
Source date
Not stated
Retrieved
2026-11-13
Commit
1c00b365c9e0b74c1580eba33d905d693125ae21
Path
packages/server/src/server/authorization/operation-permissions.ts
paseo:gaps-hub-human-intake

Paseo: src/triggers/slack/match.ts

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.

Kind
source-inspected
Locator
matchesFilters from_users; events.ts normalized author ID
Source date
Not stated
Retrieved
2026-11-13
Commit
61e51c56f8756e40c55a30982160ce000f2aa177
Path
src/triggers/slack/match.ts
paseo:gaps-hub-thread-continuity

Paseo: src/triggers/slack/provider.ts

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.

Kind
source-inspected
Locator
Accepted match conversation key; triggers/panel.tsx Agent continuity control; triggers/continuation.ts
Source date
Not stated
Retrieved
2026-11-13
Commit
61e51c56f8756e40c55a30982160ce000f2aa177
Path
src/triggers/slack/provider.ts
paseo:gaps-hub-session-delivery

Paseo: src/agent-sessions/index.ts

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.

Kind
source-inspected
Locator
AgentSessions.dispatch findAgentSessionByKey and deliver; workflows/engine.ts continuationKey
Source date
Not stated
Retrieved
2026-11-13
Commit
61e51c56f8756e40c55a30982160ce000f2aa177
Path
src/agent-sessions/index.ts
paseo:gaps-hub-message-contract

Paseo: docs/hub.md

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.

Kind
documented
Locator
Connection and authority; Session grants and agent operations
Source date
Not stated
Retrieved
2026-11-13
paseo:gaps-hub-public-preview

Paseo: public preview availability

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.

Kind
documented
Locator
Early development notice; Quick start; Run with Docker Compose
Source date
Not stated
Retrieved
2026-11-13
paseo:hub-pricing

Paseo Hub plans and pricing

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.

Kind
vendor-claimed
Locator
Plans section
Source date
Not stated
Retrieved
2026-10-09
paseo:gaps-hub-roles

Paseo: src/auth/organization-policy.ts

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.

Kind
source-inspected
Locator
ROLE_CAPABILITIES; organization-contract.ts ORGANIZATION_ROLES; organization-access.ts role mutations
Source date
Not stated
Retrieved
2026-11-13
Commit
61e51c56f8756e40c55a30982160ce000f2aa177
Path
src/auth/organization-policy.ts
paseo:gaps-hub-auth

Paseo: src/auth/server.ts

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.

Kind
source-inspected
Locator
createAuthServer emailAndPassword and plugins; src/auth; package.json
Source date
Not stated
Retrieved
2026-11-13
Commit
61e51c56f8756e40c55a30982160ce000f2aa177
Path
src/auth/server.ts
paseo:doc-metadata

Paseo: Metadata generation

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.

Kind
documented
Locator
public-docs/metadata-generation.md
Source date
Not stated
Retrieved
2026-10-09
paseo:license-chk2-nov07

Paseo licence at v0.15.3

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.

Kind
source-inspected
Locator
LICENSE opening notice and Apache-2.0 terms
Source date
Not stated
Retrieved
2026-11-07
Commit
d91ae138cb931447635e94296023414a58bedcc5
Path
LICENSE
paseo:desktop-license-chk2-nov07

Paseo desktop manifest at v0.15.3

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.

Kind
source-inspected
Locator
name, version and license fields
Source date
Not stated
Retrieved
2026-11-07
Commit
d91ae138cb931447635e94296023414a58bedcc5
Path
packages/desktop/package.json
paseo:security-chk2-nov07

Paseo security docs at v0.15.3

Daemon runs on a user host; relay is optional and defaults off. Documentation links the separately hosted open-source getpaseo/paseo-relay service. The separate relay licence was not audited.

Kind
documented
Locator
Architecture; Relay connections
Source date
Not stated
Retrieved
2026-11-07
paseo:hub-selfhost-chk2-nov07

Paseo self-hosting Hub at v0.15.3

npx @getpaseo/hub starts a self-hosted Hub with embedded PGlite by default or PostgreSQL via DATABASE_URL. GitHub webhooks need public HTTPS; Slack Socket Mode does not. Hosted/self-hosted feature parity and per-package Hub licence were not audited.

Kind
documented
Locator
Self-hosting Hub; Local data; PostgreSQL
Source date
Not stated
Retrieved
2026-11-07
paseo:release-chk2-nov07

Paseo v0.15.3 release

Latest stable v0.15.3 was released November 6, 2026. Annotated tag 944c98a8fd802586d6d79ac375d4fd811c6545df peels to d91ae138cb931447635e94296023414a58bedcc5; licence and component manifest were read at that commit.

Kind
documented
Locator
Release date; annotated tag peeled commit
Source date
2026-11-06
Retrieved
2026-11-07
paseo:doc-hub-selfhost

Paseo: Self-hosting Hub

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.

Kind
documented
Locator
public-docs/hub/self-hosting/index.md
Source date
Not stated
Retrieved
2026-10-09
paseo:why-tag

public-docs/why.md, line 23

Re-read 2026-10-09 at release tag ab10a6694: "Open source. No telemetry on your code." No "tracking" or "required account" wording; no phone files, terminals or diffs wording.

Kind
source-inspected
Locator
public-docs/why.md, line 23
Source date
Not stated
Retrieved
2026-10-09
Commit
ab10a6694
Path
public-docs/why.md
paseo:why-main

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

Re-read 2026-10-09 at main d0bc188a5 (eight commits after the tag): "no telemetry, tracking, or required Paseo account" (line 43) and "gives you agents, files, terminals, and diffs on your phone" (line 35). Main-only wording; not claimed for v0.11.1.

Kind
source-inspected
Locator
public-docs/why.md, lines 35 and 43
Source date
Not stated
Retrieved
2026-10-09
Commit
d0bc188a5
Path
public-docs/why.md
paseo:paseo-custom-providers-tag

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

Re-read 2026-10-09 at tag ab10a6694: 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).

Kind
source-inspected
Locator
env examples lines 56, 129 and 134; Multiple profiles line 118
Source date
Not stated
Retrieved
2026-10-09
Commit
ab10a6694
Path
public-docs/custom-providers.md
paseo:paseo-voice-tag

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

Re-read 2026-10-09 at tag ab10a6694: 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).

Kind
source-inspected
Locator
providers.openai.stt and tts apiKey examples, lines 94 and 98
Source date
Not stated
Retrieved
2026-10-09
Commit
ab10a6694
Path
public-docs/voice.md
paseo:d80-why

paseo public-docs/why.md

Paseo is Apache-2.0 with no telemetry, tracking or required Paseo account.

Kind
documented
Locator
public-docs/why.md l43-l44; Why Paseo; v0.16.0 (c54bc39)
Source date
Not stated
Retrieved
2026-11-16
paseo:d80-negtree

paseo packages

No analytics or crash-reporting code exists in the app, server or CLI packages; the only analytics script is Plausible on the marketing website package.

Kind
source-inspected
Locator
packages; case-insensitive searches for posthog, sentry, amplitude, mixpanel, segment, plausible, crashlytics and telemetry over packages (ts, tsx, json, kt, swift); v0.16.0 (c54bc39)
Source date
Not stated
Retrieved
2026-11-16
Commit
c54bc39e7997c03a07402c09df2e825889432557
Path
packages
paseo:doc-hub-security-nov07

Paseo: Hub security

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.

Kind
documented
Locator
Current stable v0.15.3 file; named headings and operations
Source date
Not stated
Retrieved
2026-11-07
paseo:github-metadata-nov07

GitHub repository metadata

Repository metadata reread November 7 for repository identity. No refreshed popularity count is used as capability evidence.

Kind
documented
Locator
stargazers_count, open_issues_count, pushed_at, license
Source date
Not stated
Retrieved
2026-11-07
paseo:releases-nov07

Paseo GitHub releases

Current latest stable resolves to v0.15.3 dated November 6; tag peels to d91ae138cb931447635e94296023414a58bedcc5. Earlier v0.11.1 is historical.

Kind
documented
Locator
Latest stable release v0.15.3, November 6, 2026; historical entries retained
Source date
2026-11-06
Retrieved
2026-11-07
paseo:issues-count-2026-10-09-nov07

GitHub API repos/getpaseo/paseo open_issues_count

Current public issues list reread November 7; prior October counts are not carried forward as current.

Kind
documented
Locator
open_issues_count
Source date
Not stated
Retrieved
2026-11-07
paseo:release-current-nov07

Paseo v0.15.3

Current stable release body explicitly dates 0.15.3 November 6, 2026. Annotated tag peels to d91ae138cb931447635e94296023414a58bedcc5. No binary executed.

Kind
documented
Locator
Latest release; dated release body; peeled git tag
Source date
2026-11-06
Retrieved
2026-11-07
paseo:hub-page-faq-chk1

Paseo Hub - GitHub, Slack, and Discord triggers

Hub FAQ says Hub can run code on connected daemons, which is why access to the beta stays small and trusted; users can self-host today or sign in to Hosted Hub for a free account and upgrade from Billing.

Kind
vendor-claimed
Locator
FAQ: 'Can the Hub run code on my machines?' and 'How do I get access?'
Source date
Not stated
Retrieved
2026-11-07
paseo:doc-hub-selfhost-nov07

Paseo: Self-hosting Hub

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.

Kind
documented
Locator
Current stable v0.15.3 file; named headings and operations
Source date
Not stated
Retrieved
2026-11-07
paseo:hub-live-faq-nov07

Paseo Hub live page FAQ

Current Hub FAQ retains small trusted beta language and dispatch to user-connected daemons; self-host or sign up for hosted Free.

Kind
documented
Locator
FAQ: "Can the Hub run code on my machines?"; beta reference in answer
Source date
Not stated
Retrieved
2026-11-07

Comparisons with Paseo

Compare Paseo with any other product on adecomparison.com.