Collect a quote from each maker
fw-s3tfw-s2l
Bud shows your project’s Beads issues as one simple board. Every task shows who made it and where its agent is, in the same place you review the pages and the code.
fw-s3tfw-s2l
fw-a5hfw-epic
fw-r8tfw-epic
fw-m2xfw-studio
fw-7qdfw-epic
fw-epic
fw-alt-reviewfw-quality
fw-carefw-epic
fw-care-clayfw-care
fw-contrastfw-quality
fw-error-pagefw-quality
fw-focusfw-quality
fw-keyboardfw-quality
fw-launch-readyfw-quality
fw-measurefw-quality
fw-mobile-passfw-quality
fw-offlinefw-quality
fw-press-captionfw-press-kit
fw-press-manifestfw-press-kit
fw-printfw-epic
fw-quality
fw-reduce-motionfw-quality
fw-release-notefw-quality
fw-shipping-notefw-epic
fw-studio-creditfw-studio
fw-s2lfw-studio
fw-studio
fw-p4nfw-epic
fw-k3pfw-epic
fw-motionfw-quality
fw-press-kit
fw-touchfw-quality
fw-gallery-draftfw-quality
Tasks sit in status columns or in a list, and follow changes from bd, agents and other tabs on their own. With the factory on, the columns are its steps and agents move the cards; you only close or reopen them.
fieldwork · Board
Every task has its own page: its title and description, edited in place, who made it, its epic and linked tasks, the agent’s run, the discussion and its activity.
fw-k3p · In progress · Mara Lind, 2 days ago
Give the headline more room above the collection. Keep the same spacing on /collection.
Epic · Launch the autumn collectionLinked · Move the studio story closer to the topBud has no task storage of its own. It reads and writes the Beads workspace in your project through the bd CLI, so your plan stays in your repository and in your tools. Other trackers can plug in through an adapter.
# Once per project
bd init
# Then run your dev server as usual
npm run devBrowsing never initializes, migrates or syncs.
Every change checks the task hasn’t moved on.
Sync pulls and pushes the remote you configured.
Without Beads, bud doctor says what’s missing.
Add Bud to Vite, pick a few pages and start the conversation. Free, and one npm install away.