Paseo plugins are trusted, unsandboxed code. Review the source before installing it on the daemon\nhost.
\nFrom GitHub:
\npaseo plugin add omercnet/paseo-plugins:paseo-beads\nFrom a local checkout on the Paseo daemon host:
\ngit clone https://github.com/omercnet/paseo-plugins.git\ncd paseo-plugins/paseo-beads\nbun install --frozen-lockfile\npaseo plugin install \"$PWD\"\nOpen a workspace, choose New tab in Explorer, then select Beads. You can also run Open\nBeads from the Command Center while viewing a workspace or one of its agents.
","readmeText":"# Paseo Beads\n\nA dependency-aware Beads work queue for every Paseo workspace. Paseo Beads turns active issues into\na read-only delivery view that makes the ready frontier, work in progress, and blockers immediately\nvisible.\n\nIt adds a workspace-scoped **Beads** Explorer panel and an **Open Beads** Command Center item.\n\n## Screenshots\n\nIssue IDs, titles, assignees, labels, and issue details in these screenshots are synthetic. They do\nnot contain data from a real Beads project.\n\n### Wide\n\n\n\n### Compact\n\n\n\n## What it shows\n\n- Active issues grouped into **Ready frontier**, **In progress**, **Blocked**, and **Other** lanes.\n- Priority, issue ID, title, type, assignee, labels, and relationship and comment counts on each row.\n- Lane totals, text search over ID, title, assignee, and labels, and **All**, **P0–P1**, and\n **Assigned** filters.\n- A detail view with status, readiness, priority, type, assignee, parent, labels, description,\n acceptance criteria, design, notes, dependencies, dependents, and update time.\n- A side-by-side list and detail view when space permits, with list/detail navigation in compact\n layouts.\n- A virtualized issue list, descriptive accessibility labels, and focus restoration when navigating\n between the compact list and detail view.\n\nWithin each lane, issues are ordered by priority, most recent update, then ID. In-progress and hooked\nissues enter **In progress** first; remaining blocked issues enter **Blocked**; ready issues enter\n**Ready frontier**; all remaining active issues enter **Other**.\n\n## How it works\n\nThe panel calls workspace-scoped Paseo plugin RPC handlers. On the daemon host, each handler resolves\nthe workspace directory through Paseo and executes the `bd` CLI with `--readonly` and `-C`:\n\n- The list handler runs `bd list --json --sort priority`, then runs one authoritative\n `bd list --ready --json --limit 0` query and intersects its IDs with the displayed issues.\n- Selecting an issue runs `bd show