Sweep 65 markdown files across docs/, website/, claude-plugin/, examples/, integrations/, and root to replace removed `bd daemon` references with current Dolt server mode equivalents. CHANGELOG.md preserved per policy. Key replacements: - `bd daemon start/stop/status` → `bd dolt start/stop` / `bd doctor` - `bd daemons killall/health/logs` → `bd dolt stop` / `bd doctor` - `--no-daemon` flag → removed (embedded mode is default) - `BEADS_NO_DAEMON` / `BEADS_DAEMON_MODE` env vars → removed - `.beads/bd.sock` → removed - "daemon mode" / "direct mode" → "server mode" / "embedded mode" - daemon.pid/daemon.log → .beads/dolt/sql-server.pid/.log Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Executed-By: beads/polecats/topaz Rig: beads Role: polecats
3.4 KiB
| id | title | sidebar_position |
|---|---|---|
| ide-setup | IDE Setup | 3 |
IDE Setup for AI Agents
Configure your IDE for optimal beads integration.
Claude Code
The recommended approach for Claude Code:
# Setup Claude Code integration
bd setup claude
This installs:
- SessionStart hook - Runs
bd primewhen Claude Code starts - PreCompact hook - Ensures
bd syncbefore context compaction
How it works:
- SessionStart hook runs
bd primeautomatically bd primeinjects ~1-2k tokens of workflow context- You use
bdCLI commands directly - Git hooks auto-sync the database
Verify installation:
bd setup claude --check
Manual Setup
If you prefer manual configuration, add to your Claude Code hooks:
{
"hooks": {
"SessionStart": ["bd prime"],
"PreCompact": ["bd sync"]
}
}
Cursor IDE
# Setup Cursor integration
bd setup cursor
This creates .cursor/rules/beads.mdc with beads-aware rules.
Verify:
bd setup cursor --check
Aider
# Setup Aider integration
bd setup aider
This creates/updates .aider.conf.yml with beads context.
Verify:
bd setup aider --check
GitHub Copilot
For VS Code with GitHub Copilot, use the MCP server:
# Install MCP server
uv tool install beads-mcp
Create .vscode/mcp.json in your project:
{
"servers": {
"beads": {
"command": "beads-mcp"
}
}
}
For all projects: Add to VS Code user-level MCP config:
| Platform | Path |
|---|---|
| macOS | ~/Library/Application Support/Code/User/mcp.json |
| Linux | ~/.config/Code/User/mcp.json |
| Windows | %APPDATA%\Code\User\mcp.json |
{
"servers": {
"beads": {
"command": "beads-mcp",
"args": []
}
}
}
Initialize beads and reload VS Code:
bd init --quiet
See GitHub Copilot Integration for detailed setup.
Context Injection with bd prime
All integrations use bd prime to inject context:
bd prime
This outputs a compact (~1-2k tokens) workflow reference including:
- Available commands
- Current project status
- Workflow patterns
- Best practices
Why context efficiency matters:
- Compute cost scales with tokens
- Latency increases with context size
- Models attend better to smaller, focused contexts
MCP Server (Alternative)
For MCP-only environments (Claude Desktop, no shell access):
# Install MCP server
pip install beads-mcp
Add to Claude Desktop config:
{
"mcpServers": {
"beads": {
"command": "beads-mcp"
}
}
}
Trade-offs:
- Works in MCP-only environments
- Higher context overhead (10-50k tokens for tool schemas)
- Additional latency from MCP protocol
See MCP Server for detailed configuration.
Git Hooks
Ensure git hooks are installed for auto-sync:
bd hooks install
This installs:
- pre-commit - Validates changes before commit
- post-merge - Imports changes after pull
- pre-push - Ensures sync before push
Check hook status:
bd info # Shows warnings if hooks are outdated
Verifying Your Setup
Run a complete health check:
# Check version
bd version
# Check project health
bd doctor
# Check hooks
bd hooks status
# Check editor integration
bd setup claude --check # or cursor, aider