Files
beads/website/docs/recovery/sync-failures.md
Steve Yegge 584608a14e feat: add llms.txt standard support for AI agent discoverability (#784)
Cherry-picked website/, scripts/generate-llms-full.sh, and deploy-docs.yml
from joyshmitz's PR. Fixed workflow to trigger on main branch instead of
docs/docusaurus-site.

Features:
- Docusaurus documentation site with llms.txt support
- Environment-variable driven config (defaults to steveyegge org)
- Automated llms-full.txt generation from docs
- GitHub Pages deployment workflow

Co-authored-by: joyshmitz <joyshmitz@users.noreply.github.com>

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Executed-By: beads/crew/dave
Rig: beads
Role: crew
2025-12-30 18:27:50 -08:00

1.3 KiB

sidebar_position, title, description
sidebar_position title description
5 Sync Failures Recover from bd sync failures

Sync Failures Recovery

This runbook helps you recover from bd sync failures.

Symptoms

  • bd sync hangs or times out
  • Network-related error messages
  • "failed to push" or "failed to pull" errors
  • Daemon not responding

Diagnosis

# Check daemon status
bd daemon status

# Check sync state
bd status

# View daemon logs
cat .beads/daemon.log | tail -50

Solution

Step 1: Stop the daemon

bd daemon stop

Step 2: Check for lock files

ls -la .beads/*.lock
# Remove stale locks if daemon is definitely stopped
rm -f .beads/*.lock

Step 3: Force a fresh sync

bd doctor --fix

Step 4: Restart daemon

bd daemon start

Step 5: Verify sync works

bd sync
bd status

Common Causes

Cause Solution
Network timeout Retry with better connection
Stale lock file Remove lock after stopping daemon
Corrupted state Use bd doctor --fix
Git conflicts See Merge Conflicts

Prevention

  • Ensure stable network before sync
  • Let sync complete before closing terminal
  • Use bd daemon stop before system shutdown