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>
25 lines
808 B
Markdown
25 lines
808 B
Markdown
---
|
|
description: DEPRECATED - Multi-repository management
|
|
argument-hint: [command]
|
|
---
|
|
|
|
**DEPRECATED:** This command is no longer functional.
|
|
|
|
Global daemon support was removed in v0.16.0. bd now uses per-project local daemons (LSP model) for complete database isolation.
|
|
|
|
## Why Was This Removed?
|
|
|
|
- Cross-project database pollution risks
|
|
- Git worktree conflicts
|
|
- Complexity in multi-workspace scenarios
|
|
|
|
## Multi-Repo Workflows Now
|
|
|
|
For working across multiple beads projects:
|
|
- Use your editor/shell to switch between project directories
|
|
- Each project has its own daemon at `.beads/bd.sock`
|
|
- Run `bd ready` in each project individually
|
|
- Use single MCP server instance that routes to per-project daemons
|
|
|
|
See [ADVANCED.md](../ADVANCED.md#architecture-daemon-vs-mcp-vs-beads) for architecture details.
|