Collect a quote from each maker
fw-s3tfw-s2l
Bud puts your pages, your code and every conversation about them in one place. Point at the detail, agree on the change and keep the decision in Git.
Objects made to be lived with. Slowly considered, naturally imperfect.
Useful things, honest materials, and a little room to breathe. That’s where we begin.
A small collection of pieces that make a space feel like yours.
We’re a small design studio with a simple belief: the things around us should earn their place.
We work with natural materials, small runs, and people who care about what they make. Every piece starts with a conversation.
Bud opens on Pages: the routes you configured beside a real browser of your running site, with tabs, history and an address bar that stays on your site.
Objects made to be lived with. Slowly considered, naturally imperfect.
Useful things, honest materials, and a little room to breathe. That’s where we begin.
The pages from your config, searchable.
Tabs, back, forward, reload and home, and the address bar never leaves your site.
The page you see is part of Bud’s address, loaded on your own origin.
Your project’s Beads issues as a board. Plan, claim and close work in the same place you review it.
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
Bud reads and writes your issues through the bd CLI, with explicit sync.
Group by epic, filter by anything.
Dependencies decide what can start next; claims and closes go straight to Beads.
Browse the project, open a file and review what changed, right next to the pages it affects.
Diffs against HEAD or any commit, hunk by hunk.
Bud never overwrites changes it hasn’t seen, and moved or deleted originals can be restored.
Select lines to start a thread with your team, beside the page threads.
Add Bud to the Vite config you already have and pick the pages worth reviewing. Then run your usual dev command.
Installation guideimport { defineConfig } from 'vite'
import { bud } from '@bud.sh/app/vite'
export default defineConfig({
plugins: [bud()],
})import { defineConfig } from '@bud.sh/app'
export default defineConfig({
name: 'Fieldwork',
routes: ['/', '/collection', '/studio'],
})A web project on Vite and a Git repository. Add Bud to Vite, list a few routes and run your usual dev command. Bud finds your app and opens next to it.
Yes. Bud is free while it’s in private development. The installation guide builds a local package; an npm release comes later.
No. You bring the context to your editor or agent yourself, and Bud keeps it specific: the page, the detail and what was decided. It never runs an agent on its own.
Comments save to your project’s Beads workspace. Sync pushes them through your Beads remote, and teammates sync to pull them in. There is no server or account to set up.
For tasks and comments, by default. They’re stored in the project’s Beads workspace, so they appear once you install the bd CLI and run bd init. Canvas and Files work in any Git repository, and other storage can plug in through an adapter.
Anything that serves its pages through Vite’s HTML pipeline. Custom server rendering needs one small integration, described in the docs.
Add Bud to Vite, pick a few pages and start the conversation. Free while in private development.