dsh-beads-viewer

浅色 Light	深色 Dark

✨ Features

More screenshots

Issue detail — description first, secondary blocks on the wash:

Light	Dark

The full badge palette, contrast-checked in both themes:

Light	Dark

The interface follows the Host language:

🚀 Installation

# from the registry
dsh plugin --profile <name> add dsh-beads-viewer

# or from a checkout, which links the profile entry to this directory
dsh plugin --profile <name> add /path/to/dsh-beads-viewer

Then restart the Harness so the new bundle's client half loads (a hard browser refresh also picks up a newer bundle). The tab appears in the right sidebar's new-tab guide.

A linked install picks up edits on the next load with no reinstall; a registry install is a normal package, so upgrading means running add again.

🔧 How it reads the tracker

The Host half serves one read-only route, GET /beads-viewer/api:

?force=1 bypasses the four-second list cache. Three properties are deliberate:

• It shells out to bd, and reads no database file. A Beads workspace is either a Dolt server or a SQLite file depending on how it was initialised, and the schema moves between bd releases. bd --json is the interface that stays correct across both — and when a workspace is too old, bd prints the migration instruction, which the panel shows verbatim rather than guessing at.
• It is read-only. Every read goes through one readBd helper that prepends bd --readonly, so the guarantee is structural rather than a per-call habit — a test asserts the flag is on the argv. No route mutates anything.
• It only answers itself. The route refuses non-loopback peers, and ?cwd= must be an existing directory that (or whose parent) holds .beads. The directory is then used as the workspace for every bd call, so a request cannot point bd at an arbitrary tree.

📁 Layout

index.js            Host half: the read-only route and the bd calls
client.js           Client half: the sidebar tab, panel, and Markdown renderer
cordis.patch.yml    The bundle patch that mounts the host row
locale/{en,zh}.json Plugin title and description for the Plugin Manager
icon.svg            Panel artwork
test/               Five suites, 103 checks
docs/               Screenshots referenced by this README

npm test

📋 Known limits

• Reading the tracker costs two bd processes per refresh (list + ready; ~0.8s on a 380-issue project); the list is cached four seconds, refreshes when the window regains focus, and the Refresh control bypasses the cache for its one request.
• The list is capped at 2000 issues and 200 comments per issue.
• The panel is a viewer. Creating, editing and closing issues stays with bd and with the agent, which is the one place that can report exactly what changed.
• Markdown comes from a small built-in renderer rather than a full CommonMark implementation: it covers what issue bodies actually use and adds file and issue links on top.

📄 License

MIT