IDE Setup

Configure your IDE or coding agent for optimal beads integration.

Last reviewed: 2026-07-10

Freshness source: cmd/bd/setup*.go and internal/recipes/.

How bd setup Works

The bd setup command uses a recipe-based architecture: recipes define where beads workflow instructions are written. Built-in recipes cover popular tools, and you can add custom recipes for any other tool (see Custom Recipes below). Integrations complement each other — you can install several at once.

bd setup --list             # Show all available recipes
bd setup claude             # Install an integration (claude, cursor, gemini, ...)
bd setup claude --check     # Verify installation
bd setup claude --remove    # Uninstall

bd prime is the single source of truth for operational workflow commands. Each integration's instruction file either points to bd prime (hook-enabled agents) or carries the full command reference (AGENTS-first agents).

Template Profiles

Each integration writes one of two profiles that control how much content goes into the tool's instruction file (AGENTS.md, CLAUDE.md, GEMINI.md, or .github/copilot-instructions.md):

Hook-enabled agents use the minimal profile because bd prime injects full context at session start. AGENTS-first agents use the full profile because their instruction file remains the primary integration surface. Codex is skill-based instead: it uses .agents/skills/beads/SKILL.md, with managed AGENTS.md guidance telling Codex when to use the skill.

Profile precedence: if a file already has a full profile section and a minimal profile tool installs to the same file (for example via symlinks), the full profile is preserved to avoid information loss.

Policy Profiles

Template profiles control how much text gets installed. Policy profiles control what an agent is authorized to do at handoff:

The generated beads section and bd prime default to conservative git authority. Set the profile explicitly with the agent.profile config key or the BD_AGENT_PROFILE environment variable (values: conservative, minimal, team-maintainer; the env var takes precedence; an unrecognized value falls back to conservative):

bd config set agent.profile team-maintainer
# or, for a single session/process:
BD_AGENT_PROFILE=team-maintainer bd prime

bd prime layers this explicit knob on top of its per-branch git-authority checks (stealth mode, no git remote, ephemeral branch, no-push); those hard constraints still take precedence, and team-maintainer remains subordinate to any explicit "do not commit"/"do not push" instruction. Beads never infers team-maintainer authority merely because a remote exists — it must be set via this knob (or, for tools without config access, via top-level project instructions).

Managed Sections

bd setup factory, bd setup mux, and bd setup opencode append a beads section to AGENTS.md, wrapped in BEGIN/END BEADS INTEGRATION HTML-comment markers. The begin marker carries version, profile, and hash metadata (e.g. <!-- BEGIN BEADS INTEGRATION v:1 profile:full hash:19cc25d9 -->) so --check can report missing, stale, or current; legacy markers without metadata are auto-upgraded on the next install or update. Re-running setup updates the existing section in place (idempotent), and --remove deletes only the managed section — the rest of your AGENTS.md is untouched.

bd setup codex uses its own marker pair (BEGIN/END BEADS CODEX SETUP). Running it alongside bd setup factory or bd setup mux against the same AGENTS.md leaves two managed sections side by side; each recipe's --check inspects only its own section, and each --remove removes only its own section.

One AGENTS.md works across many tools — Factory Droid, Mux, OpenCode, Cursor, Zed, Jules, and other AGENTS.md-aware assistants — so bd setup factory is a good starting point when your team mixes AI tools.

Claude Code

The recommended approach for Claude Code:

bd setup claude            # Project install: .claude/settings.json
bd setup claude --global   # Global install: ~/.claude/settings.json

This installs:

• SessionStart hook - Runs bd prime --hook-json, which wraps the workflow context in the JSON envelope Claude Code expects. SessionStart fires when a session starts, resumes, or clears, and again after context compaction — no separate compaction hook is needed.
• Minimal beads section in CLAUDE.md - A pointer to bd prime, managed with hash/version markers for safe updates and --check freshness detection.

If the beads Claude Code plugin is installed, hooks are plugin-managed and bd setup claude skips writing them, so bd prime doesn't fire twice per session.

How it works:

1. SessionStart hook runs bd prime --hook-json automatically
2. bd prime injects ~1-2k tokens of workflow context
3. You use bd CLI commands directly
4. Git hooks refresh exports and legacy fallbacks; Dolt remotes handle sync

Flags:

Restart Claude Code after installation for the hooks to take effect.

Verify installation:

bd setup claude --check

Manual Setup

If you prefer manual configuration, add the hook to your Claude Code settings:

{
  "hooks": {
    "SessionStart": [
      {
        "matcher": "",
        "hooks": [
          { "type": "command", "command": "bd prime --hook-json" }
        ]
      }
    ]
  }
}

Cursor IDE

bd setup cursor            # Always-applied rules file

This creates .cursor/rules/beads.mdc with beads-aware rules that Cursor re-includes every turn.

Verify:

bd setup cursor --check

See Cursor for details.

Gemini CLI

bd setup gemini            # Global hooks in ~/.gemini/settings.json
bd setup gemini --project  # Project hooks in .gemini/settings.json

This installs a SessionStart hook running bd prime --hook-json — Gemini requires hook stdout to be valid JSON, and --hook-json wraps the markdown in the required envelope — plus a minimal beads section in GEMINI.md. --stealth works the same as for Claude Code; --check and --remove cover both the hooks and the managed GEMINI.md section.

Verify:

bd setup gemini --check

See Gemini CLI for details.

Aider

# Setup Aider integration
bd setup aider

This writes three files:

Aider is human-in-the-loop: the AI suggests bd commands, and you run them with /run. See Aider for the workflow.

Verify:

bd setup aider --check

AGENTS.md Tools: Factory, Mux, OpenCode, Codex

bd setup factory    # Factory.ai Droid — AGENTS.md section
bd setup mux        # Mux — AGENTS.md section (+ --project/--global layers)
bd setup opencode   # OpenCode — AGENTS.md section
bd setup codex      # Codex — beads skill + AGENTS.md guidance + native hooks

These create or update a managed section in AGENTS.md (see Managed Sections above). bd init runs the project Codex setup automatically unless --skip-agents or --stealth is used. In worktree, shared, or BEADS_DIR setups, use bd where to confirm the resolved workspace — these integrations do not require a local ./.beads. Restart the tool after setup if it is already running.

Details: Factory.ai Droid, Mux, OpenCode, Codex.

GitHub Copilot

Copilot CLI:

bd setup copilot

This installs a native Copilot CLI plugin manifest (.copilot-plugin/plugin.json, which registers bd prime hooks) and repository instructions (.github/copilot-instructions.md). See Copilot CLI.

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:

{
  "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
• Persistent memories from bd remember

bd prime prints memories near the top and starts with a truncation warning. If your host stores the full hook output in a file and only shows a preview, have the agent read the full file before continuing.

In hook contexts, bd prime --hook-json wraps the output in the SessionStart JSON envelope (Claude Code, Gemini CLI, Codex). For memory-only hooks:

bd prime --memories-only

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.

Custom Recipes

For editors or tools without a built-in recipe:

bd setup --add myeditor .myeditor/rules.md   # Save a custom recipe
bd setup myeditor                            # Install it
bd setup myeditor --check                    # Check it
bd setup myeditor --remove                   # Remove it

Custom recipes are stored in .beads/recipes.toml (adding one requires an active beads workspace):

[recipes.myeditor]
name = "myeditor"
path = ".myeditor/rules.md"
type = "file"

For a one-off install without saving a recipe, write the template to any path — or inspect it first:

bd setup -o .my-custom-location/beads.md
bd setup --print

Recipe types:

Custom recipes added via --add are always type file.

Git Hooks

Ensure git hooks are installed for export refresh and legacy fallback behavior:

bd hooks install

This installs:

• pre-commit - Runs chained hooks before commit
• post-merge - Runs chained hooks after pull/merge
• pre-push - Runs chained hooks before push
• post-checkout - Runs chained hooks after branch checkout
• prepare-commit-msg - Adds agent identity trailers for forensics

Check hook status:

bd hooks list   # Installed, outdated, or missing
bd info         # Shows warnings if hooks are outdated

Verifying Your Setup

Run a complete health check:

# Check version
bd version

# Check project health (includes integration status)
bd doctor

# Check git hooks
bd hooks list

# Check editor integration
bd setup claude --check   # or cursor, gemini, aider, ...

Troubleshooting:

• Hooks not working? Restart your AI tool after installation, then re-run bd setup claude --check (or your tool's recipe) and check bd doctor output for integration status.
• Context not appearing? Make sure bd prime works standalone; if it fails, fix the underlying beads issue first.