/init
Initialize beads in the current project
> /plugin marketplace add gastownhall/beads > /plugin install beads@beads-marketplace
How it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/init
Context preview
What this command does when you run it.
Initialize beads in the current project
Command definition
init.mddescription: Initialize beads in the current project argument-hint: "[prefix]"
Initialize beads issue tracking in the current directory.
If a prefix is provided as $1, use it as the issue prefix (e.g., "myproject" creates issues like myproject-1, myproject-2). If not provided, the default is the current directory name.
Use the beads MCP `init` tool with the prefix parameter (if provided) to set up a new beads database.
After initialization: 1. Show the database location 2. Show the issue prefix that will be used 3. Explain the basic workflow (or suggest running `/beads:workflow`) 4. Suggest creating the first issue with `/beads:create`
If beads is already initialized, inform the user and show project stats using the `stats` tool.
Distributed graph issue tracker for AI agents, powered by Dolt. Platforms: macOS, Linux, Windows, FreeBSD Docs: Beads provides a persistent, structured memory for coding agents.
Repo: gastownhall/beads
Other commands on beads.
- /plan-to-beads
Convert a Claude Code plan file into beads epic + tasks for cross-session tracking.
Open command - /audit
Log and label agent interactions (append-only JSONL)
Open command - /blocked
Show blocked issues
Open command - /close
Close a completed issue
Open command - /comments
View or manage comments on an issue
Open command - /compact
Compact old closed issues using semantic summarization
Open command