Skip to main content
How to use beads with Aider. Aider is a human-in-the-loop AI pair programming tool: unlike autonomous agents such as Claude Code, it doesn’t run shell commands on its own. The beads integration works with that design — the AI suggests bd commands, and you confirm each one with aider’s /run command.

Setup

Prerequisites

  • beads installed and initialized in your project (see Installation); run bd init if there’s no .beads/ directory yet
  • aider installed: pip install aider-chat (or pipx install aider-chat)

Quick Setup

This creates:
  • .aider.conf.yml — tells aider to load the beads instructions
  • .aider/BEADS.md — workflow instructions the AI reads
  • .aider/README.md — quick reference for humans

Verify Setup

Remove the Integration

This removes .aider.conf.yml, .aider/BEADS.md, and .aider/README.md.

Configuration

The generated .aider.conf.yml loads the beads instructions into aider’s read-only context:
.aider/BEADS.md holds the workflow rules the AI follows: track all work in bd (never markdown TODOs), suggest bd ready to find work, suggest bd create for new issues, suggest bd dolt push at end of session — and always suggest commands for you to run via /run. You can edit it to add project-specific instructions, but rerunning bd setup aider regenerates it.

Workflow

Start Session

Inside Aider

Aider’s own commands start with / (/run, /add, /help); anything else is a message to the AI. The AI suggests bd commands, and you execute the ones you approve with /run:
To give the AI full bd context mid-session, run /run bd prime — the AI reads the output and picks up the complete workflow guide.

During Work

Use bd commands alongside aider:

End Session

Best Practices

  1. Keep issues visible - Use bd prime to inject issue context
  2. Push regularly - Run bd dolt push after significant changes
  3. Use discovered-from - Track issues found during work
  4. Document context - Include descriptions in issues
  5. Aider commits, bd syncs - Aider auto-commits your code changes; issue data moves separately with bd dolt push

Example Workflow

Troubleshooting

Config not loading

Aider reads .aider.conf.yml at startup, so restart aider (/exit, then aider) after regenerating.

Issues not visible

See Also