beadsiderun the repo
my agents keep a backlog. beadside is where i read it and talk back.
a local board over beads, the issue tracker my agent sessions file their work into. find a thing, read what happened, leave a note the next session reads first. the bit i like: the beads event journal is only a doorbell. a ring makes the server re-export the whole store, and the page hears "changed" only when a hash of that export actually moved, so it stays live without twitching on every write.
Beads 1.3.0 adds a change feed (bd events) and an HTTP API (bd serve)
issue #1 came from a beads maintainer: the tracker had grown a change feed, so the board learned to listen to it.
react · typescript · hono · tanstack query · sse
public since 15 sep 2026 · mit licence
enlarge · 2 shots









