Troubleshooting
Troubleshoot sync, daemon, and resume issues
When something is off, the fastest path is to check watcher state, local registry, daemon logs, and the hosted repo timeline together.
Operations
•https://docs.brbgit.com/troubleshootingSync is not happening
- Confirm the repo was registered with brb init.
- Make sure watch mode or the daemon is actually running.
- Wait until the quiet window has elapsed after your last edit.
- Check the project page for the current sync state: Watching, Collecting, Syncing, or Paused.
Daemon and local state
bash
launchctl list | grep com.brb.daemon
tail -f ~/.brb/logs/daemon.out.log
tail -f ~/.brb/logs/daemon.err.log- Registry: ~/.brb/registry.json
- Logs: ~/.brb/logs/daemon.out.log and daemon.err.log
- Legacy ~/.git-agent state is still read when present, which can affect older machines.
Sync is paused
Paused means the local watcher is alive, but BRB deliberately stopped syncing because it encountered blocked content, most commonly from secret scanning or a protected internal path.
- Change or remove the blocked content locally.
- Wait for the watcher to observe the new safe state.
- The next successful sync should record recovery automatically.
Not logged in
bash
brb loginBRB keeps repos private per account. If the CLI tells you to log in, create or refresh the saved token first.