Local UI for Beads — Collaborate on issues with your coding agent.
npm install beads-ui
Local UI for the bd CLI – Beads
Collaborate on issues with your coding agent.
- ✨ Zero setup – just run bdui start
- 📺 Live updates – Monitors the beads database for changes
- 🔎 Issues view – Filter and search issues, edit inline
- ⛰️ Epics view – Show progress per epic, expand rows, edit inline
- 🏂 Board view – Blocked / Ready / In progress / Closed columns
- ⌨️ Keyboard navigation – Navigate and edit without touching the mouse
``sh`
npm i beads-ui -gIn your project directory:
bdui start --open
See bdui --help for options.
Issues
Epics
Board
- BD_BIN: path to the bd binary.BDUI_RUNTIME_DIR
- : override runtime directory for PID/logs. Defaults to$XDG_RUNTIME_DIR/beads-ui
or the system temp dir.HOST
- : overrides the bind address (default 127.0.0.1).PORT
- : overrides the listen port (default 3000).
These can also be set via CLI options: bdui start --host 0.0.0.0 --port 8080
- macOS/Linux are fully supported. On Windows, the CLI uses cmd /c start toprocess.kill
open URLs and relies on Node’s semantics for stopping the
daemon.
- 🔨 Clone the repo and run npm install.npm start
- 🚀 Start the dev server with .npm link
- 🔗 Alternatively, use to link the package globally and runbdui start
from any project.
- The codebase uses the debug package with namespaces like beads-ui:*.localStorage.debug = 'beads-ui:*'
- Enable logs in the browser by running in DevTools:
- then reload the pageDEBUG
- Enable logs for Node/CLI (server, build scripts) by setting :DEBUG=beads-ui:* bdui start
- DEBUG=beads-ui:* node scripts/build-frontend.js`
-
MIT