bud.sh

Keep building.
Bring the context.

Connect Bud to the project you already run. Review the pages, agree on a change, hand it to your agent and share the decision through Git.

Follow the setup guideExplore the canvas

  1. Add Bud
    to your dev server.

    Install Bud and add it next to your framework’s Vite plugins. Bud starts with Vite, on its own port, and nothing changes in your production build.

    Installation

    Terminal

    npm install -D @bud.sh/app

    vite.config.ts

    import { defineConfig } from 'vite'
import { bud } from '@bud.sh/app/vite'

export default defineConfig({
  plugins: [bud()],
})

  2. Choose the pages
    worth reviewing.

    Not the whole sitemap: the few pages your next change touches. Use real URLs, and give long-lived pages a stable id.

    Configuration

    bud.config.ts

    import { defineConfig } from '@bud.sh/app'

export default defineConfig({
  name: 'Fieldwork',
  routes: [
    '/',
    { id: 'collection', path: '/collection', title: 'Collection' },
    { id: 'vase', path: '/collection/vase', title: 'Product' },
  ],
})

  3. Point at
    what should change.

    Click the spot on the page, or select the lines in Files. Say what the result should be, so the request still makes sense after the layout moves.

    Comments

    Hard to act on

    Which page? Which part?

    “This part feels a little off.”

    Ready to build

    A page, a detail, an outcome.

    “Give this headline more room above the collection. Keep the same spacing on /collection.”

  4. Hand the context
    to your agent.

    Copy the thread into your editor or agent, or make it a task and let Bud start one in a sandbox. The page, the detail and the decision are already there. Then move the thread along as the work happens.

    Working with agents

    Handoff

    Route: /collection
Change: More room above the collection, same as on /.
Check: / and /collection in both themes.
    • Without status
    • In progress
    • Needs approval
    • Resolved

  5. Share the decision
    when you sync.

    Comments save locally to your Beads workspace. Sync merges everyone’s threads through your Beads remote, and your source branch never moves.

    Sharing

    One explicit sync

    Your Beads remote carries the conversation.

    MMayaComments and syncs
    JJonasSyncs, replies, syncs again
    MMayaSyncs and sees the reply

Give your next change
a little Bud.

Add Bud to Vite, pick a few pages and start the conversation. Free, and one npm install away.

Read the setup guide