Beadsmith a web UI for Beads	Docs	read
Source	github
Appearance

A web dashboard for Beads

Beadsmith reads your Beads issue databases from a Dolt SQL server and shows every project, issue, dependency and recent change in one place, for you and the people you work with. Agents keep doing the work with bd; Beadsmith only reads.

Status	Early. No versioned releases yet: `main` is what ships, and anything can change.
Reads	Beads databases on a Dolt sql-server, written by bd 1.1 to 1.3
Runs	On your own machine or server, with Docker Compose or NixOS
Try it	Two commands and a sample dataset: quickstart
License	MIT, source on GitHub

Beadsmith showing the lighthouse sample project. A list groups twelve issues under Rolling, Lined up and Stalled; the issue "Alerts flap during rolling deploys" is open on the right with its metadata, parent and two comments. — fig. 1 The lighthouse sample project: issues grouped by state, with one open in the reading pane.

What's in it6

01 Every project at once Parade, list and board views per project, a Ready deck of unblocked work across all of them, and an activity log.
02 Read-only by design Beadsmith never runs bd or writes issue rows. It needs SELECT on your Dolt server and nothing else.
03 Accounts Email and password sign-in with admin and member roles. Sign-up stays closed unless an admin opens it.
04 Backups Scheduled dumps of every project to any S3-compatible bucket, optionally encrypted with your passphrase.
05 Agents, optionally Send an issue to an agent to discuss, elaborate, close or tackle it, through any runner that accepts a signed webhook.
06 Keyboard first Press ? on any page for the keys it answers. Usable at phone width.

Views4

The UI is still moving, so these are sketches until it settles. Figure 1 is a real capture.

[screenshot pending] board

lighthouse 12        parade  list  [board]

OPEN 8          IN PROGRESS 3   BLOCKED 1
┌────────────┐  ┌────────────┐  ┌────────────┐
│● 1     P1  │  │● 2.3   P0  │  │● 4     P1  │
│Status page │  │Alerts flap │  │Checks time │
│v1          │  │during roll…│  │out on IPv6…│
└────────────┘  └────────────┘  └────────────┘
┌────────────┐  ┌────────────┐
│● 2     P1  │  │● 3     P1  │
│Alerting    │  │Warn before │
└────────────┘  └────────────┘
┌────────────┐  ┌────────────┐
│● 5     P2  │  │● 1.3   P2  │
│Upgrade the…│  │Cache the s…│
└────────────┘  └────────────┘

fig. 2 Board: one column per status, cards sorted by priority.

[screenshot pending] ready

READY  unblocked issues across all projects

● lh-1    P1  Status page v1        lighthouse
● pan-4   P1  Weekly meal plan      pantry
● th-3    P1  Redirect the old URLs trailhead
● lh-2.4  P2  Choose an email pro…  lighthouse
● pan-6   P2  Convert between cup…  pantry
● lh-5    P2  Upgrade the HTTP cl…  lighthouse
● th-4    P2  Search with a keybo…  trailhead
● lh-6    P3  Write the self-host…  lighthouse
● pan-8   P3  Accessibility pass …  pantry
● lh-7    P4  Probe from several …  lighthouse

fig. 3 Ready: every unblocked issue across all projects, one deck.

[screenshot pending] activity

ACTIVITY LOG

● 9m   claude-agent  status changed  pan-2
● 41m  alex          commented       pan-5
● 2h   maya          updated         lh-2.3
● 14h  sam           commented       lh-2.3
● 1d   priya         status changed  lh-4
● 1d   maya          commented       lh-2.3
● 2d   rae           created         th-3
● 3d   sam           created         lh-2.3
● 4d   lee           closed          th-1.1
● 6d   coding-agent  closed          lh-1.1

fig. 4 Activity log: recent changes from people and agents, newest first.

[screenshot pending] phone

≡ lighthouse      /

ROLLING 3
● 2.3 P0 Alerts flap…
● 3   P1 Warn before…
● 1.3 P2 Cache the s…

LINED UP 8
● 2   P1 Alerting
● 1   P1 Status page…
● 5   P2 Upgrade the…
● 2.4 P2 Choose an e…

STALLED 1
● 4   P1 Checks time…

fig. 5 At phone width the same parade, one column.

How it fits

   people                              people and agents
      │ browser                                │ bd
      ▼                                        ▼
┌───────────┐     read-only SQL      ┌──────────────────┐
│ Beadsmith │ ─────────────────────▶ │ Dolt sql-server  │
└─────┬─────┘                        │ one database per │
      │                              │ Beads project    │
      │ signed webhook               └──────────────────┘
      │ (optional)                             ▲
      ▼                                        │ bd
┌─────────────┐                                │
│ your runner │ ──── starts an agent ──────────┘
└─────────────┘

Beads keeps each project's issues in a Dolt database. People and agents change them with bd, as they do today. Beadsmith connects to the same sql-server with an account that can only read, and shows every database on it.

When an admin sends an issue to an agent, Beadsmith records the request and hands it to your runner over a signed webhook. The agent then changes Beads with bd like any other contributor. Beadsmith itself has no Beads CLI, no project checkout and no way to write to Beads.

Try it

You need Docker with Compose v2.

git clone https://github.com/Vonshlovens/beadsmith
cd beadsmith
docker compose -f quickstart/compose.yaml up -d --build --wait
docker compose -f quickstart/compose.yaml exec beadsmith cat /state/setup-token

Open http://localhost:4321, paste the token and create your admin account. Three sample projects (lighthouse, pantry, trailhead) are waiting, with a few weeks of made-up history and two agents mid-task.

Everything stays on your machine: Beadsmith listens on 127.0.0.1 only, Dolt is not published at all, and every secret is generated on first start. The first start builds the image, usually one to three minutes.

Then point it at your own projects: use your own Beads projects.