f5feee0d20
- Stub out 'bd repos' command with deprecation message - Remove 140+ lines of global daemon/multi-repo docs from ADVANCED.md - Add architecture section explaining daemon/MCP/beads roles (LSP model) - Update AGENTS.md, MCP README, FAQ.md to emphasize per-project daemons - Update commands/daemon.md and commands/repos.md Closes #140 Global daemon was removed in v0.16.0 due to cross-project pollution risks. bd now uses per-project local daemons (one per workspace) for complete database isolation, following LSP architecture patterns. Amp-Thread-ID: https://ampcode.com/threads/T-c45147dc-8939-43bf-8fbd-303ed4a8d845 Co-authored-by: Amp <amp@ampcode.com>
1.4 KiB
1.4 KiB
description: Run background sync daemon
argument-hint: [--stop] [--status] [--health]
Run a per-project background daemon that manages database connections and syncs with git.
Per-Project Daemon (LSP Model)
Each project runs its own daemon at .beads/bd.sock for complete database isolation.
On Windows this file stores the daemon's loopback TCP endpoint metadata—leave it in place so bd can reconnect.
Why per-project daemons?
- Complete database isolation between projects
- No cross-project pollution or git worktree conflicts
- Simpler mental model: one project = one database = one daemon
- Follows LSP (Language Server Protocol) architecture
Note: Global daemon support was removed in v0.16.0. The --global flag is no longer functional.
Common Operations
- Start:
bd daemon(auto-starts on firstbdcommand) - Stop:
bd daemon --stop - Status:
bd daemon --status - Health:
bd daemon --health- shows uptime, cache stats, performance metrics - Metrics:
bd daemon --metrics- detailed operational telemetry
Sync Options
- --auto-commit: Automatically commit JSONL changes
- --auto-push: Automatically push commits to remote
- --interval: Sync check interval (default: 5m)
The daemon provides:
- Connection pooling and caching
- Better performance for frequent operations
- Automatic JSONL sync (5-second debounce)
- Optional git sync