/reopen
Reopen closed issues
> /plugin marketplace add steveyegge/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
/reopen
Context preview
What this command does when you run it.
Reopen closed issues
Command definition
reopen.mddescription: Reopen closed issues argument-hint: "[issue-ids...] [--reason]"
Reopen one or more closed issues.
Sets status to 'open' and clears the closed_at timestamp. Emits a Reopened event.
Usage
- **Reopen single**: `bd reopen bd-42`
- **Reopen multiple**: `bd reopen bd-42 bd-43 bd-44`
- **With reason**: `bd reopen bd-42 --reason "Found regression"`
More explicit than `bd update --status open` - specifically designed for reopening workflow.
Common reasons for reopening:
- Regression found
- Requirements changed
- Incomplete implementation
- New information discovered
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: steveyegge/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