bd help --doc init.
Initialize bd in the current directory by creating a .beads/ directory
and its storage (a Dolt database by default). Optionally specify a custom issue prefix.
Dolt is the default backend and the only one with version control (history,
branching, sync). Select an alternative with —backend=<postgres|mysql|sqlite>;
see docs/architecture/storage-backends.md for the trade-offs and setup.
Use —database to specify an existing server database name, overriding the
default prefix-based naming. This is useful when an external tool (e.g. an orchestrator)
has already created the database.
With —stealth: configures per-repository git settings for invisible beads usage:
• .git/info/exclude to prevent beads files from being committed
Perfect for personal use without affecting repo collaborators.
To set up a specific AI tool, run: bd setup <claude|cursor|aider|…> —stealth
By default, beads uses an embedded Dolt engine (no external server needed).
Pass —server to use an external dolt sql-server instead. In server mode,
set connection details with —server-host, —server-port, and —server-user.
Password should be set via BEADS_DOLT_PASSWORD environment variable.
Auto-export is optional. When enabled, bd exports issues to
.beads/issues.jsonl after write commands (throttled to once per 60s). This is
for viewers (bv), interchange, and issue-level migration; not backup.
Cross-machine sync and backups use Dolt remotes/backups, not JSONL import/export.
To enable: bd config set export.auto true
Non-interactive mode (—non-interactive or BD_NON_INTERACTIVE=1):
Skips all interactive prompts, using sensible defaults:
• Role defaults to “maintainer” (override with —role)
• Fork exclude auto-configured when fork detected
• Auto-export left at default (disabled)
• —contributor and —team flags are rejected (wizards require interaction)
Also auto-detected when stdin is not a terminal or CI=true is set.
CLI Reference
bd init
Initialize bd in the current directory
Generated from
Flags: