/update
Update an issue's status, priority, or other fields
> /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
/update
Context preview
What this command does when you run it.
Update an issue's status, priority, or other fields
Command definition
update.mddescription: Update an issue's status, priority, or other fields argument-hint: "[issue-id] [status]"
Update a beads issue.
If arguments are provided:
- $1: Issue ID
- $2: New status (open, in_progress, blocked, closed)
If arguments are missing, ask the user for: 1. Issue ID 2. What to update (status, priority, assignee, title, description) 3. New value
Use the beads MCP `update` tool to apply the changes. Show the updated issue to confirm the change.
**Note:** Comments are managed separately with `bd comments add`. The `update` command is for singular, versioned properties (title, status, priority, etc.), while comments form a discussion thread that's appended to, not updated.
Common workflows:
- Start work: `bd update <id> --claim` (atomic claim + `in_progress`)
- Mark blocked: Update status to `blocked`
- Reprioritize: Update priority (0-4)
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