How local changes become durable remote commits
BRB keeps the local repo primary, batches file-system changes after a pause, syncs deltas to a repo agent, and commits remotely with conversation-aware messages.
Source of truth
- The local repo is primary.
- The remote Cloudflare repo agent mirrors local state.
- BRB does not auto-commit the user’s local repo.
Adaptive batching
| Parameter | Description | Default |
|---|---|---|
| quiet-window-ms | Wait for a natural editing pause before syncing. | 5000 |
| max-batch-window-ms | Force a sync if continuous editing goes on for too long. | 30000 |
| min-resync-gap-ms | Prevent noisy back-to-back syncs. | 2000 |
Commit message generation
Remote commit messages use changed files, checkpoints, recent commit history, and synced conversation context when available. Low-signal incidental changes are down-ranked so the title tracks the real user-facing work.
Commit authorship
BRB prefers your local git user.name if it exists, and falls back to BRB Sync for remote sync-created commits.
Sync states in the UI
- Not watching means no watcher or daemon heartbeat is active.
- Collecting means BRB is still batching changes.
- Syncing means a delta is being pushed right now.
- Paused means sync is blocked, for example by secret scanning.
- Watching means the repo is healthy and currently up to date.