.tgz`, plus a file inventory and integrity\nhash in `.smoke/npm/pack.json`. It does not publish anything. The generated package\ncontains the runtime sources, original resvg WASM, precompiled MathJax renderer,\nstatic MathJax SVG font data, preparation scripts,\nworker lockfile, and a production `npm-shrinkwrap.json`. Host libraries and build\ntools are excluded from its dependencies. The precompiled renderer uses the same\nMathJax 3.2.2 profile as the Git source and includes its license. Unused MathJax\nspeech/XML dependencies are not installed; dependency overrides in a published\npackage do not reliably control the consuming application's dependency graph.\n\nThe repository stays private in npm metadata because its manifest prepares a Git\ncheckout with `npm ci` and a source build. The generated npm package is public-ready\nand its manifest prepares the formula assets, Mermaid worker and browser. Publis"},{"id":"agent-crew","repo":"omercnet/paseo-plugins","url":"https://github.com/omercnet/paseo-plugins/tree/main/agent-crew","package":"@omercnet/paseo-agent-crew","npm":{"package":"@omercnet/paseo-agent-crew","version":"1.0.1","integrity":"sha512-ysZV0Rcmv3o0uX45gUDriPWc9Of/hZ6lKv6UCa1JTPn26I7cd140HYp3DNW7ylzCGcbPO3YcWrSPUq0qLMlJ2g==","publishedAt":"2026-09-28T11:36:39.809Z","downloadsLast30Days":5008},"name":"agent-crew","description":"A Paseo Explorer panel for visualizing and controlling every managed agent crew in a workspace.","categories":["monitoring","productivity","orchestration"],"platforms":[],"caveats":["Requires Paseo 0.8.x"],"images":["https://raw.githubusercontent.com/omercnet/paseo-plugins/main/agent-crew/docs/images/agent-crew-overview.png","https://raw.githubusercontent.com/omercnet/paseo-plugins/main/agent-crew/docs/images/agent-crew-action.png"],"themes":[],"health":{"manifestValid":true,"hasReadme":true,"hasLicense":true,"hasTests":true,"hasTypecheckScript":true,"updatedRecently":true},"scannedAt":"2026-09-29T03:52:34.153Z","addedAt":"2026-09-08T17:06:44+03:00","npmSecurity":{"status":"passed","blockingFindings":0,"advisoryFindings":0,"scannedAt":"2026-09-28T11:48:35.920Z","version":"1.0.1","integrity":"sha512-ysZV0Rcmv3o0uX45gUDriPWc9Of/hZ6lKv6UCa1JTPn26I7cd140HYp3DNW7ylzCGcbPO3YcWrSPUq0qLMlJ2g=="},"path":"agent-crew","version":"1.0.1","security":{"status":"passed","blockingFindings":0,"advisoryFindings":0,"scannedAt":"2026-09-28T11:48:35.920Z","commit":"38c6a71949140fd608f95ba2e3594031caa1d8f5"},"npmPreview":{"package":"@omercnet/paseo-agent-crew","version":"1.0.1-next.167.1","integrity":"sha512-hEveUpyv4cx/Y7ARnSOkbiycaKD4CnNWduudQA5joDcm5Dtx2BbXRrOLJdqwkvquWHns0xyUPq9DYxTITQwfnw==","publishedAt":"2026-09-28T11:36:37.389Z","distTag":"next"},"npmPreviewSecurity":{"status":"passed","blockingFindings":0,"advisoryFindings":0,"scannedAt":"2026-09-28T11:48:35.920Z","version":"1.0.1-next.167.1","integrity":"sha512-hEveUpyv4cx/Y7ARnSOkbiycaKD4CnNWduudQA5joDcm5Dtx2BbXRrOLJdqwkvquWHns0xyUPq9DYxTITQwfnw=="},"author":"Omer Cohen","license":"MIT","paseoVersionRequirement":"^0.9.0 || ^0.10.0-beta.1","descriptionNodes":[{"type":"text","text":"A Paseo Explorer panel for visualizing and controlling every managed agent crew in a workspace."}],"caveatNodes":[[{"type":"text","text":"Requires Paseo 0.8.x"}]],"manifest":{"id":"agent-crew","description":"A Paseo Explorer panel for visualizing and controlling every managed agent crew in a workspace.","requirements":{"paseo":"^0.9.0 || ^0.10.0-beta.1"}},"repoMeta":{"stars":13,"defaultBranch":"main","pushedAt":"2026-09-29T01:43:00Z"},"owner":{"login":"omercnet","avatarUrl":"https://avatars.githubusercontent.com/u/639682?v=4"},"installNotesHtml":"Paseo plugins are trusted, unsandboxed code. Review the source before installing it.
\nFrom npm:
\npaseo plugin install npm:@omercnet/paseo-agent-crew\n
\nUpdate the installed npm package after reviewing the proposed revision:
\npaseo plugin update agent-crew\n
\nOpen a workspace, choose New tab in Explorer, then select Agent Crew. The Open Agent Crew\nCommand Center action opens it directly.
","readmeText":"# Agent Crew\n\nSee and control every managed Paseo agent working in a workspace. Agent Crew adds a\nworkspace-context Explorer panel plus an `Open Agent Crew` Command Center item.\n\nIt answers \"which crews are active here, and which agent needs me now?\" while preserving managed\nparent-child relationships across workspace boundaries.\n\n## Demo\n\nhttps://github.com/user-attachments/assets/abed14b4-f30c-4db7-a48e-d5a380d330fe\n\n## Screenshots\n\nAgent, workspace, and task details come from an isolated synthetic workspace. Both PNGs were\ncaptured at 2× pixel density after browser DevTools rewrote local paths and host labels and verified\nthat no private organization names remained in the rendered page.\n\n### Crew overview\n\n\n\n### Safe action confirmation\n\n\n\n## Auto open\n\nWhen enabled in the plugin settings screen, Agent Crew opens the Explorer tab once for each new workspace observed on that host.\n\n- Default: off.\n- Existing workspaces are not opened when the setting is enabled.\n- Disabling stops queued and future opens. Re-enabling resumes observation for workspaces created or updated afterward.\n- Workspace claims are remembered on the daemon so reconnects and reloads do not reopen a workspace.\n- A failed claim batch is retried once after two seconds, then dropped with a logged error.\n\n## What it shows\n\n- Every non-archived managed agent in the current workspace, organized into orchestration trees.\n- Managed descendants remain in their crew when they run in another workspace.\n- Out-of-workspace ancestors required to explain a local agent appear as dimmed, open-only context;\n unrelated foreign branches are pruned.\n- Independent agents appear as top-level rows, while collapsible tree rails and descendant counts\n distinguish delegated crews.\n- Provider and model, workspace, last error, state, and activity age for each visible agent.\n- Counts and filters for Needs input, Failed, Working, Ready, Idle, and Closed.\n- Text search over title, agent ID, provider, model, working directory, workspace, and labels.\n- Live agent and workspace subscriptions, debounced by 500 ms, plus a 30-second backstop refresh.\n- Direct navigation to a selected agent when the host provides agent navigation.\n- Explicit Allow and Deny controls for visible pending permission requests.\n\n## Controls\n\nEach row exposes the operations available through the public Paseo SDK:\n\n- **Open** navigates to the selected agent.\n- **Expand or collapse** shows or hides a managed branch without changing agent state.\n- **Nudge** sends a follow-up to an idle or waiting agent.\n- **Interrupt and redirect** sends a new direction to a running agent. Paseo stops the active turn\n before starting that direction, and the confirmation dialog says so explicitly.\n- **Detach** removes a managed child branch from its parent while allowing it to continue\n independently. Root agents and context-only ancestors do not expose this action.\n- **Archive** stops and removes the selected agent. Same-workspace descendants may be archived with\n it; cross-workspace descendants may detach and continue. The confirmation dialog describes that\n behavior before the action runs.\n- **Permission allow / deny** opens one explicit request modal for the selected pending request and\n answers it with `request.id`; no automatic approval policy runs.\n\nEvery mutating control uses a confirmation dialog. Successful actions show a toast; SDK errors are\nshown without hiding the failure.\n\n## How it reads state\n\n`usePaseo().agents.list()` and `usePaseo().workspaces.list()` page the selected daemon directory at\n200 entries per page, up to 10 pages. Parent relationships come from the first-class\n`parentAgentId` field when the public SDK exposes it, with a legacy label fallback for older\nsnapshots. The workspace crew contains local agents, their managed descendants, and only the foreign\nancestor paths needed to explain local membership. Archived agents are omitted, malformed parent\ncycles are bounded, and siblings are ordered by actionable state, creation time, then ID.\n\nState precedence is:\n\n1. Failed\n2. Needs input\n3. Working\n4. Ready\n5. Closed\n6. Idle\n\nFailed takes precedence over pending permission state so an errored agent is never presented as an\nagent that can resume normally.\n\n## Limits\n\nAgent Crew intentionally stays inside the public Paseo plugin SDK.\n\n- It shows managed Paseo agents only. Native provider subagents are not exposed by the public plugin\n SDK.\n- Workspace-less top-level agents are outside every workspace crew; workspace-less descendants of\n visible members remain in that crew.\n- It does not add heartbeat controls, private cancellation calls, or direct daemon API access.\n- Sending to a running agent interrupts its active turn; there is no separate non-interrupting send\n operation.\n- If the daemon contains more than 2,000 agents, the panel warns that its directory snapshot may\n omit agents in this workspace or their descendants.\n\n## Install\n\nPaseo plugins are trusted, unsandboxed code. Review the source before installing it.\n\nFrom npm:\n\n```bash\npaseo plugin install npm:@omercnet/paseo-agent-crew\n```\n\nUpdate the installed npm package after reviewing the proposed revision:\n\n```bash\npaseo plugin update agent-crew\n```\n\nOpen a workspace, choose **New tab** in Explorer, then select **Agent Crew**. The **Open Agent Crew**\nCommand Center action opens it directly.\n\n## Develop\n\n```bash\nbun install\nbun run check\nbun run test\nbun run test:coverage\nbun run typecheck\n```\n\nThe manifest supports Paseo `^0.9.0 || ^0.10.0-beta.1`. Development pins the stable 0.9 SDK line; nightly compatibility checks run the OMP provider against both the current stable and beta SDK channels. React 19.1 and React Native 0.81 match the host.\n\nRelease Please maintains versions, changelog entries, component tags, and GitHub releases from\nConventional Commits in the monorepo.\n"},{"id":"agent-heartbeats","repo":"panrafal/paseo-plugins","url":"https://github.com/panrafal/paseo-plugins/tree/main/agent-heartbeats","name":"agent-heartbeats","description":"Composer pill with the heartbeat count, plus a panel to list, create, edit, and delete that agent's heartbeats.","categories":["productivity"],"platforms":[],"caveats":["Changing a heartbeat prompt or max-run count creates a replacement and resets run history"],"images":["https://raw.githubusercontent.com/panrafal/paseo-plugins/004c6a80c6aa8e76bb563694c3eee5c2c0b0466f/agent-heartbeats/images/agent-heartbeats-panel.png","https://raw.githubusercontent.com/panrafal/paseo-plugins/004c6a80c6aa8e76bb563694c3eee5c2c0b0466f/agent-heartbeats/images/agent-heartbeats-pill.png"],"themes":[],"health":{"manifestValid":true,"hasReadme":true,"hasLicense":true,"hasTests":false,"hasTypecheckScript":true,"updatedRecently":true},"scannedAt":"2026-09-25T20:16:12.498Z","addedAt":"2026-09-10T11:29:03+03:00","path":"agent-heartbeats","version":"0.1.0","security":{"status":"failed","blockingFindings":1,"advisoryFindings":0,"scannedAt":"2026-09-25T20:04:23.597Z","commit":"004c6a80c6aa8e76bb563694c3eee5c2c0b0466f"},"author":"panrafal","license":"MIT","paseoVersionRequirement":">=0.7.2-0","descriptionNodes":[{"type":"text","text":"Composer pill with the heartbeat count, plus a panel to list, create, edit, and delete that agent's heartbeats."}],"caveatNodes":[[{"type":"text","text":"Changing a heartbeat prompt or max-run count creates a replacement and resets run history"}]],"manifest":{"id":"agent-heartbeats","requirements":{"paseo":">=0.7.2-0"}},"repoMeta":{"stars":2,"defaultBranch":"main","pushedAt":"2026-09-24T07:33:21Z"},"owner":{"login":"panrafal","avatarUrl":"https://avatars.githubusercontent.com/u/1268900?v=4"},"installNotesHtml":"paseo plugin add panrafal/paseo-plugins:agent-heartbeats\n
\nFrom a checkout:
\nnpm install\nnpm run typecheck\npaseo plugin install /absolute/path/to/paseo-plugins/agent-heartbeats\npaseo plugin ls\n
\nAfter editing:
\nnpm run typecheck\npaseo plugin reload agent-heartbeats\npaseo plugin logs agent-heartbeats\n
","limitationsNotesHtml":"\n- Completed heartbeats are not counted or listed.
\n- Changing a heartbeat prompt or maximum-run count creates a replacement and resets that\nheartbeat's run history. Cron-only edits keep history.
\n
","readmeText":"# agent-heartbeats\n\nPaseo plugin that adds a compact heartbeat icon and count to every active agent's composer. Pressing\nthe pill opens an agent-scoped panel for reviewing and managing that agent's heartbeats.\n\n\n\n\n## Interface\n\n- The composer pill contains only a heartbeat icon and the number of currently scheduled\n heartbeats.\n- The panel lists each prompt, human-readable cadence, raw cron expression, next run, completed run\n count, and maximum run count.\n- Heartbeats can be edited or deleted. Cron-only edits preserve their run history. Paseo does not\n expose prompt or maximum-run updates for heartbeats, so changing either creates a replacement and\n resets the daemon's run history for that heartbeat.\n- The add form is always visible. Its schedule field accepts five-field cron, one-shot delays such as\n `15m`, `15 minutes`, or `in one hour`, and recurring phrases such as `every 15 minutes`. Suggested\n common schedules appear directly below the field.\n- One-shot delays are compiled to a UTC cron occurrence with a one-run limit. Recurring phrases are\n accepted only when five-field cron can represent the interval exactly.\n\nThe count and panel refresh every 15 seconds and immediately after a mutation. Completed heartbeats\nare not counted or listed.\n\n## Runtime behavior\n\nThe plugin reads the daemon's atomic schedule records under `$PASEO_HOME/schedules` to list\nagent-target heartbeats, including heartbeats created outside this plugin. Mutations run Paseo's\nsupported `heartbeat create`, `heartbeat update`, and `heartbeat delete` commands without a shell,\nafter checking that the heartbeat belongs to the selected agent.\n\n## Limitations\n\n- Completed heartbeats are not counted or listed.\n- Changing a heartbeat prompt or maximum-run count creates a replacement and resets that\n heartbeat's run history. Cron-only edits keep history.\n\n## Install\n\n```bash\npaseo plugin add panrafal/paseo-plugins:agent-heartbeats\n```\n\nFrom a checkout:\n\n```bash\nnpm install\nnpm run typecheck\npaseo plugin install /absolute/path/to/paseo-plugins/agent-heartbeats\npaseo plugin ls\n```\n\nAfter editing:\n\n```bash\nnpm run typecheck\npaseo plugin reload agent-heartbeats\npaseo plugin logs agent-heartbeats\n```\n"},{"id":"agent-link-9router","repo":"itsjustanks/paseo-plugin-9router","url":"https://github.com/itsjustanks/paseo-plugin-9router/tree/main/apps/paseo","name":"agent-link-9router","description":"The runtime ID is `agent-link-9router`. Open **9Router** in the Paseo sidebar.","categories":["provider","productivity"],"platforms":[],"caveats":[],"images":[],"themes":[],"health":{"manifestValid":true,"hasReadme":true,"hasLicense":true,"hasTests":true,"hasTypecheckScript":true,"updatedRecently":true},"scannedAt":"2026-09-25T20:16:13.450Z","addedAt":"2026-09-10T18:09:18+03:00","path":"apps/paseo","version":"0.16.0","security":{"status":"passed","blockingFindings":0,"advisoryFindings":0,"scannedAt":"2026-09-25T20:04:23.597Z","commit":"f63923bec9feddb4a5e0994d918caf2dbb4beb24"},"license":"MIT","paseoVersionRequirement":">=0.8.0","descriptionNodes":[{"type":"text","text":"The runtime ID is "},{"type":"text","text":"agent-link-9router","code":true},{"type":"text","text":". Open "},{"type":"text","text":"9Router","strong":true},{"type":"text","text":" in the Paseo sidebar."}],"caveatNodes":[],"manifest":{"id":"agent-link-9router","requirements":{"paseo":">=0.8.0"}},"repoMeta":{"stars":4,"defaultBranch":"main","pushedAt":"2026-09-20T11:49:41Z"},"owner":{"login":"itsjustanks","avatarUrl":"https://avatars.githubusercontent.com/u/11022280?v=4"},"readmeText":"# 9Router Paseo plugin\n\nThe runtime ID is `agent-link-9router`. Open **9Router** in the Paseo sidebar.\n\nSee the [illustrated project README](../../README.md) for installation, the guided walkthrough,\nfeature map, Astra setup, direct versus routed providers, troubleshooting, and development.\n\n```sh\nnpm ci\nnpm run typecheck\nnpm test\nnpm run preview:ui\n```\n\nThe local UI preview uses fictional data and does not connect to a live daemon or provider.\n"},{"id":"agent-monitor","repo":"omercnet/paseo-plugins","url":"https://github.com/omercnet/paseo-plugins/tree/main/agent-monitor","package":"@omercnet/paseo-agent-monitor","npm":{"package":"@omercnet/paseo-agent-monitor","version":"1.0.1","integrity":"sha512-yZ7rf+DZfguuPiTVrYtPz91gKFTiose959v0Pm0SAXU2QdfBGYLKjk0CiiZM3M8/frWsmCS0Xp51NLuaTGYeNw==","publishedAt":"2026-09-28T11:43:09.380Z","downloadsLast30Days":4616},"name":"agent-monitor","description":"A Paseo plugin that provides a host-wide agent triage roster.","categories":["monitoring","productivity"],"platforms":["macos","linux","windows"],"caveats":["Requires Paseo 0.8.x"],"images":["https://raw.githubusercontent.com/omercnet/paseo-plugins/main/agent-monitor/docs/images/agent-monitor-roster.png","https://raw.githubusercontent.com/omercnet/paseo-plugins/main/agent-monitor/docs/images/agent-monitor-settings.png"],"themes":[],"health":{"manifestValid":true,"hasReadme":true,"hasLicense":true,"hasTests":true,"hasTypecheckScript":true,"updatedRecently":true},"scannedAt":"2026-09-29T03:52:35.116Z","addedAt":"2026-09-08T17:06:34+03:00","npmSecurity":{"status":"passed","blockingFindings":0,"advisoryFindings":0,"scannedAt":"2026-09-28T11:48:35.920Z","version":"1.0.1","integrity":"sha512-yZ7rf+DZfguuPiTVrYtPz91gKFTiose959v0Pm0SAXU2QdfBGYLKjk0CiiZM3M8/frWsmCS0Xp51NLuaTGYeNw=="},"path":"agent-monitor","version":"1.0.1","security":{"status":"passed","blockingFindings":0,"advisoryFindings":0,"scannedAt":"2026-09-28T11:48:35.920Z","commit":"38c6a71949140fd608f95ba2e3594031caa1d8f5"},"npmPreview":{"package":"@omercnet/paseo-agent-monitor","version":"1.0.0-next.163.1","integrity":"sha512-seRr8f032svlzgf3qA5vFsl3XhIXb7HDFYBxUputnPesvJDpW0U4ZjR5MMTPMkIXmzG4SpK5hUIx1SDnjG3i+A==","publishedAt":"2026-09-28T05:32:50.066Z","distTag":"next"},"npmPreviewSecurity":{"status":"passed","blockingFindings":0,"advisoryFindings":0,"scannedAt":"2026-09-28T11:48:35.920Z","version":"1.0.0-next.163.1","integrity":"sha512-seRr8f032svlzgf3qA5vFsl3XhIXb7HDFYBxUputnPesvJDpW0U4ZjR5MMTPMkIXmzG4SpK5hUIx1SDnjG3i+A=="},"author":"Omer Cohen","license":"MIT","paseoVersionRequirement":"^0.9.0 || ^0.10.0-beta.1","descriptionNodes":[{"type":"text","text":"A Paseo plugin that provides a host-wide agent triage roster."}],"caveatNodes":[[{"type":"text","text":"Requires Paseo 0.8.x"}]],"manifest":{"id":"agent-monitor","description":"A Paseo plugin that provides a host-wide agent triage roster.","requirements":{"paseo":"^0.9.0 || ^0.10.0-beta.1"}},"repoMeta":{"stars":13,"defaultBranch":"main","pushedAt":"2026-09-29T01:43:00Z"},"owner":{"login":"omercnet","avatarUrl":"https://avatars.githubusercontent.com/u/639682?v=4"},"installNotesHtml":"Requires Paseo ^0.9.0 || ^0.10.0-beta.1. Development uses the stable 0.9 SDK line.
\nInstall the published package on the daemon host:
\npaseo plugin install npm:@omercnet/paseo-agent-monitor\npaseo plugin update agent-monitor\n
","readmeText":"# agent-monitor\n\nOne roster for every agent on a daemon. Sidebar surface (`Agent monitor`) plus a global Command\nCenter item (`Open agent monitor`).\n\nAnswers \"which of my 38 agents needs me right now\" without walking the workspace tree.\n\n## Demo\n\nhttps://github.com/user-attachments/assets/3c841799-ed98-4ec4-86a0-a7917e3894fc\n\n## Screenshots\n\nAgent, project, and workspace names come from an isolated synthetic workspace. Both PNGs were\ncaptured at 2× pixel density after browser DevTools replaced the local host label and verified that\nno private organization names remained in the rendered page.\n\n### Project-first roster\n\n\n\n### Monitor settings\n\n\n\n## What it shows\n\n- Counts and filters by triage bucket: Attention, Running, Idle, Closed. Attention covers\n `requiresAttention`, `status === \"error\"`, and pending permission requests.\n- Default layout groups agents by **project**, then by workspace under each project. Open the\n gear beside Refresh for the host-native Monitor settings screen, which can switch to workspace\n groups or a flat compact list.\n- Settings also control float-pinned sorting, agent sort (triage / recently updated / title),\n collapse of matching workspace headers, density, default bucket, whether Closed stays out of\n All, and display toggles for diffs, pin markers, model, wait age, subagent counts, last error, and\n compact placement. Preferences are a typed, host-scoped document shared by connected clients.\n- Workspace headers show up to two workspace labels and current `+additions −deletions`\n (additions in the success color, deletions in danger when color diffs are on).\n- Per row: a status dot that separates errors (danger) from agents waiting on you (warning) and\n running agents (success), state and wait age on a right-aligned rail (`attentionTimestamp`,\n falling back to `updatedAt`), model, and `lastError` inline.\n- Parent rows show their subagent count; child rows use a left indent guide.\n- Text filter over title, agent id, provider, model, cwd, project, and workspace.\n- Select an agent row to open that agent, or select a workspace header (or its folder button when\n collapsed) to open its workspace through Paseo's cross-platform navigation API.\n- Archive one agent, or sweep every closed agent (two taps).\n\n## How it reads state\n\n`usePaseo().agents.list()` pages the daemon agent directory, `usePaseo().workspaces.list()` reads\nworkspace pin state, project id, and diff stats (200 per page, up to 10 pages each), and\n`usePaseo().projects.list()` supplies registered project names, including custom renames, so an\nagent whose workspace is beyond the paged workspace list still lands under its real project. Rows\nrefresh from agent, workspace, and project subscription deltas, debounced 750ms, with a 30s\nbackstop refetch. The plugin borrows the selected host's connection; it opens no socket of its own.\n\n## Limits\n\nInterrupting a turn is not part of `PaseoApi`, so archive is the only lifecycle action here.\n\n## Install\n\nRequires Paseo `^0.9.0 || ^0.10.0-beta.1`. Development uses the stable 0.9 SDK line.\n\nInstall the published package on the daemon host:\n\n```bash\npaseo plugin install npm:@omercnet/paseo-agent-monitor\npaseo plugin update agent-monitor\n```\n\n## Develop\n\n```bash\nbun install\nbun run check\nbun run test\nbun run test:coverage\nbun run typecheck\n```\n\nRelease Please maintains the version, changelog, component tag, and GitHub release from\nConventional Commits in the monorepo.\n\nThe project supports Paseo `^0.9.0 || ^0.10.0-beta.1` and pins `@getpaseo/plugin`, `@getpaseo/client`,\n`@getpaseo/protocol`, and `@getpaseo/cli` to the stable 0.9 SDK line. Renovate groups `@getpaseo/*`\nupdates so the SDKs move together.\n\nReact `19.1` and React Native `0.81` intentionally match the versions supplied by Paseo.\n"},{"id":"agents-dash-list","repo":"panrafal/paseo-plugins","url":"https://github.com/panrafal/paseo-plugins/tree/main/agents-dash-list","name":"agents-dash-list","description":"Sidebar dashboard of workspaces grouped by waiting, unread, in progress, failing, approved, idle, or closed, with archive and unread actions.","categories":["monitoring","productivity"],"platforms":[],"caveats":["Unread marks stay on the daemon that stored them and do not sync across hosts"],"images":["https://raw.githubusercontent.com/panrafal/paseo-plugins/004c6a80c6aa8e76bb563694c3eee5c2c0b0466f/agents-dash-list/images/agents-dash-list.png"],"themes":[],"health":{"manifestValid":true,"hasReadme":true,"hasLicense":true,"hasTests":false,"hasTypecheckScript":true,"updatedRecently":true},"scannedAt":"2026-09-25T20:16:15.340Z","addedAt":"2026-09-10T11:29:03+03:00","path":"agents-dash-list","version":"0.1.0","security":{"status":"failed","blockingFindings":1,"advisoryFindings":0,"scannedAt":"2026-09-25T20:04:23.597Z","commit":"004c6a80c6aa8e76bb563694c3eee5c2c0b0466f"},"author":"panrafal","license":"MIT","paseoVersionRequirement":">=0.7.2-0","descriptionNodes":[{"type":"text","text":"Sidebar dashboard of workspaces grouped by waiting, unread, in progress, failing, approved, idle, or closed, with archive and unread actions."}],"caveatNodes":[[{"type":"text","text":"Unread marks stay on the daemon that stored them and do not sync across hosts"}]],"manifest":{"id":"agents-dash-list","requirements":{"paseo":">=0.7.2-0"}},"repoMeta":{"stars":2,"defaultBranch":"main","pushedAt":"2026-09-24T07:33:21Z"},"owner":{"login":"panrafal","avatarUrl":"https://avatars.githubusercontent.com/u/1268900?v=4"},"installNotesHtml":"paseo plugin add panrafal/paseo-plugins:agents-dash-list\n
\nFrom a checkout:
\nnpm install # from the monorepo root\nnpm run typecheck\npaseo plugin install /absolute/path/to/paseo-plugins/agents-dash-list\npaseo plugin ls # expect \"running\"\n
\nAfter editing:
\nnpm run typecheck\npaseo plugin reload agents-dash-list\npaseo plugin logs agents-dash-list\n
","limitationsNotesHtml":"\n- The dash only shows a workspace's root agents as pills; subagents running inside their parent's\nworkspace contribute to that workspace's activity but do not get their own pill.
\n- Pull request state, checks, and review decision are only as fresh as what Paseo's daemon has\nalready synced from the forge; the plugin does not poll the forge itself.
\n- Unread marks and viewing settings live on the daemon the dash was opened on. Opening the dash\nfrom a different host shows that host's marks and settings instead.
\n- Workspaces on other hosts show the lettered color square rather than their project icon, and\ntheir workspace labels are colored from the opening host's catalog when the names match.
\n
","readmeText":"# agents-dash-list\n\nPaseo plugin that adds an **Agents dash** entry to the app sidebar, next to \"New workspace\",\n\"History\" and \"Schedules\". It lists every workspace on **every host you have configured** and the\nagents inside it, on one screen, grouped by what needs your attention.\n\n\n\n## Groups\n\nWorkspaces are sorted into exactly one group, in this order, and within a group by last activity\n(newest first):\n\n| Group | Shown when |\n| --- | --- |\n| Waiting for you | An agent (or the workspace itself) is waiting for a question or permission to be answered. |\n| Unread | An agent finished with new results you have not seen yet, or you marked the workspace unread from the dash. |\n| In progress | An agent is currently working. |\n| Failing | An agent errored, the pull request has a failing check, or a reviewer requested changes. |\n| Approved | The pull request is approved by reviewers and nothing above applies. |\n| Idle | Everything is done and read. |\n| Merged or closed | The pull request was merged or closed. |\n\nOnly non-empty groups are shown. Each group is a bordered section with a bold heading; pressing\nthe heading folds the group shut or open. The Unread and Approved headings also carry an\n**Archive all** button (see below).\n\n## Hosts\n\nEvery host configured in Paseo is read at once and the workspaces are merged into a single feed,\nso a group like \"Waiting for you\" holds whatever is waiting anywhere. Each row names its host on\nthe meta line, opens on that host when pressed, and is archived through that host's own\nconnection.\n\nWhen more than one host is configured the header holds a **Host** picker listing them all with\nworkspace counts; disconnected hosts are listed as `name (offline)`. Pick any number of hosts to\nnarrow the feed. A host that is disconnected or fails to answer is reported in a notice above the\nfeed while the other hosts keep working; only when *none* of the selected hosts answers does the\nwhole screen turn into an error with a Retry.\n\nOn a Paseo older than 0.8 the app exposes no host list, and the dash shows the host it was opened\non exactly as before.\n\n## Project filter\n\nThe header holds a **Project** picker listing every project that has a workspace on a visible\nhost, with workspace counts. Pick any number of projects to show only their workspaces; the count\nin the header then reads `12 of 61 workspaces`, and \"All\" in the picker (or \"Clear filters\" on the\nempty screen) clears the choice.\n\n## Remembered settings\n\nThe host choice, the project choice and the folded groups are remembered between opens and across\napp restarts. They are stored per daemon by the plugin's server entry under\n`$PASEO_HOME/plugin-data/agents-dash-list/settings.json`, so every client of that daemon opens the\ndash the way it was left.\n\n## Row anatomy\n\nEach workspace is one row:\n\n1. **Main line** — the project icon, the workspace name, the time of last activity, and (for the\n groups that have them) quick-action buttons.\n2. **Meta line** — project name, branch, host, and, when the workspace has a pull request: its\n state, checks, and review decision. Workspace labels render last, as the same colored chips\n the built-in sidebar workspace list uses.\n3. **Agents line** — a row of small pills, one per agent, each showing a shortened agent name and\n an icon for that agent's own activity (waiting, unread, working, failing, idle). Pills are\n sorted by activity, then by last activity.\n\nPressing the main line navigates to the workspace's first agent (or the workspace itself when it\nhas no agents); pressing an agent pill navigates straight to that agent. Pressing the pull request\nitem on the meta line opens it in the browser instead of navigating.\n\n## Quick actions\n\nQuick actions appear on the groups a glance can settle; the groups with live activity (Waiting,\nIn progress, Failing) are navigate-only:\n\n- **Unread** — Archive.\n- **Approved** — Archive.\n- **Idle** — Mark as unread, Archive.\n- **Merged or closed** — Archive.\n\nArchiving a workspace that has uncommitted changes or unpushed commits asks for confirmation\nfirst, listing what would be left behind.\n\nThe **Unread** and **Approved** headings also offer **Archive all**, which archives every\nworkspace currently in that group. It always asks first: the dialog says how many workspaces go\nand lists the ones that still hold uncommitted changes or unpushed commits. Workspaces are\narchived one after another and a toast reports the outcome, naming any that failed.\n\n## Unread marks\n\n\"Mark as unread\" is a marker owned by this plugin, not by Paseo itself — the built-in sidebar has\nno notion of it. The mark clears automatically the moment the workspace is opened from the dash,\nor the moment the workspace produces newer activity than the mark (a finished run, a new pull\nrequest check, and so on), whichever comes first. Marks are stored per daemon under\n`$PASEO_HOME/plugin-data/agents-dash-list/unread.json` and pruned after 90 days, or when their\nworkspace no longer exists and the dash was able to list *every* host's whole workspace directory\n(a directory too large to enumerate, or a host that did not answer, is never treated as a census,\nso no mark is dropped by mistake). The store is the one belonging to the host the dash was opened\non, and it holds marks for workspaces on the other hosts too.\n\n## How it works\n\n- The client keeps one live mirror per host: `useHosts()` lists the configured hosts and\n `getPaseoClient(serverId)` borrows each one's API, and the mirror subscribes to that host's\n workspace and agent directories (the same `list` + `subscribe` streams the rest of the app\n uses). Mirrors are reconciled as hosts connect and disconnect, so one host dropping does not\n re-seed the others. The grouped model is recomputed locally whenever any stream changes or an\n unread mark is set or cleared; each host is indexed separately, since agents and their parents\n never cross hosts.\n- The server side exposes small RPCs the client can't do itself because they need the daemon's\n filesystem: reading the workspace-label color catalog, resolving project icons (custom upload\n or automatic discovery), and reading/writing this plugin's own unread marks and viewing\n settings — all under `$PASEO_HOME` on the daemon machine (resolved the way the daemon resolves\n it, including a leading `~`).\n- Project icons in SVG or ICO form only render on web and desktop. React Native cannot decode\n those containers on iOS or Android, and a plugin cannot bring its own SVG renderer, so on\n phones and tablets those projects show the same lettered color square Paseo falls back to.\n- Plugin RPC has no cross-host form, so the server side only ever runs on the host the dash was\n opened on. Project icons are therefore resolved for that host's projects alone — rows from other\n hosts fall back to the lettered color square — while the label color catalog, unread marks and\n viewing settings from that one host apply to the whole feed.\n\n## Limitations\n\n- The dash only shows a workspace's root agents as pills; subagents running inside their parent's\n workspace contribute to that workspace's activity but do not get their own pill.\n- Pull request state, checks, and review decision are only as fresh as what Paseo's daemon has\n already synced from the forge; the plugin does not poll the forge itself.\n- Unread marks and viewing settings live on the daemon the dash was opened on. Opening the dash\n from a different host shows that host's marks and settings instead.\n- Workspaces on other hosts show the lettered color square rather than their project icon, and\n their workspace labels are colored from the opening host's catalog when the names match.\n\n## Install\n\n```bash\npaseo plugin add panrafal/paseo-plugins:agents-dash-list\n```\n\nFrom a checkout:\n\n```bash\nnpm install # from the monorepo root\nnpm run typecheck\npaseo plugin install /absolute/path/to/paseo-plugins/agents-dash-list\npaseo plugin ls # expect \"running\"\n```\n\nAfter editing:\n\n```bash\nnpm run typecheck\npaseo plugin reload agents-dash-list\npaseo plugin logs agents-dash-list\n```\n"},{"id":"agents-history","repo":"panrafal/paseo-plugins","url":"https://github.com/panrafal/paseo-plugins/tree/main/agents-history","name":"agents-history","description":"Sidebar history of every workspace and agent, including archived ones, with filters and ranked search over on-disk conversation transcripts.","categories":["monitoring","productivity"],"platforms":[],"caveats":["Reads on-disk provider transcripts; writes only its own search index under plugin-data"],"images":["https://raw.githubusercontent.com/panrafal/paseo-plugins/004c6a80c6aa8e76bb563694c3eee5c2c0b0466f/agents-history/images/agents-history.png"],"themes":[],"health":{"manifestValid":true,"hasReadme":true,"hasLicense":true,"hasTests":false,"hasTypecheckScript":true,"updatedRecently":true},"scannedAt":"2026-09-25T20:16:16.234Z","addedAt":"2026-09-10T11:29:03+03:00","path":"agents-history","version":"0.1.0","security":{"status":"failed","blockingFindings":1,"advisoryFindings":0,"scannedAt":"2026-09-25T20:04:23.597Z","commit":"004c6a80c6aa8e76bb563694c3eee5c2c0b0466f"},"author":"panrafal","license":"MIT","paseoVersionRequirement":">=0.7.2-0","descriptionNodes":[{"type":"text","text":"Sidebar history of every workspace and agent, including archived ones, with filters and ranked search over on-disk conversation transcripts."}],"caveatNodes":[[{"type":"text","text":"Reads on-disk provider transcripts; writes only its own search index under plugin-data"}]],"manifest":{"id":"agents-history","requirements":{"paseo":">=0.7.2-0"}},"repoMeta":{"stars":2,"defaultBranch":"main","pushedAt":"2026-09-24T07:33:21Z"},"owner":{"login":"panrafal","avatarUrl":"https://avatars.githubusercontent.com/u/1268900?v=4"},"installNotesHtml":"paseo plugin add panrafal/paseo-plugins:agents-history\n
\nFrom a checkout:
\nnpm install # from the monorepo root\nnpm run typecheck\npaseo plugin install /absolute/path/to/paseo-plugins/agents-history\npaseo plugin ls # expect \"running\"\n
\nAfter editing:
\nnpm run typecheck\npaseo plugin reload agents-history\npaseo plugin logs agents-history # \"search index at …\" and \"index sync\" lines once the surface is opened\n
","limitationsNotesHtml":"\n- Only providers that keep a transcript file on disk are searchable (see the table above).
\n- Conversation files that have been deleted, or a Claude session directory Paseo cannot map to\nthe agent's directory, make that agent \"not searchable\"; the census still lists it.
\n- The index holds what people and agents said. Tool input and output, injected context, and\nprovider bookkeeping are not indexed; use Regex to grep those.
\n- Ranked search folds case and stems words with the English porter stemmer; it does not match\ninside words (
beat does not find heartbeat) and cannot take a regular expression. \n- A transcript's last line is indexed once its newline is written; a message still being\nstreamed appears after the next sync.
\ngrep -i folds case according to the daemon's locale. A grep hit inside a very long line (a\nlarge tool result) shows a snippet cut from the first megabyte of that line. grep returns\nthe first hits in file order, and a query that also appears in a record's fields (a branch\nname, a directory, a session id) matches every line of that transcript; such hits are labelled\nmeta and shown only when nothing said in the conversation matched.- A grep-backed search needs
grep on the daemon's PATH. Windows ships none, so when PATH\nhas no grep the one bundled with Git for Windows is used, looked up under %ProgramFiles%,\n%ProgramFiles(x86)%, %LOCALAPPDATA%, scoop, and C:\\msys64. On a host with neither,\nRanked search still … \n
","readmeText":"# agents-history\n\nPaseo plugin that adds an **Agents history** entry to the app sidebar. It lists every workspace\nthe selected daemon has ever had, archived ones included, with the agents that ran in each, and\nsearches what was said in those conversations through a ranked full-text index of the providers'\ntranscript files on the daemon host (falling back to `grep -E` over the raw transcripts for\nregular expressions, and wherever the index is not available yet — see **Limitations**).\n\nPaseo's own History screen searches agent titles and hides archived workspaces; this surface is\nfor finding the workspace where something was discussed weeks ago.\n\n\n\n## What is listed\n\nEvery workspace in the daemon's registry, newest activity first, grouped into **Active** and\n**Archived** when the archived filter is set to all. Each card carries:\n\n1. **Head** — the workspace title (its name when it has no title), an amber `archived` badge\n when the workspace or its project is archived, and how long ago anything in it last moved.\n Below, each with a small icon: project, branch, worktree name, agent count, and labels. Pressing the head opens\n the workspace; for an archived one Paseo shows its recovery screen and offers to unarchive.\n2. **Agent rows** — one per agent, archived ones included: a status glyph (a spinner while\n running), the title, an `archived` badge, the last activity, and under it, each with a small\n icon, provider, model, and last status.\n Pressing an active row opens the agent. Pressing an archived row asks whether to restore it.\n **Restore and open** restores its provider session, then opens that agent; **Cancel** leaves\n it archived. A failed restore shows an error and keeps the dialog open for retry.\n\nAgents whose workspace record no longer exists are grouped under a \"Workspace record missing\"\ncard so they stay reachable.\n\nThe header sums what is showing: how many workspaces and agents, and, with filters on, out of how\nmany.\n\n## Search\n\nTyping in the search box does two things:\n\n- **Immediately**, the list narrows to workspaces whose name, title, branch, directory, project,\n labels, or agent titles contain the text.\n- **After a short pause** (or on Enter), the daemon searches every conversation of the agents that\n pass the other filters and the list is reordered: workspaces with the best match first, and\n inside each, the best-matching agents first. Under a matching agent up to three lines appear:\n who said it (`you` or `agent`), the text around the match, and the match itself in bold.\n \"+ N more matching lines\" means more exist than are shown.\n\n**Ranked** (the default) answers from the search index. Every word must occur, in any order and\nany form (`schedule` finds `scheduled`, `heartbeat` finds `heartbeats`); the last word may be a\nprefix so results fill in while typing. When no conversation has every word, any word is accepted\nand the note under the filters says so. Names count more than what was said: a hit in an agent\ntitle, workspace name, branch, project, label, directory segment, model, or provider is weighted\nabove hits in the conversation text, and such agents show \"matches workspace name, branch\" above\ntheir snippets. Letter case is ignored, so **Aa** is muted.\n\n**Regex** treats the text as an extended regular expression and runs `grep -E` over the raw\ntranscript files instead; **Aa** then makes it case-sensitive. Grep also answers when the index\nhas not been built yet (the note says so) or when the daemon's Node.js has no SQLite with FTS5.\nGrep hits are listed in file order, not ranked, and also cover tool output and provider\nbookkeeping (`tool` and `meta` lines), which the index leaves out.\n\nA line under the filters says how many conversations matched across how many agents, how many\nagents could not be searched or are not indexed yet, and whether the search was cut short. An\ninvalid regular expression is reported there as well. A second line shows the state of the index.\n\n## Filters\n\n- **Archived** — all, active only, or archived only. A workspace counts as archived when it or\n its project is.\n- **Provider** — pick any number of providers, with agent counts; a workspace stays listed when\n at least one of its agents matches, and only those agents are shown.\n- **Project** — pick any number of projects, with workspace counts.\n- **Label** — pick any number of workspace labels, with workspace counts; a workspace needs at\n least one of them.\n- **Period** — last 24 hours, 7, 30, or 90 days, or any time, on the latest activity of the\n workspace or any of its agents.\n\nOn a desktop-sized window the dropdowns open as popovers under their trigger; on a phone they\nopen in Paseo's sheet.\n\nThe search text and filter choices are kept while you navigate around the app, so opening a\nworkspace you found and coming back shows the same results; they reset when the app restarts.\n\n## Where the history comes from\n\nPaseo does not store conversations itself; it replays the provider's own transcript. The plugin\nsearches those files directly:\n\n| Provider | File |\n| ----------------- | ----------------------------------------------------------------------------------------------------- |\n| Claude Code | `~/.claude/projects//.jsonl` plus the subagent files under `/subagents/` (`CLAUDE_CONFIG_DIR` respected) |\n| Codex | `~/.codex/sessions//rollout-*-.jsonl`, or `~/.codex/archived_sessions/` once the agent is archived (`CODEX_HOME` respected) |\n| OMP, Pi | the session file the daemon recorded as the agent's native handle |\n| Cursor, Kilo, Copilot, other ACP providers | nothing on disk; these agents are listed but say \"keeps no conversation file to search\" during a search |\n\n## How it works\n\n- The plugin SDK lists only live workspaces, so the server entry reads the daemon's own records:\n `$PASEO_HOME/projects/workspaces.json`, `projects.json`, and one JSON file per agent under\n `$PASEO_HOME/agents`. Files are re-parsed only when their size or modification time changes;\n the client re-reads the census every 30 seconds. Agent records also hold provider credentials;\n the server never returns or logs those fields.\n- Typing is debounced by 400 ms; a newer search cancels the one still running; at most two run\n at once; a grep search is cut short after 20 seconds.\n- Everything is scoped to the host you are viewing; switching hosts reloads the census.\n\n### Search index\n\n- The index is one SQLite file, `$PASEO_HOME/plugin-data/agents-history/search.sqlite`, using\n Node's built-in `node:sqlite` and its FTS5 extension (present in Node 24 and in Node 22.16 or\n later). Nothing is installed. It holds one row per user or assistant message (`chunks`) and one\n row of metadata per agent (`agent_meta`: title, workspace, project, branch, labels, paths,\n model, provider), both with the porter stemmer.\n- It is built the first time the surface is opened and brought up to date every time the surface\n refreshes its census (every 30 seconds while open) or a ranked search finds it stale, at most\n once per 15 seconds. Nothing runs while the surface is closed, and nothing watches the files.\n A schema bump — a change to how a line is parsed — deletes the file and rebuilds it from the\n transcripts on the next open, because a file already consumed to its end would otherwise never\n be read again.\n- Transcripts are append-only, so each file remembers how many bytes were consumed and a later\n sync reads only what was added; a file that shrank or was replaced is re-read from the start.\n Work happens in small batches, each its own transaction, with the event loop released in\n between, so searches answer while indexing runs and a plugin reload stops it within a batch.\n Files, agents, and messages that disappear are pruned.\n- A search runs two FTS5 queries: one over the messages (every word required, prefix on the last\n one; relaxed to any word when nothing matched) and one over the agent metadata with per-column\n weights (title 6, workspace 5, project, branch, and labels 4, path 2, model and provider 1.5).\n An agent's score is five times its metadata score plus its best message score plus a share of\n its next four. Snippets come from FTS5's `snippet()`.\n- A Node.js without `node:sqlite` or without FTS5 leaves every search on grep; the note under the\n filters says so.\n\n## Limitations\n\n- Only providers that keep a transcript file on disk are searchable (see the table above).\n- Conversation files that have been deleted, or a Claude session directory Paseo cannot map to\n the agent's directory, make that agent \"not searchable\"; the census still lists it.\n- The index holds what people and agents said. Tool input and output, injected context, and\n provider bookkeeping are not indexed; use **Regex** to grep those.\n- Ranked search folds case and stems words with the English porter stemmer; it does not match\n inside words (`beat` does not find `heartbeat`) and cannot take a regular expression.\n- A transcript's last line is indexed once its newline is written; a message still being\n streamed appears after the next sync.\n- `grep -i` folds case according to the daemon's locale. A grep hit inside a very long line (a\n large tool result) shows a snippet cut from the first megabyte of that line. `grep` returns\n the first hits in file order, and a query that also appears in a record's fields (a branch\n name, a directory, a session id) matches every line of that transcript; such hits are labelled\n `meta` and shown only when nothing said in the conversation matched.\n- A grep-backed search needs `grep` on the daemon's `PATH`. Windows ships none, so when `PATH`\n has no `grep` the one bundled with Git for Windows is used, looked up under `%ProgramFiles%`,\n `%ProgramFiles(x86)%`, `%LOCALAPPDATA%`, `scoop`, and `C:\\msys64`. On a host with neither,\n Ranked search still works once the index is built, but the first search after a fresh install\n fails with a message saying which executable is missing. Set `AGENTS_HISTORY_GREP` to a grep\n binary to override the search.\n- Grep is handed one command line per chunk of transcript files. Windows rejects a command line\n over 32,767 characters, so the chunk budget is smaller there and a single agent holding more\n files than one command line can carry is split across chunks.\n- The plugin never archives, unarchives, or deletes anything. Its only writes are its own index\n file, which can be deleted at any time and is rebuilt on the next open.\n- Browsing and searching write only the plugin's index, which can be deleted and rebuilt.\n Confirming **Restore and open** uses the daemon-local Paseo CLI (`agent reload`) to unarchive\n the selected agent and restore its provider session. This may also recover its owning workspace.\n The CLI must be available as `paseo` or through `PASEO_CLI_PATH`.\n\n## Install\n\n```bash\npaseo plugin add panrafal/paseo-plugins:agents-history\n```\n\nFrom a checkout:\n\n```bash\nnpm install # from the monorepo root\nnpm run typecheck\npaseo plugin install /absolute/path/to/paseo-plugins/agents-history\npaseo plugin ls # expect \"running\"\n```\n\nAfter editing:\n\n```bash\nnpm run typecheck\npaseo plugin reload agents-history\npaseo plugin logs agents-history # \"search index at …\" and \"index sync\" lines once the surface is opened\n```\n"},{"id":"agy-provider","repo":"3ae3ae/paseo-plugin-agy-provider","url":"https://github.com/3ae3ae/paseo-plugin-agy-provider","name":"agy-provider","description":"Paseo 0.8+ provider plugin for Google's official Antigravity ACP server","categories":["provider"],"platforms":["macos"],"caveats":["Requires Paseo 0.8.x and the official ACP server; the login action also needs Node.js 22.18+ on the daemon host.","Log in from the workspace Command Center; API-key authentication can instead use the official server settings.","Official server 1.1.1 ignores Paseo system prompts; workflows relying on them are unsupported.","Real-agent verification: macOS ARM64 only; see README for other official distributions.","The current shim/server can display duplicate tool rows and split streamed text."],"images":["https://raw.githubusercontent.com/3ae3ae/paseo-plugin-agy-provider/899a1f4ea222beb974306d6ea672e2330dc402eb/images/compact.jpg","https://raw.githubusercontent.com/3ae3ae/paseo-plugin-agy-provider/899a1f4ea222beb974306d6ea672e2330dc402eb/images/conversation.jpg","https://raw.githubusercontent.com/3ae3ae/paseo-plugin-agy-provider/899a1f4ea222beb974306d6ea672e2330dc402eb/images/demo.gif","https://raw.githubusercontent.com/3ae3ae/paseo-plugin-agy-provider/899a1f4ea222beb974306d6ea672e2330dc402eb/images/models.jpg"],"themes":[],"health":{"manifestValid":true,"hasReadme":true,"hasLicense":true,"hasTests":true,"hasTypecheckScript":true,"updatedRecently":true},"scannedAt":"2026-09-25T20:16:17.080Z","addedAt":"2026-09-11T10:22:44Z","version":"0.1.2","security":{"status":"passed","blockingFindings":0,"advisoryFindings":0,"scannedAt":"2026-09-25T20:04:23.597Z","commit":"899a1f4ea222beb974306d6ea672e2330dc402eb"},"author":"3ae3ae","license":"MIT","paseoVersionRequirement":">=0.8.0","descriptionNodes":[{"type":"text","text":"Paseo 0.8+ provider plugin for Google's official Antigravity ACP server"}],"caveatNodes":[[{"type":"text","text":"Requires Paseo 0.8.x and the official ACP server; the login action also needs Node.js 22.18+ on the daemon host."}],[{"type":"text","text":"Log in from the workspace Command Center; API-key authentication can instead use the official server settings."}],[{"type":"text","text":"Official server 1.1.1 ignores Paseo system prompts; workflows relying on them are unsupported."}],[{"type":"text","text":"Real-agent verification: macOS ARM64 only; see README for other official distributions."}],[{"type":"text","text":"The current shim/server can display duplicate tool rows and split streamed text."}]],"manifest":{"id":"agy-provider","requirements":{"paseo":">=0.8.0"}},"repoMeta":{"stars":5,"defaultBranch":"main","pushedAt":"2026-09-24T12:27:44Z"},"owner":{"login":"3ae3ae","avatarUrl":"https://avatars.githubusercontent.com/u/83870598?v=4"},"installNotesHtml":"1. Install the official server
\nOn the Paseo daemon host, download your platform's archive from the official ACP Registry. Extract the entire archive, keeping the companion localharness_external executable beside the server. The ordinary agy CLI does not replace this server. The plugin has no macOS-only restriction; it selects the command for the daemon host on macOS, Linux, or Windows.
\n\n\n\n| Platform | \nExecutable | \nPlugin-supplied arguments | \n
\n\n\n\n| macOS ARM64 | \nagy_acp_server.par | \nNone | \n
\n\n| Linux x64 / ARM64 | \nagy_acp_server.par | \n--uid= | \n
\n\n| Windows x64 / ARM64 | \nagy_acp_server.exe | \nNone | \n
\n\n
\nAdd the extraction directory to the daemon's PATH, or set PASEO_AGY_ACP_BIN to the executable's absolute path. For example:
\nexport PASEO_AGY_ACP_BIN=\"$HOME/.local/share/antigravity-acp/agy_acp_server.par\"\n
\nSet this in the environment that starts the daemon; exporting it in another terminal does not change a running daemon. Restart the daemon after changing its environment. The login terminal also needs Node.js 22.18+ and the same server configuration.
\n2. Install the plugin
\npaseo plugin add 3ae3ae/paseo-plugin-agy-provider\n
\nFor an existing installation, run paseo plugin update agy-provider. Both the client and daemon must use Paseo 0.8 or later and a plugin revision with the matching version requirement. The login menu requires plugin…
","limitationsNotesHtml":"\n- Real-agent verification covers macOS ARM64 and personal Google OAuth. Linux/Windows sessions, API-key and enterprise authentication, and physical mobile devices are unverified.
\n- In-place steering and structured output guarantees are not implemented.
\n- The current server/shim can display duplicate tool rows.
\n- The login action requires an open workspace and the default plugin ID
agy-provider. For a remote daemon, authentication runs on that host; the helper does not relay OAuth callbacks to another machine. \n
\nSee VERIFICATION.md for tested behavior and versions.
","readmeText":"# agy-provider\n\nUse Google's official **Antigravity ACP server** in [Paseo](https://paseo.sh/docs/plugins/providers) **0.8 and later** (`>=0.8.0`), including **0.9.0**. This is a community-maintained plugin. Real-agent verification covers 0.8.0; the stable 0.9.0 SDK has passed type and automated compatibility checks, with live sessions still unverified. Later versions are allowed by the manifest but have not been verified.\n\n> [!IMPORTANT]\n> **Paseo's injected system prompts and the instructions they contain are not applied.**\n> Official ACP server 1.1.1 ignores these instructions. Workflows that rely on them are unsupported by this plugin. Review this limitation before installing.\n\n**Known issue in Paseo 0.8.0:** streamed replies can appear as separate blocks with large gaps, splitting words, lists, and Markdown formatting ([paseo#4699](https://github.com/getpaseo/paseo/issues/4699)). **Paseo 0.9.0 includes the upstream ACP fix** ([#4701](https://github.com/getpaseo/paseo/pull/4701)); the original Antigravity session has not been reverified. The fix comes from the daemon's ACP runtime; updating this plugin alone does not fix a 0.8.0 daemon.\n\n\n\nCaptured model picker and conversation in Paseo 0.8.0. [Desktop](images/conversation.jpg) · [Compact layout](images/compact.jpg)\n\n## Installation\n\n### 1. Install the official server\n\nOn the **Paseo daemon host**, download your platform's archive from the [official ACP Registry](https://github.com/agentclientprotocol/registry/blob/main/antigravity-acp/agent.json). Extract the entire archive, keeping the companion `localharness_external` executable beside the server. The ordinary `agy` CLI does not replace this server. The plugin has no macOS-only restriction; it selects the command for the daemon host on macOS, Linux, or Windows.\n\n| Platform | Executable | Plugin-supplied arguments |\n| --- | --- | --- |\n| macOS ARM64 | `agy_acp_server.par` | None |\n| Linux x64 / ARM64 | `agy_acp_server.par` | `--uid=` |\n| Windows x64 / ARM64 | `agy_acp_server.exe` | None |\n\nAdd the extraction directory to the daemon's PATH, or set `PASEO_AGY_ACP_BIN` to the executable's absolute path. For example:\n\n```sh\nexport PASEO_AGY_ACP_BIN=\"$HOME/.local/share/antigravity-acp/agy_acp_server.par\"\n```\n\nSet this in the environment that starts the daemon; exporting it in another terminal does not change a running daemon. Restart the daemon after changing its environment. The login terminal also needs **Node.js 22.18+** and the same server configuration.\n\n### 2. Install the plugin\n\n```sh\npaseo plugin add 3ae3ae/paseo-plugin-agy-provider\n```\n\nFor an existing installation, run `paseo plugin update agy-provider`. Both the client and daemon must use Paseo 0.8 or later and a plugin revision with the matching version requirement. The login menu requires plugin v0.1.1+; older revisions restricted to 0.8 must be updated for 0.9.\n\n### 3. Log in\n\n1. Open a workspace in Paseo.\n2. Open the **Command Center** (`Cmd+K` on macOS) and choose **Antigravity: Log in with Google**.\n3. Complete Google's browser sign-in. The **Antigravity login** workspace terminal shows progress and the result; use its sign-in link if the browser does not open.\n4. If the model list still shows an earlier authentication error, reload `agy-provider` in Settings → Plugins.\n\n**No separate clone or npm install is needed.** The action uses the helper already included in the installed plugin.\n\nThe official server owns authentication and credential storage. Existing ACP authentication can be reused; ordinary `agy` CLI login alone is insufficient. If you override `GEMINI_HOME`, use the same value for the daemon and login terminal.\n\n### Gemini API key instead of Google sign-in\n\nSet `GEMINI_API_KEY` securely in the daemon's launch environment. Merge this into `~/.gemini/antigravity-acp/settings.json`, preserving other settings:\n\n```json\n{\n \"auth\": { \"type\": \"gemini-api-key\" }\n}\n```\n\nUse the corresponding path under `GEMINI_HOME` if overridden, and restart the daemon to load the environment. Both the key and `auth.type` are required. This route needs no browser or login-helper invocation. See [Google's authentication options](https://antigravity.google/docs/ide/extensions/zed).\n\n## Usage\n\nChoose **Antigravity** in the model picker, or run:\n\n```sh\npaseo run --provider agy \"Explain this project's entry point.\"\n```\n\nModels and modes come from the official server and your account.\n\n```sh\npaseo plugin update agy-provider\npaseo plugin reload agy-provider\npaseo plugin remove agy-provider\n```\n\nUpdate the official server separately. Removing the plugin leaves Google's server, credentials, and conversations intact.\n\n- **Paseo 0.8:** release-pinned installations do not track updates; remove and re-add with a newer `--ref` to change the pin.\n- **Paseo 0.9:** `plugin update` previews the proposed revision and asks for confirmation. Add `--check` to preview only or `--yes` to approve without a prompt. Git updates target the default branch HEAD regardless of the initial `--ref`; that selector is not a persistent pin. To select a specific tag or commit, run `paseo plugin update agy-provider --ref ` (applies without another confirmation). See the [update reference](https://paseo.sh/docs/plugins/reference#cli-reference).\n\n## Limitations\n\n- Real-agent verification covers macOS ARM64 and personal Google OAuth. Linux/Windows sessions, API-key and enterprise authentication, and physical mobile devices are unverified.\n- In-place steering and structured output guarantees are not implemented.\n- The current server/shim can display duplicate tool rows.\n- The login action requires an open workspace and the default plugin ID `agy-provider`. For a remote daemon, authentication runs on that host; the helper does not relay OAuth callbacks to another machine.\n\nSee [VERIFICATION.md](VERIFICATION.md) for tested behavior and versions.\n\n## Troubleshooting\n\n| Symptom | Check |\n| --- | --- |\n| Executable not found | Daemon PATH or `PASEO_AGY_ACP_BIN`. |\n| `Internal error` opening a session | Keep the companion executable beside the server; extract the full archive. |\n| `Authentication required` | Use the login action, or check API-key configuration. |\n| Login menu missing | Update the plugin, use a Paseo 0.8+ client, and open a workspace. |\n| Plugin rejected on Paseo 0.9 | Update to a plugin revision whose manifest requires `>=0.8.0`; check the client and daemon versions. |\n| No models after login | Reload the plugin; check `paseo provider diagnostic agy`. |\n\nPlugin startup logs: `paseo plugin logs agy-provider`. Remove credentials, OAuth links, and private content before sharing logs.\n\n## Development\n\n```sh\nnpm ci\nnpm run typecheck\nnpm test\npaseo plugin install /absolute/path/to/paseo-plugin-agy-provider\n```\n\nThe provider uses `runAcpProvider()`; the login action reuses Paseo's terminal. There are no plugin runtime dependencies or build steps. The development SDK stays at 0.8.0 to check the oldest supported API; Paseo supplies the runtime SDK. CI runs type checks and tests against SDKs 0.8.0 and 0.9.0 on macOS, Linux, and Windows. Keep the manifest compatible with 0.8: its strict schema rejects the `description` field introduced in 0.9.\n\n[Contributing](CONTRIBUTING.md) · [Code of Conduct](CODE_OF_CONDUCT.md) · [Security reports](SECURITY.md)\n\n## License\n\n[MIT](LICENSE) covers this repository's code. Google's proprietary server is installed separately under [Google's terms](https://antigravity.google/terms).\n"},{"id":"antigravity-cli","repo":"lefos13/paseo-plugin-antigravity-cli","url":"https://github.com/lefos13/paseo-plugin-antigravity-cli","package":"paseo-plugin-antigravity-cli","npm":{"package":"paseo-plugin-antigravity-cli","version":"0.6.0","integrity":"sha512-rRPnvPbi6V3OV5xkOJZ/DqLbl/j0cCh3dl8vc6hDYcHWsk2k4fdunj4GnQ1rZPzH/0ipOs9zbNFcN5Z2pGnpNA==","publishedAt":"2026-09-28T11:49:07.573Z","downloadsLast30Days":1036},"name":"antigravity-cli","description":"Antigravity CLI (agy) as a Paseo provider: streaming turns, tool rows with diffs, images, structured output, skills and slash commands, question cards for ask_question, conversation import, opt-in MCP sharing, and multiple accounts with per-account usage quota.","categories":["provider"],"platforms":[],"caveats":["Requires Google's Antigravity CLI (agy) installed and signed in on the daemon host; built against agy 1.2.10.","No steering, tool-approval prompts, or revert: agy's stream-json mode does not expose them.","Sharing Paseo's MCP tools is opt-in and writes a credential-bearing .agents/mcp_config.json (locally git-excluded).","Plan mode is enforced by the plugin (instruction plus approval prompt); agy's headless --mode plan does not block edits.","Verified end to end on macOS only."],"images":["https://raw.githubusercontent.com/lefos13/paseo-plugin-antigravity-cli/6b559c4f9408289f0c3643a608325c010a97fcbf/images/01-chat.jpg","https://raw.githubusercontent.com/lefos13/paseo-plugin-antigravity-cli/6b559c4f9408289f0c3643a608325c010a97fcbf/images/02-slash-commands.jpg","https://raw.githubusercontent.com/lefos13/paseo-plugin-antigravity-cli/6b559c4f9408289f0c3643a608325c010a97fcbf/images/03-provider-enabled.jpg","https://raw.githubusercontent.com/lefos13/paseo-plugin-antigravity-cli/6b559c4f9408289f0c3643a608325c010a97fcbf/images/04-models.jpg","https://raw.githubusercontent.com/lefos13/paseo-plugin-antigravity-cli/6b559c4f9408289f0c3643a608325c010a97fcbf/images/05-multiple-accounts.jpg"],"themes":[],"health":{"manifestValid":true,"hasReadme":true,"hasLicense":true,"hasTests":true,"hasTypecheckScript":true,"updatedRecently":true},"scannedAt":"2026-09-28T12:10:51.756Z","addedAt":"2026-09-24T20:52:43+01:00","npmSecurity":{"status":"passed","blockingFindings":0,"advisoryFindings":0,"scannedAt":"2026-09-28T12:10:34.337Z","version":"0.6.0","integrity":"sha512-rRPnvPbi6V3OV5xkOJZ/DqLbl/j0cCh3dl8vc6hDYcHWsk2k4fdunj4GnQ1rZPzH/0ipOs9zbNFcN5Z2pGnpNA=="},"version":"0.6.0","security":{"status":"passed","blockingFindings":0,"advisoryFindings":0,"scannedAt":"2026-09-28T11:48:35.920Z","commit":"6b559c4f9408289f0c3643a608325c010a97fcbf"},"author":"lefos13","license":"MIT","paseoVersionRequirement":">=0.9.1","descriptionNodes":[{"type":"text","text":"Antigravity CLI (agy) as a Paseo provider: streaming turns, tool rows with diffs, images, structured output, skills and slash commands, question cards for ask_question, conversation import, opt-in MCP sharing, and multiple accounts with per-account usage quota."}],"caveatNodes":[[{"type":"text","text":"Requires Google's Antigravity CLI (agy) installed and signed in on the daemon host; built against agy 1.2.10."}],[{"type":"text","text":"No steering, tool-approval prompts, or revert: agy's stream-json mode does not expose them."}],[{"type":"text","text":"Sharing Paseo's MCP tools is opt-in and writes a credential-bearing .agents/mcp_config.json (locally git-excluded)."}],[{"type":"text","text":"Plan mode is enforced by the plugin (instruction plus approval prompt); agy's headless --mode plan does not block edits."}],[{"type":"text","text":"Verified end to end on macOS only."}]],"manifest":{"id":"antigravity-cli","requirements":{"paseo":">=0.9.1"}},"repoMeta":{"stars":1,"defaultBranch":"main","pushedAt":"2026-09-28T11:46:52Z"},"owner":{"login":"lefos13","avatarUrl":"https://avatars.githubusercontent.com/u/71150524?v=4"},"installNotesHtml":"From npm, from GitHub, or by pasting either source into Settings → Plugins → Plugin source:
\npaseo plugin install npm:paseo-plugin-antigravity-cli\npaseo plugin install github:lefos13/paseo-plugin-antigravity-cli\n
\nCheck it with paseo plugin ls; antigravity-cli should be running. agy --version must print and\nagy must be signed in, and then pick Antigravity when you start a new agent. The sidebar entry\nAntigravity accounts picks which account new agents run under — see\nMultiple accounts.
\nUnlike agy-provider, which adapts Antigravity's ACP\nserver through Paseo's ACP shim, this plugin drives the agy CLI directly over its documented\nstream-json mode. The agy it launches is the first of providerOptions.agyPath,\nPASEO_ANTIGRAVITY_BIN, ~/.local/bin/agy (checked explicitly, because a daemon started by a GUI app\noften has no such directory on PATH), then agy from PATH.
","limitationsNotesHtml":"\n--sandbox is not demonstrated. The flag is accepted and the turn runs, but with permissive\nAntigravity settings a write outside the workspace still succeeded, so the plugin does not claim the\nrestriction holds.- Edit diffs are reconstructed from file snapshots, because the stream names only the edited file;\na file the plugin cannot read, or one that did not change, leaves the row without a diff.
\n- Transient 503s fail the turn with
code: \"unavailable\", and an error result ends the CLI\nprocess, which the next turn relaunches on the same conversation. \n- Imported conversations resume from
session.list, but their earlier turns are not replayed. \n- The command list is read from disk, not from the CLI, so a skill the CLI would refuse to load can\nappear in the picker, and a command it no longer expands is sent as ordinary text.
\n- Subagent sessions are read-only in Paseo, and rely on agy's undocumented transcript file: if a\nCLI update changes it, subagents fall back to rows without a child session.
\n- Questions are relayed after the fact. The plugin stops the CLI once agy has already answered\n
User Skipped, so any tool the model called in the same step as the question has already run. The\ncard lives in memory: a plugin reload or daemon restart drops it, and you answer in chat instead.\nQuestions asked inside a subagent, and on a structured-output turn, are not relayed, so agy settles\nthem itself. The relay reads agy's undocumented… \n
","readmeText":"# Antigravity CLI provider for Paseo\n\nRuns Google's official Antigravity CLI (`agy`) as a Paseo provider: Paseo owns the session, the CLI\ndoes the work, and every turn, tool call, and message is rendered from the CLI's `stream-json`\nprotocol. Nothing about Antigravity is reimplemented — the plugin spawns the `agy` binary that is\nalready installed and signed in on your machine.\n\n- Provider id: `antigravity-cli`\n- Requires: Paseo ≥ 0.9.1 (provider protocol version 1), Node 24 for the plugin process, and\n Antigravity CLI 1.2.9–1.2.11 for the behaviour described below. The plugin also ships a client\n entry (the [accounts screen](#multiple-accounts)), so the connected Paseo **app** must satisfy the\n same minimum — a compatible daemon does not make an older app compatible.\n\n## Screenshots\n\n\n\n\n\n\n\n## Install\n\nFrom npm, from GitHub, or by pasting either source into **Settings → Plugins → Plugin source**:\n\n```\npaseo plugin install npm:paseo-plugin-antigravity-cli\npaseo plugin install github:lefos13/paseo-plugin-antigravity-cli\n```\n\nCheck it with `paseo plugin ls`; `antigravity-cli` should be `running`. `agy --version` must print and\n`agy` must be signed in, and then pick **Antigravity** when you start a new agent. The sidebar entry\n**Antigravity accounts** picks which account new agents run under — see\n[Multiple accounts](#multiple-accounts).\n\nUnlike [`agy-provider`](https://paseo.cafe/plugins/agy-provider), which adapts Antigravity's ACP\nserver through Paseo's ACP shim, this plugin drives the `agy` CLI directly over its documented\n`stream-json` mode. The `agy` it launches is the first of `providerOptions.agyPath`,\n`PASEO_ANTIGRAVITY_BIN`, `~/.local/bin/agy` (checked explicitly, because a daemon started by a GUI app\noften has no such directory on `PATH`), then `agy` from `PATH`.\n\n## What the plugin supports\n\nOne `agy` process per session: each prompt is one NDJSON turn and exactly one `result` back, and a\nprompt sent while a turn runs is queued by the CLI as the next turn. Model, tier, mode, and settings\nare launch flags, so a change restarts the CLI on the next turn and resumes the same conversation;\nAntigravity conversations can be imported read-only, the conversation id agy reports is persisted,\neach subagent becomes a child session ([Subagents](#subagents)), and `permission` covers plan approval\nand the questions agy cannot ask ([Questions](#questions-ask_question)). Images go over by file,\nbecause a `stream-json` turn carries text only.\n\nModels come from `agy models` (cached ten minutes; `force` rediscovers), so the composer offers one\nmodel per family with the tiers that family has — High, Medium and Low today. `providerOptions.effort`\nis described in the table below.\n\nModes are *Default* (review file writes before they run), *Accept edits*, and *Plan*; tool rows cover\nshell commands, file edits with a diff, searches, web fetches, and MCP tool calls.\n\n### Plan mode\n\nagy's own `--mode plan` is never passed: on 1.2.11 it either has no effect, while slash-command\nexpansion is disabled, or approves its own plan review — nobody can answer that in a headless run —\nand implements in the same turn. Plan mode is therefore the plugin's own: a plan-mode turn is prefixed\nwith a `` block telling the model to investigate read-only and end with a plan, and its last\nanswer is then offered as a plan (`kind: \"plan\"` permission) with **Implement** and **Keep planning**.\n*Implement* switches to *Accept edits* and sends `The plan is approved. Implement it now.`; *Keep\nplanning*, or another message, withdraws it. It is an instruction, not a sandbox: a model that ignores\nit can still write files.\n\n### Questions (`ask_question`)\n\nHeadless agy never shows an `ask_question` dialog. It answers the call itself with `User Skipped` and\nthe model carries on, making the choice on its own. That is what happens to `/teamwork-preview`'s\nteam-scale question, `/grill-me`'s interview, `/schedule`'s time, and any question the model decides\nto ask. The stream reports the call only as an `unknown` step, so the plugin reads the question from\nthe conversation's transcript. It then stops the CLI before the model acts on the skip, completes the\nturn, and offers the questions as Paseo's question card (`kind: \"question\"`): single or multi-select,\nalways with a write-in answer.\n\n- **Answer:** the answers go back as the next turn of the same conversation, in a fresh CLI. The model\n is told the skip came from the CLI, not from you. A command turn's answer is a plain message.\n- **Dismiss:** nothing is sent. The model has \"User Skipped\", and the next message is yours.\n- **Another message instead:** the card is withdrawn and the message is sent as usual. The same\n happens to a question whose turn already had a message queued behind it: that message runs, and\n the question is not asked.\n\nIn Plan mode the question comes first and the plan card follows the answer turn.\n\n### Background commands\n\nWhen the model starts a long-running command in the background, agy holds back every later step until\nit exits. After 5 s of that the plugin reads the conversation's own transcript, publishes the held\nsteps, and completes the turn as soon as the transcript shows the final answer. The CLI holding the\ncommand is left running, so the server stays up (a notice says so), but it cannot take another turn:\nyour next message stops it, and the command with it, and resumes the conversation in a fresh CLI.\n\n## Subagents\n\n`invoke_subagent` starts each subagent as its own conversation while the parent turn stays open. The\nplugin shows a **row per subagent** in the parent timeline (type, role, prompt, *running* until it\nfinishes) and a **child session per subagent** following the transcript agy names for it: the prompt,\neach tool call with its result, and the final answer. A child spawned with `Workspace: branch` runs in\nits own git worktree, which becomes that child session's working directory; a `Workspace: inherit`\nchild keeps the parent's.\n\nThe transcript is agy-internal and undocumented, so a child session is best-effort: a missing,\nunreadable, or unrecognised transcript leaves the row above in place and never affects the parent turn.\nFollowing stops when the subagent finishes, the session closes, or the turn is interrupted or fails.\n\n## Slash commands\n\nThe composer's picker lists the commands this plugin has verified the CLI expands in `stream-json`\nturns; a command is a *turn* on a CLI launched without `--disable-slash-commands`, and the next plain\nturn relaunches with it.\n\n| Command | Source |\n|---|---|\n| `/plan`, `/goal`, `/grill-me`, `/teamwork-preview`, `/learn`, `/schedule`, `/boost`, `/browser` | The CLI's own workflows. `/learn` records a behaviour in the workspace's `GEMINI.md`, `/schedule` sets up a recurring run, and `/boost` and `/browser` are the deep-thinking and browser-agent flows. |\n| `/` | A skill, either in the workspace's customization roots (`.agents/skills//SKILL.md`, and the same under `.agent/`, `_agents/`, `_agent/`) or installed for every workspace under `~/.gemini/antigravity-cli/skills/`, `~/.gemini/config/skills/`, `~/.gemini/skills/`, in that precedence. The name is the skill's frontmatter `name`, and the CLI's own built-ins are listed too. |\n| `:` | A plugin's skill, under `~/.gemini/config/plugins//skills/`. A plugin holding one skill directly in `skills/` is addressed with a `..` placeholder: `/android-cli-plugin:..:android-cli`. |\n\n- **Disabled plugins** are left out: `\"enabled\": false` in `~/.gemini/config/config.json`, or\n `\"disabled\": true` in a `plugin.json` with no `config.json` entry (an entry there always wins).\n- **`skills.json`** (`.agents/skills.json`, the same file under the other workspace roots, and\n `~/.gemini/config/skills.json`) loads the items directly inside its `path`, one level deep;\n `include_only` and `exclude` name those items exactly, a nested one is named by its relative path in\n `include_only` (`nested/deep`), and a relative `path` resolves from the repository root.\n- **Some built-ins are per account**: `/compact`, `/review` and `/owl` are gated server-side, and\n commands the CLI answers itself (`/skills`, `/model`, …) end a `stream-json` turn, so both stay out.\n\n## What it cannot do, and why\n\n- **Steering** is impossible: a line written to agy's stdin while a turn runs is queued as the *next*\n turn, so Paseo replaces the active turn instead of offering to steer it.\n- **Tool permission prompts** cannot be surfaced either — agy resolves tool approval internally from\n its own `toolPermission` setting. Choose the behaviour in session settings.\n- **Rewind**: Antigravity's `/rewind` is interactive-only; nothing in `stream-json` exposes it.\n- **Shared-installer skills** (`~/.agents/skills/`) are offered and expanded by the plugin, not the\n CLI: the turn is sent the `SKILL.md` body, capped at 64 KiB (a larger one fails with\n `code: \"skill_too_large\"`).\n\n## Session settings\n\n| Setting | Behaviour |\n|---|---|\n| **Tool approval** | Default *Use Antigravity setting*, no flag; *Skip all permissions* passes `--dangerously-skip-permissions`. |\n| **Sandbox** | Off/On; *On* passes `--sandbox`. |\n| **Share Paseo tools with Antigravity** | Off/On, *Off* by default — see [MCP sharing](#sharing-paseos-mcp-servers-opt-in). |\n| **Agent profile** | An optional select of the custom agents `agy` has here; *Default* passes no `--agent`. |\n\nThe select only offers what `agy` will launch: agents under the workspace's `.agents/agents/` and its\nglobal agent roots, `.md` or `/agent.md`, with a frontmatter `name` and `description`.\n`mainAgent: false` agents are skipped, hidden ones are offered, and workspace agents need that workspace\ntrusted in `antigravity-cli/settings.json` (`trustedWorkspaces`) — the real\n`~/.gemini/antigravity-cli/settings.json` for the Default account, and each other account's own copy\n([Multiple accounts](#multiple-accounts)) — an unknown `--agent` name\nsilently runs the default agent. The two Off/On settings are selects rather than toggles, because a\nPaseo plugin toggle has no visible state; older `true`/`false` values read as *On*/*Off*.\n\n## providerOptions\n\n| Option | Effect |\n|---|---|\n| `agyPath` | Absolute path to the CLI binary for this session. |\n| `extraArgs`, `addDirs` | Extra argv appended after the plugin's own flags, and absolute paths each passed as an extra `--add-dir` (anything else is dropped with a warning notice). |\n| `agent` | Custom agent persona to pass as `--agent `. The **Agent profile** setting wins over it. |\n| `effort` | Reasoning effort: the selected model family's tier when it has that tier, the `--effort` flag when no model is selected, and otherwise dropped with one log line. Never passed alongside `--model`. |\n\n## Multiple accounts\n\n> **Your own responsibility.** Using the plugin with the Default account — the one sign-in `agy`\n> already has — stays within the [terms of service](#terms-of-service) as described there. Whether\n> running several Antigravity accounts side by side is allowed is **not clear** from the published\n> terms. Use multiple accounts at your own risk.\n\nThe sidebar entry **Antigravity accounts** manages a host-wide *active account*: the account every new\nagent runs under. The screen lists the accounts and marks the active one; pressing an account shows\nits settings in the pane below, and that account's **Use** button makes it the active account — the\nactive row shows the `active` badge in place of the button. It also adds, signs in and removes\naccounts, and edits the two per-account settings below.\n\n- **Default** is the real home and its `~/.gemini` — the account `agy` already uses in a normal\n terminal. It is always listed first, has no directory of its own, and cannot be removed; the plugin\n reads and writes about it exactly as it did before multiple accounts existed.\n- **New agents** spawn the official `agy` with `HOME` pointing at the active account's own home. A\n running agent keeps the account it started with: switching changes the next spawn only.\n- **Resumed and imported conversations** reopen under the account that created them, because the\n account id is stored beside the conversation id; a conversation with no account id belongs to\n Default. Opening one whose account has been removed fails with an error naming it.\n- **Add account** asks for a name, creates the account's home, and opens the CLI's own sign-in there.\n On macOS that is a Terminal window on the **daemon's** machine (the screen names the host) with\n `HOME` set to the account's home; the launcher is `sign-in.command` in the account's directory, run\n with `open`. Off macOS, or when that hand-off fails, nothing is launched and the screen shows the\n exact `HOME=… agy` line to run on that host instead.\n- **Sign in again** re-runs that flow for an existing account.\n- **Remove** deletes the account's own directory — its sign-in and its conversation history — and\n never touches the real home. Removing the active account makes Default active.\n- **Per-account settings**: the pane below the list edits the account's *tool permission* and its\n *trusted workspaces*; the change applies to that account's next launch. Default's copy is shown\n read-only, because `agy` owns the real file.\n\n### Usage quota\n\nEach account's card shows what that account has left: one row per pool the CLI reports — for the\naccounts seen here, Gemini models and Claude and GPT models, each with a weekly and a 5-hour pool —\nwith the share left, a bar, the reset time, and a `checked HH:MM` line (local clock) under the rows.\nThe figures come from the account's own run of the CLI's print-mode command, spawned under that\naccount's `HOME` (Default: the daemon's environment unchanged) from the temp directory:\n\n```\nHOME= agy -p /usage --output-format json\n```\n\n`agy` 1.1.11 added non-interactive answers for the read-only slash commands, so the binary answers\n`/usage` without starting an agent turn, without spending quota and without leaving a conversation\nbehind; the plugin additionally refuses any answer whose `num_turns` is not 0. The argv is exactly\n`-p /usage --output-format json` — never `--disable-slash-commands`, which session launches pass\nunless slash commands are allowed, and which would stop `/usage` from expanding and turn it into a\nreal agent turn that spends quota — and the plugin parses only that command's output. One read takes\na few seconds to about twenty, and writes a normal `agy` log file in the account's\n`.gemini/antigravity-cli/log/`.\n\nA card reads when the screen is opened and when **Refresh** is pressed; nothing polls in the\nbackground. The daemon keeps a successful answer for 5 minutes per account and merges concurrent\nreads into one process, so reopening the screen is free. While a read runs the card shows *Checking\nquota…*; a signed-out account shows a hint; `agy` reporting an error is shown with its own message\n(for example an account with no quota summary); anything else is an error with **Refresh** beside it.\n\nThe shape of that JSON is not in Antigravity's documentation — it comes from `agy`'s changelog and\nobserved output — so a future `agy` may change it, and the card then shows an error instead of wrong\nnumbers.\n\n### The shadow home\n\nAn account is a *shadow home*: a directory that looks like a home directory to the CLI. Its top level\nis links into your real home, so the agent's shell keeps seeing your dotfiles, and `.gemini` is a real\ndirectory whose shared parts link back to the real `~/.gemini`:\n\n| Shared with the "},{"id":"archive-branch-cleanup","repo":"MaplumeX/paseo-archive-branch-cleanup","url":"https://github.com/MaplumeX/paseo-archive-branch-cleanup","name":"archive-branch-cleanup","description":"A [Paseo](https://paseo.sh) plugin that automatically deletes the local git branch when a Paseo-owned worktree workspace is archived.","categories":["git","automation"],"platforms":[],"caveats":[],"images":[],"themes":[],"health":{"manifestValid":true,"hasReadme":true,"hasLicense":false,"hasTests":false,"hasTypecheckScript":true,"updatedRecently":true},"scannedAt":"2026-09-25T20:16:19.264Z","addedAt":"2026-09-10T18:09:18+03:00","version":"0.1.0","security":{"status":"passed","blockingFindings":0,"advisoryFindings":0,"scannedAt":"2026-09-25T20:04:23.597Z","commit":"59bc5335e7cd3d5e61fc375565bb1fca9faee6da"},"paseoVersionRequirement":">=0.8.0","descriptionNodes":[{"type":"text","text":"A "},{"type":"link","href":"https://paseo.sh","children":[{"type":"text","text":"Paseo"}]},{"type":"text","text":" plugin that automatically deletes the local git branch when a Paseo-owned worktree workspace is archived."}],"caveatNodes":[],"manifest":{"id":"archive-branch-cleanup","requirements":{"paseo":">=0.8.0"}},"repoMeta":{"stars":0,"defaultBranch":"master","pushedAt":"2026-09-13T10:51:22Z"},"owner":{"login":"MaplumeX","avatarUrl":"https://avatars.githubusercontent.com/u/44311044?v=4"},"installNotesHtml":"paseo plugin install /absolute/path/to/paseo-archive-branch-cleanup\n
\nRequires the daemon-wide Enable plugins switch under Settings → Plugins.
","readmeText":"# paseo-archive-branch-cleanup\n\nA [Paseo](https://paseo.sh) plugin that automatically deletes the local git branch when a Paseo-owned worktree workspace is archived.\n\n## Why\n\nWhen you archive a PR worktree workspace in Paseo, the daemon removes the worktree directory but leaves the local branch behind. Over time these stale branches accumulate. This plugin cleans them up automatically.\n\n## How it works\n\nThe plugin runs a background watcher inside the Paseo daemon plugin subprocess:\n\n1. Connects to the local Paseo daemon via `@getpaseo/client`\n2. Subscribes to workspace update events\n3. Caches branch and repo info for Paseo-owned worktree workspaces from upsert events\n4. On a workspace `remove` event, deletes the cached branch from the main repo with `git branch -D`\n\nBranch deletion retries for up to 30 seconds, because the daemon may still be removing the worktree (the branch stays checked out until the worktree is gone).\n\n## Safety\n\n- Only touches workspaces where `gitRuntime.isPaseoOwnedWorktree === true` (branches Paseo created)\n- Refuses to delete main-line branches (`main`, `master`, `trunk`, `develop`, `dev`, `production`, `prod`, `release/*`) even on a Paseo-owned worktree, since a worktree can check out an existing branch\n- Only deletes the **local** branch (`git branch -D`), never the remote\n- Branch name is resolved from `githubRuntime.pullRequest.headRefName`, falling back to `gitRuntime.currentBranch`\n- Deletion runs in the main repo root (`project.checkout.mainRepoRoot`), not the worktree\n\n## Install\n\n```sh\npaseo plugin install /absolute/path/to/paseo-archive-branch-cleanup\n```\n\nRequires the daemon-wide **Enable plugins** switch under Settings → Plugins.\n\n## Requirements\n\n- Paseo daemon reachable on the local machine. The plugin auto-detects the listen target from `PASEO_HOME/config.json` (`daemon.listen`), falling back to `127.0.0.1:6767`.\n- Git CLI on PATH\n\n## Development\n\n```sh\nnpm run typecheck # type-check\npaseo plugin reload paseo-archive-branch-cleanup # reload after edits\npaseo plugin logs paseo-archive-branch-cleanup # view backend output\n```\n\n## License\n\nMIT"},{"id":"auto-pin","repo":"stv1024/paseo-auto-pin","url":"https://github.com/stv1024/paseo-auto-pin","package":"paseo-auto-pin","npm":{"package":"paseo-auto-pin","version":"0.4.0","integrity":"sha512-qP6IgwXcJhiCU+Ep5oSC+BjJI10fjUMO37D6SOSMp/Sky/oWA8a5eG3xymBhhuTzkEtVHtoV/xD6vCtaQU2Nqw==","publishedAt":"2026-09-24T07:28:48.151Z","downloadsLast30Days":0},"name":"auto-pin","description":"Automatically pin new Paseo workspaces, with defaults and rules for individual projects.","categories":["automation","productivity"],"platforms":[],"caveats":["Requires Paseo >=0.9.1 <0.10.0 and Node.js/npm on the daemon host.","Uses Paseo's internal daemon client API for workspace pinning.","Rules apply to newly created workspaces only; existing pins and restored workspaces stay unchanged."],"images":["https://raw.githubusercontent.com/stv1024/paseo-auto-pin/2685698055b7cb6476392f3b0661a5c56ac49415/docs/demo.gif"],"themes":[],"health":{"manifestValid":true,"hasReadme":true,"hasLicense":true,"hasTests":true,"hasTypecheckScript":true,"updatedRecently":true},"scannedAt":"2026-09-25T20:16:20.078Z","addedAt":"2026-09-25T10:00:16Z","npmSecurity":{"status":"passed","blockingFindings":0,"advisoryFindings":0,"scannedAt":"2026-09-25T20:04:23.597Z","version":"0.4.0","integrity":"sha512-qP6IgwXcJhiCU+Ep5oSC+BjJI10fjUMO37D6SOSMp/Sky/oWA8a5eG3xymBhhuTzkEtVHtoV/xD6vCtaQU2Nqw=="},"version":"0.4.0","security":{"status":"passed","blockingFindings":0,"advisoryFindings":0,"scannedAt":"2026-09-25T20:04:23.597Z","commit":"2685698055b7cb6476392f3b0661a5c56ac49415"},"author":"stv1024","license":"MIT","paseoVersionRequirement":">=0.9.1 <0.10.0","descriptionNodes":[{"type":"text","text":"Automatically pin new Paseo workspaces, with defaults and rules for individual projects."}],"caveatNodes":[[{"type":"text","text":"Requires Paseo >=0.9.1 <0.10.0 and Node.js/npm on the daemon host."}],[{"type":"text","text":"Uses Paseo's internal daemon client API for workspace pinning."}],[{"type":"text","text":"Rules apply to newly created workspaces only; existing pins and restored workspaces stay unchanged."}]],"manifest":{"id":"auto-pin","description":"Automatically pin new workspaces. Follow a default or choose Always / Never for each project.","requirements":{"paseo":">=0.9.1 <0.10.0"},"build":[["npm","ci","--include=dev","--ignore-scripts"]]},"repoMeta":{"stars":1,"defaultBranch":"main","pushedAt":"2026-09-24T08:09:32Z"},"owner":{"login":"stv1024","avatarUrl":"https://avatars.githubusercontent.com/u/10416476?v=4"},"installNotesHtml":"Requires Paseo 0.9.1–0.9.x and Node.js/npm on the machine running the Paseo daemon.
\npaseo plugin install npm:paseo-auto-pin@0.4.0\n
\nOr install from GitHub:
\npaseo plugin install https://github.com/stv1024/paseo-auto-pin\n
\nOpen Auto-Pin in the sidebar to adjust your settings. It starts with auto-pin\non for all new workspaces.
","readmeText":"# Auto-Pin for Paseo\n\nAutomatically pin new [Paseo](https://paseo.sh) workspaces, with exceptions for individual projects.\n\nKeep everyday work near the top of your sidebar and leave experiments unpinned.\nAuto-Pin runs in the background, even when its panel is closed.\n\n\n\nCreate a workspace. Auto-Pin moves it into **Pinned** automatically.\n[Watch the original video](docs/demo.mp4).\n\n## Install\n\nRequires **Paseo 0.9.1–0.9.x** and Node.js/npm on the machine running the Paseo daemon.\n\n```bash\npaseo plugin install npm:paseo-auto-pin@0.4.0\n```\n\nOr install from GitHub:\n\n```bash\npaseo plugin install https://github.com/stv1024/paseo-auto-pin\n```\n\nOpen **Auto-Pin** in the sidebar to adjust your settings. It starts with auto-pin\non for all new workspaces.\n\n## Choose what gets pinned\n\nThe **Pin new workspaces by default** switch sets the behavior for projects\nwithout an override. Each project has three choices:\n\n| Rule | What happens when you create a workspace |\n| --- | --- |\n| **Follow default** | Uses the current default switch. |\n| **Always** | Pins it, even when the default is off. |\n| **Never** | Leaves it unpinned, even when the default is on. |\n\nFor example, set your main project to **Always**, experiments to **Never**, and\nleave everything else on **Follow default**.\n\nProjects appear automatically from Paseo. You can search by name or folder path.\nRules apply to new workspaces belonging to that project, including worktrees.\n\n### A few things to know\n\n- Changes save automatically and are shared by clients connected to the same daemon.\n- Rules only affect workspaces created afterward. Existing pins stay as they are.\n- Restoring an archived workspace does not pin it again.\n- Auto-Pin never removes a pin. You can still pin or unpin workspaces yourself.\n- **Always** and **Never** override the default switch. To pause the entire plugin,\n disable it in Paseo's plugin settings.\n\nIn the Command Center, use **Auto-Pin: Toggle Default** for a quick change, or\n**Auto-Pin: Open Panel** to manage project rules.\n\n## Update\n\nFor an installation from npm or Git:\n\n```bash\npaseo plugin update auto-pin --check\npaseo plugin update auto-pin\n```\n\nUpdating from 0.3 keeps your existing on/off setting. Every project starts on\n**Follow default** until you choose otherwise.\n\nAuto-Pin **0.4.x** supports Paseo **0.9.1–0.9.x**.\nFor Paseo 0.8, use Auto-Pin 0.2.0; for Paseo 0.7, use 0.1.0.\n\n## Need a hand?\n\nIf a new workspace is not pinned, check its project rule and the default switch.\nIf you just changed a setting on another device, press **Refresh** in the panel.\n\nFor errors or unexpected behavior, [open an issue](https://github.com/stv1024/paseo-auto-pin/issues).\nInclude your Paseo and Auto-Pin versions, the rule you selected, and what happened.\nLogs are available with `paseo plugin logs auto-pin`; remove private paths before\nsharing them.\n\nHave a workflow this does not cover? Describe it in an issue. A concrete example\nhelps decide what to build next.\n\n[Share your workflow in the Paseo community discussion](https://github.com/getpaseo/paseo/discussions/5346).\n\n[What's changed](CHANGELOG.md) · [Development](docs/development.md) · [Community post and demo guide](docs/community.md)\n\n## License\n\n[MIT](LICENSE)\n"},{"id":"beads-board","repo":"jmkelly/paseo-beads-board","url":"https://github.com/jmkelly/paseo-beads-board","package":"paseo-beads-board","npm":{"package":"paseo-beads-board","version":"0.1.1","integrity":"sha512-gcJa6jjn7Zm+hnOIhllhdN+zzQLzCUvQE48PZRx0uR3z2/niE+bigtpmnmtTpj2xEsrTdxfzRSOKvWceGcemJA==","publishedAt":"2026-09-28T12:31:47.474Z","downloadsLast30Days":0},"name":"beads-board","description":"Kanban board for the beads (bd) issue tracker inside Paseo, with a workspace panel, sidebar surface, and composer attachment source.","categories":["productivity"],"platforms":[],"caveats":["Requires the beads `bd` CLI on the daemon host; set PASEO_BEADS_BD_BIN if it is not on PATH.","Server code runs `bd` as the daemon user and can modify any beads database that user can reach.","Pre-1.0 release: versions are 0.x, so a minor bump may contain breaking changes.","No drag and drop: move beads with the status buttons in the bead detail sheet.","Board only; beads-web's GitOps, PR, memory, and worktree panels are not included.","Boards load at most 5000 beads per project, and long bead text is fetched on demand."],"images":["https://raw.githubusercontent.com/jmkelly/paseo-beads-board/2a501e7caa780ae85ed02aa49d8d3a01add0e6d8/images/bead-detail.png","https://raw.githubusercontent.com/jmkelly/paseo-beads-board/2a501e7caa780ae85ed02aa49d8d3a01add0e6d8/images/board-closed-column.png","https://raw.githubusercontent.com/jmkelly/paseo-beads-board/2a501e7caa780ae85ed02aa49d8d3a01add0e6d8/images/board.png","https://raw.githubusercontent.com/jmkelly/paseo-beads-board/2a501e7caa780ae85ed02aa49d8d3a01add0e6d8/images/create-bead.png"],"themes":[],"health":{"manifestValid":true,"hasReadme":true,"hasLicense":true,"hasTests":true,"hasTypecheckScript":true,"updatedRecently":true},"scannedAt":"2026-09-28T13:25:38.677Z","addedAt":"2026-09-28T16:20:36+03:00","npmSecurity":{"status":"passed","blockingFindings":0,"advisoryFindings":0,"scannedAt":"2026-09-28T13:25:21.577Z","version":"0.1.1","integrity":"sha512-gcJa6jjn7Zm+hnOIhllhdN+zzQLzCUvQE48PZRx0uR3z2/niE+bigtpmnmtTpj2xEsrTdxfzRSOKvWceGcemJA=="},"version":"0.1.1","security":{"status":"passed","blockingFindings":0,"advisoryFindings":0,"scannedAt":"2026-09-28T13:25:21.577Z","commit":"2a501e7caa780ae85ed02aa49d8d3a01add0e6d8"},"author":"James Kelly","license":"MIT","paseoVersionRequirement":">=0.8.0","descriptionNodes":[{"type":"text","text":"Kanban board for the beads (bd) issue tracker inside Paseo, with a workspace panel, sidebar surface, and composer attachment source."}],"caveatNodes":[[{"type":"text","text":"Requires the beads "},{"type":"text","text":"bd","code":true},{"type":"text","text":" CLI on the daemon host; set PASEO_BEADS_BD_BIN if it is not on PATH."}],[{"type":"text","text":"Server code runs "},{"type":"text","text":"bd","code":true},{"type":"text","text":" as the daemon user and can modify any beads database that user can reach."}],[{"type":"text","text":"Pre-1.0 release: versions are 0.x, so a minor bump may contain breaking changes."}],[{"type":"text","text":"No drag and drop: move beads with the status buttons in the bead detail sheet."}],[{"type":"text","text":"Board only; beads-web's GitOps, PR, memory, and worktree panels are not included."}],[{"type":"text","text":"Boards load at most 5000 beads per project, and long bead text is fetched on demand."}]],"manifest":{"id":"beads-board","requirements":{"paseo":">=0.8.0"}},"repoMeta":{"stars":0,"defaultBranch":"main","pushedAt":"2026-09-28T12:32:54Z"},"owner":{"login":"jmkelly","avatarUrl":"https://avatars.githubusercontent.com/u/124026?v=4"},"installNotesHtml":"Paseo 0.9 and newer install from npm:
\npaseo plugin install npm:paseo-beads-board\n
\nPin a specific release when you do not want to track the latest one:
\npaseo plugin install npm:paseo-beads-board@0.1.0\n
\nPaseo 0.8 installs from the repository:
\npaseo plugin add jmkelly/paseo-beads-board\n
\nThe daemon must have plugins enabled. Check with paseo daemon status --json; the file is\n<home>/config.json and needs a root \"pluginsEnabled\": true, followed by paseo reload.
\nFrom a clone of this repository:
\nnpm install\nnpm run typecheck\nnpm test\npaseo plugin install /absolute/path/to/paseo-beads-board\npaseo plugin ls\npaseo plugin logs beads-board\n
\nSource changes need paseo plugin reload beads-board. After installing, open Beads board in\nthe sidebar, pick a project, and the board appears.
","limitationsNotesHtml":"\n- This plugin is pre-1.0 (
0.x). A minor version bump may contain breaking changes, so pin a\nversion if you are depending on today's behaviour. \n- The
bd CLI must be installed on each daemon host you install this plugin on; a missing binary\nsurfaces as an error on the board and in paseo plugin logs beads-board. \n- No drag and drop. React Native plugin code has no gesture-handler dependency, so cards move\nthrough the status buttons in the detail sheet.
\n- No GitOps, PR, memory, or worktree panels: this plugin covers the beads board itself, unlike\nbeads-web.
\n- Beads are always read with
bd list --brief; long text is fetched on demand with bd show, so\nvery large boards briefly load in two passes. \n- Board data is capped at 5000 beads per load; larger databases show a truncated board.
\n- Status names come from each database (
bd statuses --json), so a database that has renamed\nin_progress will move beads to whatever status currently maps to that column. \n
","readmeText":"# Beads board for Paseo\n\nA Paseo plugin that turns the [beads](https://github.com/steveyegian/beads) `bd` CLI into a\nkanban board inside Paseo, inspired by [beads-web](https://github.com/weselow/beads-web).\n\n> **Pre-1.0.** Releases are `0.x`, following semver's pre-1.0 convention: features and fixes bump\n> the patch version, but a minor bump may still contain breaking changes until the plugin API and\n> the board settle at `1.0.0`. Pin an exact version if you do not want to track the latest release.\n\nThe board is rendered by the Paseo app (React Native, so desktop, browser, iOS, and Android all\nwork) and every data operation runs the `bd` CLI in a subprocess on the daemon host. Install the\nplugin on each host you want a board for; Paseo shows one sidebar item with a host picker and the\nselected host serves its own projects.\n\n## Screenshots\n\n\n\n\nMore screenshots
\n\n\n\n\n\n\n\n \n\n## Features\n\n- **Project discovery** — scans Paseo projects and workspaces on the host for an initialized beads\n database, plus any extra paths you add in settings. Worktrees that share a database are collapsed\n onto it, so each project is listed once.\n- **Kanban board** — Open / In Progress / In Review / Closed, with the same status mapping as\n beads-web (`blocked`, `deferred`, `pinned` show as badges on Open; `hooked` shows on In\n Progress; `tombstone` is hidden).\n- **Epics** — child beads are grouped under their parent with a progress bar, like beads-web.\n- **Blocked detection** — a bead is blocked when an unresolved dependency is still open, or its\n status is `blocked`.\n- **Mutations** — create beads (with a project dropdown covering every discovered beads database),\n move them between columns, edit title/description/notes/priority/assignee, close and reopen, and\n add comments. Each mutation shells out to `bd`.\n- **Bead detail** — full text (`bd show`), relations, and comments (`bd comments`).\n- **Workspace panel** — the same board as a workspace tab, preselected to the workspace's project.\n- **Composer attachment source** — attach a bead to a prompt from any composer.\n- **Host settings** — extra project paths, refresh interval, closed-column default.\n\n## Requirements\n\n- Paseo 0.8.0 or newer, on the daemon host and the connected app.\n- The [beads](https://github.com/steveyegian/beads) `bd` CLI on the **daemon host's `PATH`**, so the\n plugin can shell out to it. Set `PASEO_BEADS_BD_BIN` in the daemon environment if the binary\n lives somewhere unusual.\n\nPlugins are trusted, unsandboxed code. This plugin's server code runs `bd` in the daemon user's\naccount, so it can read and change the beads databases that user can reach. Review the source\nbefore installing it on a machine you care about.\n\n## Install\n\nPaseo 0.9 and newer install from npm:\n\n```bash\npaseo plugin install npm:paseo-beads-board\n```\n\nPin a specific release when you do not want to track the latest one:\n\n```bash\npaseo plugin install npm:paseo-beads-board@0.1.0\n```\n\nPaseo 0.8 installs from the repository:\n\n```bash\npaseo plugin add jmkelly/paseo-beads-board\n```\n\nThe daemon must have plugins enabled. Check with `paseo daemon status --json`; the file is\n`/config.json` and needs a root `\"pluginsEnabled\": true`, followed by `paseo reload`.\n\nFrom a clone of this repository:\n\n```bash\nnpm install\nnpm run typecheck\nnpm test\npaseo plugin install /absolute/path/to/paseo-beads-board\npaseo plugin ls\npaseo plugin logs beads-board\n```\n\nSource changes need `paseo plugin reload beads-board`. After installing, open **Beads board** in\nthe sidebar, pick a project, and the board appears.\n\n## Using the board\n\n- **Move a bead** — open it and use the status buttons in the detail sheet. There is no drag and\n drop (see [Limitations](#limitations)).\n- **Create a bead** — the *New bead* button on the board; the project dropdown lists every\n discovered beads database.\n- **Add a bead to a prompt** — type in the composer and pick the **Beads** attachment source, then\n search by id or title.\n- **Per-host preferences** — **Settings → Beads board** controls extra project paths, the refresh\n interval, and whether the Closed column is shown. Preferences are host-scoped and shared by every\n client connected to that daemon.\n\n## Layout\n\n```text\npaseo-plugin.json plugin id, description, supported Paseo versions\nindex.client.tsx surface, sidebar item, workspace panel, settings screen, commands, attachment source\nindex.server.ts RPC handlers + host settings registration\nshared/beads.ts Zod contracts, RPC definitions, status -> column mapping\nshared/settings.ts host-scoped preferences document\nshared/attachments.ts composer attachment source\nserver/bd.ts `bd` process execution helpers\nserver/beads.ts raw bd JSON -> board normalization (parents, blockers, epic progress)\nserver/handlers.ts project discovery and every RPC handler\nclient/hooks.ts TanStack Query hooks and mutations\nclient/board/ board screen, columns, cards, detail/create/picker modals\ntests/ unit tests for the status mapping and board normalization\n```\n\n## RPCs\n\n| RPC | Runs |\n| ---------------- | --------------------------------------- |\n| `beads.projects` | `bd status --json`, `bd count --json --status inreview`, `bd where --json` |\n| `beads.board` | `bd list`, `bd statuses --json`, `bd where --json` |\n| `beads.show` | `bd show --json`, `bd comments --json` |\n| `beads.create` | `bd create --json` |\n| `beads.update` | `bd update` / `bd close` / `bd reopen` |\n| `beads.comment` | `bd comment` |\n| `beads.search` | `bd list --json --brief --all` |\n\nDiscovery uses the daemon's Paseo API (`projects.list()`, `workspaces.list()`) to find candidate\ndirectories, and a directory appears on the board when `.beads` holds an initialized database\n(`config.yaml`, `metadata.json`, or `issues.db`) — directly, or within four parent levels. Each\ndatabase is listed once however many Paseo worktrees point at it, and the counts come from `bd`'s\nown `status` summary rather than a full issue list.\n\n## Development\n\n```bash\nnpm install\nnpm run typecheck\nnpm test\npaseo plugin install /absolute/path/to/paseo-beads-board\npaseo plugin reload beads-board\n```\n\nKeep the plugin ID (`beads-board`) and the npm version in `package.json` in step: Paseo 0.9\ninstalls the npm package, and the paseo.cafe catalog uses the published version as the plugin's\nupdate identity, so every release needs a version bump and an `npm publish`. While the plugin is\npre-1.0, bump with `npm version patch` for fixes and `npm version minor` for anything that may\nchange existing behaviour.\n\n## Limitations\n\n- This plugin is pre-1.0 (`0.x`). A minor version bump may contain breaking changes, so pin a\n version if you are depending on today's behaviour.\n- The `bd` CLI must be installed on each daemon host you install this plugin on; a missing binary\n surfaces as an error on the board and in `paseo plugin logs beads-board`.\n- No drag and drop. React Native plugin code has no gesture-handler dependency, so cards move\n through the status buttons in the detail sheet.\n- No GitOps, PR, memory, or worktree panels: this plugin covers the beads board itself, unlike\n beads-web.\n- Beads are always read with `bd list --brief`; long text is fetched on demand with `bd show`, so\n very large boards briefly load in two passes.\n- Board data is capped at 5000 beads per load; larger databases show a truncated board.\n- Status names come from each database (`bd statuses --json`), so a database that has renamed\n `in_progress` will move beads to whatever status currently maps to that column.\n\n## Contributing\n\nIssues and pull requests are welcome at\n. Please run `npm run typecheck` and\n`npm test` before opening a pull request.\n\n## License\n\n[MIT](./LICENSE)\n"},{"id":"beads-viewer","repo":"cuongntr/paseo-beads-viewer","url":"https://github.com/cuongntr/paseo-beads-viewer","package":"beads-viewer","npm":{"package":"beads-viewer","version":"0.6.0","integrity":"sha512-ZCrpAMklPYWh8OCnBX+FzGf/gmqJAVBrfP5Te2v3LfslinHnP98YiM/lDmNkvUAk+0boR3K0AoUHGvupgbLTkA==","publishedAt":"2026-09-28T09:17:38.051Z","downloadsLast30Days":542},"name":"beads-viewer","description":"Read-only Beads console for Paseo: project progress, ready and waiting work, the critical chain, and a whole-project board, read through bv.","categories":["monitoring","productivity","orchestration"],"platforms":["macos","linux"],"caveats":["Requires the bv (beads_viewer) CLI on the Paseo daemon's PATH; verified against bv v0.25.0.","Read-only by design: it never claims, closes or edits issues; do that with br or bd.","Issue detail, types and assignees need the project's br or bd CLI on the daemon's PATH.","Custom statuses from .beads/policy.yaml are shown as written, never mapped to ready or done.","Projects over 2000 issues load all open work but only some closed issues, and the panel says so.","Composer attachment search covers at most 4 recently active Beads workspaces."],"images":["https://raw.githubusercontent.com/cuongntr/paseo-beads-viewer/b4c35acebdece0252fea72bcc3fbd5f9194ec9b7/images/board.png","https://raw.githubusercontent.com/cuongntr/paseo-beads-viewer/b4c35acebdece0252fea72bcc3fbd5f9194ec9b7/images/overview.png","https://raw.githubusercontent.com/cuongntr/paseo-beads-viewer/b4c35acebdece0252fea72bcc3fbd5f9194ec9b7/images/plan.png","https://raw.githubusercontent.com/cuongntr/paseo-beads-viewer/b4c35acebdece0252fea72bcc3fbd5f9194ec9b7/images/risks.png"],"themes":[],"health":{"manifestValid":true,"hasReadme":true,"hasLicense":true,"hasTests":true,"hasTypecheckScript":true,"updatedRecently":true},"scannedAt":"2026-09-28T11:12:56.630Z","addedAt":"2026-09-24T22:59:22+03:00","npmSecurity":{"status":"passed","blockingFindings":0,"advisoryFindings":0,"scannedAt":"2026-09-28T11:12:47.026Z","version":"0.6.0","integrity":"sha512-ZCrpAMklPYWh8OCnBX+FzGf/gmqJAVBrfP5Te2v3LfslinHnP98YiM/lDmNkvUAk+0boR3K0AoUHGvupgbLTkA=="},"version":"0.6.0","security":{"status":"passed","blockingFindings":0,"advisoryFindings":0,"scannedAt":"2026-09-28T11:12:47.026Z","commit":"b4c35acebdece0252fea72bcc3fbd5f9194ec9b7"},"author":"cuongntr","license":"MIT","paseoVersionRequirement":">=0.8.0","descriptionNodes":[{"type":"text","text":"Read-only Beads console for Paseo: project progress, ready and waiting work, the critical chain, and a whole-project board, read through bv."}],"caveatNodes":[[{"type":"text","text":"Requires the bv (beads_viewer) CLI on the Paseo daemon's PATH; verified against bv v0.25.0."}],[{"type":"text","text":"Read-only by design: it never claims, closes or edits issues; do that with br or bd."}],[{"type":"text","text":"Issue detail, types and assignees need the project's br or bd CLI on the daemon's PATH."}],[{"type":"text","text":"Custom statuses from .beads/policy.yaml are shown as written, never mapped to ready or done."}],[{"type":"text","text":"Projects over 2000 issues load all open work but only some closed issues, and the panel says so."}],[{"type":"text","text":"Composer attachment search covers at most 4 recently active Beads workspaces."}]],"manifest":{"id":"beads-viewer","requirements":{"paseo":">=0.8.0"}},"repoMeta":{"stars":1,"defaultBranch":"main","pushedAt":"2026-09-28T09:10:28Z"},"owner":{"login":"cuongntr","avatarUrl":"https://avatars.githubusercontent.com/u/6338052?v=4"},"installNotesHtml":"paseo plugin add cuongntr/paseo-beads-viewer\npaseo plugin ls beads-viewer # expect beads-viewer running\n
\nUpdate to the latest release with paseo plugin update beads-viewer. If the panel does not\nappear, paseo plugin logs beads-viewer shows why; the most common cause is bv missing from\nthe daemon's PATH.
\nReleases before 0.2.0 used the plugin id paseo-beads and the npm package paseo-beads. That id\nbelongs to another plugin on paseo.cafe, so this one is now beads-viewer. If you installed an\nearlier release, remove it first with paseo plugin remove paseo-beads.
\nTo run a local checkout instead:
\nnpm install && npm run typecheck && npm test\npaseo plugin install /absolute/path/to/paseo-beads-viewer\n
\nAfter editing source, run paseo plugin reload beads-viewer.
","limitationsNotesHtml":"\n- Read-only by design. Claiming, closing, and editing issues stay in
br/bd. \n- Issue detail requires an exact tracker and database route. The plugin checks
bv, then the\nselected source's .beads/metadata.json; if identity or routing remains inconclusive, detail\nreads are disabled rather than guessed. \n- Attachment search has no workspace context, so it scans a bounded set of recently active\nPaseo workspaces, searches at most 4 Beads-enabled ones, and returns at most 8 items. An\nissue in a workspace outside that window will not appear.
\n- Search relevance, ranking, and analysis semantics are entirely
bv's; the plugin only\nreshapes them. \n- Statuses, readiness values, and alert severities are treated as opaque strings, so a newer\n
bv renders without a plugin update but without bespoke styling for new values. \n- The panel serves any Beads project, so it interprets only what Beads and
bv define and what\nthe data's structure says. Statuses are Beads' built-in set (open, in_progress, hooked,\nblocked, deferred, draft, pinned, closed, tombstone); a custom status declared in a\nproject's .beads/policy.yaml is shown verbatim under Other status, not guessed to be ready\nor done. Groups follow parent links, never type names or id patterns. Labels are the project's\nown vocabulary: they are shown and counted as written, a label carried by every open item is\nset aside as uninformative, and no label is given a meaning — so there is no buil… \n
","readmeText":"# beads-viewer\n\nA read-only Beads console for Paseo workspaces. For the workspace you are in it shows how far\nalong the project is per parent issue, what is in progress, what can start now, how the project's\nown labels spread over open work, and the critical chain of dependencies; a whole-project board\nby work state;\nexecution tracks; risks; issue search; Markdown-rendered issue detail; and a composer attachment\nsource for Beads issues.\n\nThe plugin never invokes a mutating `br` or `bd` command. There is no claim, close,\nupdate, or create path in the code. `bv` may refresh its own compatibility export while\nloading a `bd`/Dolt workspace, so `bv` calls are serialized per workspace.\n\n## Screenshots\n\nShown on a made-up demo project.\n\n**Overview**: progress per parent, what is in progress, held and ready now, the project's labels\nover open work, and the critical chain.\n\n\n\n**Board**: one column per work state in the order work moves, filtered by parent or label, each\ncolumn with its definition.\n\n\n\n**Plan**: `bv`'s parallel execution tracks, containers left out.\n\n\n\n**Risks**: stuck and parked work, alerts by severity, and the keystones that unblock the most.\n\n\n\n## Requirements\n\n- Paseo `>=0.8.0` (daemon and app).\n- The [`bv`](https://github.com/Dicklesworthstone/beads_viewer) analysis CLI on the daemon machine's `PATH`.\n Verified against `bv v0.25.0`.\n- A project that uses Beads through `br` or `bd`. The tracker CLI matching the project must\n also be on the daemon `PATH` for issue detail and for issue types and assignees; everything\n else works without it.\n\nEverything else degrades gracefully: a missing `bv`, a workspace without a `.beads` source,\nand an empty-but-healthy project are three distinct, clearly labelled states.\n\n## Install\n\n```bash\npaseo plugin add cuongntr/paseo-beads-viewer\npaseo plugin ls beads-viewer # expect beads-viewer running\n```\n\nUpdate to the latest release with `paseo plugin update beads-viewer`. If the panel does not\nappear, `paseo plugin logs beads-viewer` shows why; the most common cause is `bv` missing from\nthe daemon's `PATH`.\n\nReleases before 0.2.0 used the plugin id `paseo-beads` and the npm package `paseo-beads`. That id\nbelongs to another plugin on paseo.cafe, so this one is now `beads-viewer`. If you installed an\nearlier release, remove it first with `paseo plugin remove paseo-beads`.\n\nTo run a local checkout instead:\n\n```bash\nnpm install && npm run typecheck && npm test\npaseo plugin install /absolute/path/to/paseo-beads-viewer\n```\n\nAfter editing source, run `paseo plugin reload beads-viewer`.\n\n## Development\n\n```bash\nnpm install\nnpm run typecheck\nnpm test\n```\n\nMobile audit — a hit here is a bug:\n\n```bash\nrg -n \"document\\.|window\\.|localStorage|navigator\\.|<[a-z]+[ >]|className=|onClick=\" client/\n```\n\n## What it contributes\n\n| Contribution | Where |\n| --- | --- |\n| Workspace panel `beads` (\"Beads Viewer\") | Workspace tab bar and the Explorer |\n| Command Center: **Open Beads Viewer** | Workspace context |\n| Command Center: **Refresh Beads Viewer** | Workspace context; re-reads `bv` then opens the panel |\n| Slash command `/beads` | Opens the panel for the current workspace |\n| Slash command `/bead ` | Opens the panel with that issue selected |\n| Attachment source **Beads issue** | Composer attachment picker |\n\n## Security and read-only behaviour\n\n- Only the daemon-side `server/` code touches Node, the process table, or the filesystem.\n Client code imports no Node module.\n- Subprocesses are spawned with `spawn` using a **literal argv** and an absolute executable\n path resolved by scanning `PATH` directly. `shell` is never enabled, so no input can be\n interpreted as a shell operator.\n- The working directory always comes from Paseo's own workspace record\n (`paseo.workspaces.ref(id).refresh()`), never from client input, and must be an existing\n absolute directory.\n- Only an explicit allowlist of read-only commands can run: `bv --version`,\n `bv --robot-triage`, `bv --robot-plan`, `bv --robot-alerts`, `bv --robot-graph`,\n `bv --robot-search`,\n ` --db list --status all --fields id,issue_type,assignee,updated_at,closed_at --format csv`\n (retried with `--fields id,issue_type,assignee` when the tracker rejects the timestamps),\n and ` --db show --json -- `. `br` reads also pass\n `--no-auto-import --no-auto-flush`. Bare `bv` is never invoked. Neither tracker argv takes any\n user input beyond the validated route and, for `show`, a pattern-checked issue id.\n- The search query is whitespace-collapsed, control-character-stripped, length-bounded, and\n passed as a single argv value. Issue ids are pattern-checked and passed after `--` so an id\n can never be read as a flag.\n- `bv` calls clear inherited `BEADS_DIR`, `BEADS_DB`, `BEADS_JSONL`, and `BD_DB` values so\n daemon-level environment configuration cannot redirect a workspace read. Tracker detail calls set those\n variables only to the validated route.\n- Every subprocess has a timeout and an output size cap, and is killed when either is\n exceeded. Unavailable binary, timeout, non-zero exit, oversized output, and malformed JSON\n are reported as distinct error codes. Plugin cleanup kills any process still running.\n- Plugin code never parses or writes `.beads/*.jsonl` or a Beads SQLite/Dolt database. It reads\n only `.beads/metadata.json` to bind tracker identity to `bv`'s selected source; issue data comes\n from CLI output. `bv` itself may refresh a `bd` compatibility export, so its calls are serialized.\n- `bv --robot-*` is the authority for ranking, recommendations, execution tracks, alerts, cycle\n detection, and velocity. The plugin derives only each issue's work state (from its status and\n its still-open blockers) and the longest remaining dependency chain, because `bv`'s own counts\n treat dependency-blocked work as unblocked and containers as ready; see the design doc. `bv` and its `source_authority`, freshness, and `data_hash` are shown as\n reported.\n- Only short-lived normalized command results are cached (15 s for the dashboard, 2 min for\n tracker identity and its validated route), invalidated purely by expiry. No derived graph is\n ever cached.\n\n## Limitations\n\n- Read-only by design. Claiming, closing, and editing issues stay in `br`/`bd`.\n- Issue detail requires an exact tracker and database route. The plugin checks `bv`, then the\n selected source's `.beads/metadata.json`; if identity or routing remains inconclusive, detail\n reads are disabled rather than guessed.\n- Attachment search has no workspace context, so it scans a bounded set of recently active\n Paseo workspaces, searches at most 4 Beads-enabled ones, and returns at most 8 items. An\n issue in a workspace outside that window will not appear.\n- Search relevance, ranking, and analysis semantics are entirely `bv`'s; the plugin only\n reshapes them.\n- Statuses, readiness values, and alert severities are treated as opaque strings, so a newer\n `bv` renders without a plugin update but without bespoke styling for new values.\n- The panel serves any Beads project, so it interprets only what Beads and `bv` define and what\n the data's structure says. Statuses are Beads' built-in set (`open`, `in_progress`, `hooked`,\n `blocked`, `deferred`, `draft`, `pinned`, `closed`, `tombstone`); a custom status declared in a\n project's `.beads/policy.yaml` is shown verbatim under **Other status**, not guessed to be ready\n or done. Groups follow parent links, never type names or id patterns. Labels are the project's\n own vocabulary: they are shown and counted as written, a label carried by every open item is\n set aside as uninformative, and no label is given a meaning — so there is no built-in \"needs a\n human\". To keep agents off some work, use `bv`'s own `BV_ROBOT_NOT_READY_LABELS`, which the\n panel's `bv` reads inherit.\n- Work states, in Beads' own terms (Ready and Waiting match `br ready` and `br blocked`):\n **Ready** — status `open`, and nothing it depends on is still open. **Waiting** — status\n `open`, but a dependency, or one of its parent's, is still open; a parent's dependency on its\n own children does not count. **In progress** — `in_progress` or `hooked`. **Held** — status\n set by hand to `blocked`, `deferred`, `draft` or `pinned`. **Other status** — a custom status.\n **Done** — `closed`. Each Board column shows its definition under its title.\n- The **Board** is a plain board: one column per work state in the order work moves — Ready,\n Waiting, In progress, Held and Other status (each only when non-empty), and Done (only with\n **Show done**) — each column\n one list that scrolls on its own, with no swimlanes. The **Filter** is a searchable\n multi-select over the project's parents and labels: work under any chosen parent, carrying any\n chosen label. Each card names its parent and shows how long ago it last changed (\"9m ago\";\n Beads records no separate status-change time). On a phone\n the columns become a state picker over one list. Issues that other issues name as parent are\n filter options and card context, never cards. Each column renders at most 60 cards with the\n rest reported as `+N more`, and a project past 2000 issues drops closed issues from the payload\n first and says so. If the graph read fails, the panel falls back to the triage and plan\n working set and says so. It is read-only: no drag, no drop, no status change.\n- Issue prose renders through a bounded in-repo Markdown subset (headings h1–h3, lists, task\n items, quotes, rules, code, bold, italic, links). HTML, images, and tables are not rendered,\n and link targets are shown as text — the panel never opens a URL.\n"},{"id":"beam","repo":"maxwell-01/paseo-beam","url":"https://github.com/maxwell-01/paseo-beam","name":"beam","description":"[Paseo](https://paseo.sh) plugins, one per folder. Each folder is a self-contained plugin with its own `package.json`, tests and README.","categories":["git","productivity","automation"],"platforms":[],"caveats":["Only one beam can be active at a time; beam out before beaming another workspace.","Overwrites your main checkout's working tree while active, then restores it on beam out.","The workspace and its main checkout must be worktrees of the same git repo."],"images":[],"themes":[],"health":{"manifestValid":false,"hasReadme":true,"hasLicense":true,"hasTests":false,"hasTypecheckScript":false,"updatedRecently":true},"scannedAt":"2026-09-25T20:16:22.886Z","addedAt":"2026-09-14T21:09:21+01:00","security":{"status":"failed","blockingFindings":2,"advisoryFindings":0,"scannedAt":"2026-09-25T20:04:23.597Z","commit":"975f8c4c062cb78ca82b203c8952e6c31621a9e6"},"scanError":"paseo-plugin.json missing or missing an 'id' field","license":"MIT","descriptionNodes":[{"type":"link","href":"https://paseo.sh","children":[{"type":"text","text":"Paseo"}]},{"type":"text","text":" plugins, one per folder. Each folder is a self-contained plugin with its own "},{"type":"text","text":"package.json","code":true},{"type":"text","text":", tests and README."}],"caveatNodes":[[{"type":"text","text":"Only one beam can be active at a time; beam out before beaming another workspace."}],[{"type":"text","text":"Overwrites your main checkout's working tree while active, then restores it on beam out."}],[{"type":"text","text":"The workspace and its main checkout must be worktrees of the same git repo."}]],"repoMeta":{"stars":1,"defaultBranch":"main","pushedAt":"2026-09-25T17:19:31Z"},"owner":{"login":"maxwell-01","avatarUrl":"https://avatars.githubusercontent.com/u/45392468?v=4"},"installNotesHtml":"Append the plugin's folder to the repo URL:
\npaseo plugin install https://github.com/maxwell-01/maxs-paseo-plugins.git:<folder>\n
","readmeText":"# Max's Paseo plugins\n\n[Paseo](https://paseo.sh) plugins, one per folder. Each folder is a self-contained plugin with its\nown `package.json`, tests and README.\n\n| Plugin | What it does |\n| --- | --- |\n| [beam](beam/) | Mirrors a workspace's working tree onto your main checkout, so a running dev environment shows its changes. |\n| [cross-daemon](cross-daemon/) | Lets agents on different Paseo daemons list and message each other, without interrupting a working agent. |\n| [repo-notes](repo-notes/) | Gives every agent your own notes for its repo, kept out of the repo and synced across daemons. |\n\n## Install\n\nAppend the plugin's folder to the repo URL:\n\n```bash\npaseo plugin install https://github.com/maxwell-01/maxs-paseo-plugins.git:\n```\n\n## License\n\nMIT. See [LICENSE](LICENSE).\n"},{"id":"beautiful-chat","repo":"ABorakati/beautiful-chat","url":"https://github.com/ABorakati/beautiful-chat","name":"beautiful-chat","description":"Paseo plugin: a beautiful chat for OMP tools, reasoning, prompts, and tasks","categories":["productivity"],"platforms":[],"caveats":["Requires Paseo 0.8 or newer","Syntax highlighting runs on the daemon over a plugin RPC","Selection actions and the pointer glow are desktop and web only"],"images":["https://raw.githubusercontent.com/ABorakati/beautiful-chat/42b61d8301b5400a67821bbbfcf99fa8b681dc37/images/hero.png","https://raw.githubusercontent.com/ABorakati/beautiful-chat/42b61d8301b5400a67821bbbfcf99fa8b681dc37/images/thread.png","https://raw.githubusercontent.com/ABorakati/beautiful-chat/42b61d8301b5400a67821bbbfcf99fa8b681dc37/docs/images/tool-bash.png","https://raw.githubusercontent.com/ABorakati/beautiful-chat/42b61d8301b5400a67821bbbfcf99fa8b681dc37/docs/images/tool-read.png","https://raw.githubusercontent.com/ABorakati/beautiful-chat/42b61d8301b5400a67821bbbfcf99fa8b681dc37/docs/images/tool-image.png","https://raw.githubusercontent.com/ABorakati/beautiful-chat/42b61d8301b5400a67821bbbfcf99fa8b681dc37/docs/images/tool-edit.png","https://raw.githubusercontent.com/ABorakati/beautiful-chat/42b61d8301b5400a67821bbbfcf99fa8b681dc37/docs/images/tool-thinking.png","https://raw.githubusercontent.com/ABorakati/beautiful-chat/42b61d8301b5400a67821bbbfcf99fa8b681dc37/docs/images/tool-mcp.png"],"themes":[],"health":{"manifestValid":true,"hasReadme":true,"hasLicense":true,"hasTests":false,"hasTypecheckScript":true,"updatedRecently":true},"scannedAt":"2026-09-25T20:16:23.821Z","addedAt":"2026-09-15T13:31:08+03:00","version":"0.1.0","security":{"status":"passed","blockingFindings":0,"advisoryFindings":0,"scannedAt":"2026-09-25T20:04:23.597Z","commit":"42b61d8301b5400a67821bbbfcf99fa8b681dc37"},"license":"MIT","paseoVersionRequirement":">=0.8.0","descriptionNodes":[{"type":"text","text":"Paseo plugin: a beautiful chat for OMP tools, reasoning, prompts, and tasks"}],"caveatNodes":[[{"type":"text","text":"Requires Paseo 0.8 or newer"}],[{"type":"text","text":"Syntax highlighting runs on the daemon over a plugin RPC"}],[{"type":"text","text":"Selection actions and the pointer glow are desktop and web only"}]],"manifest":{"id":"beautiful-chat","requirements":{"paseo":">=0.8.0"},"build":[["npm","ci","--include=dev"]]},"repoMeta":{"stars":3,"defaultBranch":"main","pushedAt":"2026-09-23T10:50:21Z"},"owner":{"login":"ABorakati","avatarUrl":"https://avatars.githubusercontent.com/u/41518783?v=4"},"installNotesHtml":"paseo plugin install ABorakati/beautiful-chat\n
\nThe manifest requires Paseo >=0.8.0. Open Settings → Plugins → Beautiful Chat for the\naccent, fonts, frosted glass, and prompt bubble options.
\n
","readmeText":"# Beautiful Chat\n\nA Paseo plugin that redraws the Oh My Pi (OMP) chat stream: tool calls, reasoning, prompts, approvals,\nand checklists. It replaces the host rendering of OMP timeline items with typed, syntax-aware cards\nthat follow the active Paseo theme.\n\n\n\nEvery screenshot here is a capture of the real component, rendered by the harness in `.showcase/`.\n[One whole turn, top to bottom](images/thread.png) shows the cards in the order the timeline draws\nthem.\n\n## Install\n\n```bash\npaseo plugin install ABorakati/beautiful-chat\n```\n\nThe manifest requires Paseo `>=0.8.0`. Open **Settings → Plugins → Beautiful Chat** for the\naccent, fonts, frosted glass, and prompt bubble options.\n\n---\n\n## Tool calls\n\n### Shell and Git\n\nTerminal frame, Bash syntax, exit code, duration, and the Git brand mark. A command that prints\nnothing says so rather than showing an empty panel.\n\n\n\n### Read\n\nThe file's own language logo, a wrapped path, line numbers, and a copy button. The path is a link:\npressing it shows the file in the machine's file manager.\n\n\n\n### Images\n\nA read of a `.png` carries no bytes through the timeline, so the host draws it as an empty code\nblock with a language badge. This card draws the file instead: a picture mark, the path as a link,\nthe pixel size and file size read from the header, and an eye control that hides the thumbnail. The\nbytes come from the plugin's own daemon-side RPC (`file.image`), which is the only side that can\nreach the file; PNG, JPEG, GIF, WebP, AVIF, BMP, ICO and SVG are recognised, and anything past\n3 MB reports its size rather than inlining a data URI.\n\n\n\n### Edit\n\nDiff rendering where adjacent removed and added rows join into one rounded block, and only the\nmarker column carries the red or green.\n\n\n\n### Reasoning tool\n\nLive thinking text, a token badge, and numbered steps.\n\n\n\n### MCP\n\nServer badge, transport, input parameters, and the response payload, each syntax-highlighted.\n\n\n\n### Eval\n\nOne card per kernel cell: the source that ran, then the text it printed.\n\n\n\n### Ask\n\nOption cards with the recommended badge, the chosen answer marked, and a typed reply labelled as\ntyped rather than shown as a selection.\n\n\n\n### Task\n\nSubagent name, type, model, and the delegated instructions.\n\n\n\n### Hub\n\nEvery `hub` op is mapped: `start`, `stop`, `restart`, `ps`, `logs`, and `describe` render the\nprocess card with its launch line, readiness, and recent output; `send`, `wait`, `inbox`, and\n`list` render the message card; `jobs` and `cancel` render the job snapshot. The cards report;\nthey carry no buttons, because a plugin cannot restart or cancel anything.\n\n\n\n### Paseo tools\n\nPaseo's own mark leads the card, and the created agent's provider carries its brand mark.\n\n\n\n---\n\n## Stream components\n\n### Reasoning trace\n\nA collapsible trace with a connected step rail, per-step duration, and a token total.\n\n\n\n### Checklist\n\nPhase name, per-task status, durations, and a blocked task with its reason.\n\n\n\n### Approval card\n\nRisk classification, the exact command, target path, working directory, and the approve or deny\nactions the host owns.\n\n\n\n### Prompt bubble\n\nThe authored turn on a raised theme surface with a square tail, a copy button, and the turn's token\nusage.\n\n\n\n### Syntax block\n\nShared by every card that shows code: language detection from the path, line numbers, diff tints,\nDevicon brand marks, and the file-manager link.\n\n\n\n---\n\n## Settings\n\n\n\n| Setting | Effect |\n| ---------------------- | ------------------------------------------------------------------ |\n| Accent colour | Follow the Paseo theme, or pick Jade, Violet, Amber, or Rose. |\n| Interface font | Embedded Inter, or the system interface face. |\n| Code glyphs | Iosevka with ligatures, or literal glyphs. |\n| Frosted glass | Blur card surfaces, or paint them solid. |\n| Enhanced prompt bubble | Off hands prompts back to Paseo, whose bubble shows pasted images. |\n| Assistant markdown | Off hands replies back to Paseo's own markdown renderer. |\n\n---\n\n## Finding text\n\nPaseo's own chat find (Ctrl/Cmd+F) cannot reach a prompt or reply this plugin draws (see\n[limitation 14](#plugin-sdk-limitations-found-while-building-this)). The plugin therefore takes\nCtrl/Cmd+F on desktop and web and opens its own find bar over the chat. The bar searches\neverything the chat has rendered, including tool cards. Enter moves to the next match, Shift+Enter\nto the previous one, and Escape closes the bar.\n\nThe bar searches only messages the chat has loaded. Scroll up first to include older history.\n\nTo keep Paseo's native search, which also searches unloaded history, turn off **Assistant\nmarkdown** and **Enhanced prompt bubble** in **Settings -> Plugins -> Beautiful Chat**. Paseo then\ndraws replies and prompts itself, and Ctrl/Cmd+F opens Paseo's find instead of the plugin's bar.\nNew messages follow the change.\nTool, reasoning, and checklist cards keep the plugin's styling, so Paseo's find still cannot reveal a\nmatch inside one of them.\n\n## Opening files\n\nA file name in a read, write, edit, or code block is a link. Pressing it calls the plugin's own\ndaemon-side RPC (`file.reveal`), which resolves the path against the agent's working directory and\nasks the platform shell to show it:\n\n| Platform | Behaviour |\n| -------- | ------------------------------------------------------ |\n| Windows | `explorer.exe /select,` selects the file. |\n| macOS | `open -R ` selects the file in Finder. |\n| Other | `xdg-open ` opens the containing directory. |\n\nA directory path opens that directory. A path the daemon cannot stat does nothing.\n\n## Unmapped output\n\nA tool the plugin has no typed card for still shows its output in the terminal frame, and a call\nthat printed nothing says so. No card renders an empty panel.\n\nThe link cannot open Paseo's own file editor: see the first limitation below.\n\n---\n\n## Plugin SDK limitations found while building this\n\nMeasured against `@getpaseo/plugin` 0.8.0 and the Paseo 0.8.0 desktop build. Each entry names the\nevidence and the workaround this plugin uses.\n\n1. **No file navigation.** Timeline renderer props are exactly `{agentId, theme, host, layout,\ntimestamp, item}`, and plugin navigation offers only `openSettings`, `openSurface`,\n `openWorkspacePanel`, `openAgentPanel`, `openAgent`, and `openWorkspace`. The host's own file tab\n target (`{kind:\"file\", path}`, reachable in-app through `?open=file:`) is not exposed, and\n the `paseo://` scheme only carries agent deep links. Workaround: a daemon-side RPC that reveals\n the path in the operating system's file manager.\n2. **Transformers see a stripped item.** The app maps its stream item to the plugin item before any\n transformer runs, and a user message keeps only `text`, `messageId`, and `clientMessageId`. Pasted\n images never reach plugin code, and the daemon timeline row stores the same item, so a server RPC\n cannot recover them either. Workaround: the **Enhanced prompt bubble** setting returns prompts to\n the host.\n3. **Interception is all or nothing.** A transformer replaces the host item completely. There is no\n way to decorate an item or keep host affordances that the plugin does not reimplement. Returning\n `undefined` is the only opt-out.\n4. **Transform results are cached per item.** Changing a preference does not re-run transformers for\n items already on screen. New items follow the change; existing ones need a reload.\n5. **Renderers get no workspace.** Props carry `agentId` only, so `cwd` and `workspaceId` need a\n second lookup through `useAgent`.\n6. **Token usage is live-only.** Usage is not persisted on timeline items, so a turn this client did\n not observe live shows no figures.\n7. **RPC names are validated late.** The host requires `^[a-z][a-z0-9._-]*$`. A camelCase name such\n as `revealPath` typechecks, then fails the whole plugin at install or reload with\n `Invalid plugin RPC method`.\n8. **The React Native runtime module is a stub in the package.** `@getpaseo/plugin/client/react-native`\n ships as `export {}`; the host injects the implementations. Bundling or testing plugin UI outside\n Paseo needs a shim, which is what `.showcase/shims` provides.\n9. **The theme carries six colours.** `PluginTheme` exposes `surface0`–`surface2`, `border`,\n `foreground`, `foregroundMuted`, `accent`, `accentForeground`, and three status colours. Every\n other surface, including code backgrounds and diff tints, must be derived with alpha; that is what\n `client/components/theme-tokens.ts` exists for.\n10. **No CSS escape hatch.** React Native styles drop unknown keys, so `backdrop-filter` is\n impossible through the style API. Frosted glass is a hand-injected `