Sharing

Bud saves every task change, comment, reply and status to your storage adapter. With the default Beads adapter, they're written to the project's Beads database. Your working tree, staged changes and current branch are never touched.

Sync

Sync comments in the canvas toolbar and Sync on the task board pull from your Beads remote and push your changes, the same as bd dolt pull and bd dolt push. They use the remote and credentials Beads already has, and never force-push.

1. You comment and sync.
2. A teammate syncs, replies and syncs again.
3. You sync to get the reply.

Pushing your source code doesn't sync Beads, and syncing Beads doesn't push code. Without a configured Beads remote, sync explains what's missing and your changes stay local.

Conflicts

Every write checks that the thread or task hasn't changed since you loaded it. If it has, Bud keeps your draft and shows the current version, so you decide what to keep. Nothing is overwritten.

Git comments

With the gitComments() plugin, discussions are committed to refs/heads/bud/comments through a temporary index instead. Sync comments then fetches that branch, merges it and pushes it to origin, or to the remote set with comments: { remote: 'review' }.

What is stored

Messages, author names and emails, timestamps, statuses, anchors and task links. Everything you sync becomes part of the remote's history, so use a private remote for private projects.