beads/website/versioned_docs/version-1.0.5/cli-reference/set-state.md
matt wilkie b55472412b
docs: snapshot versioned docs for 1.0.5 release (#4246)
The v1.0.5 tag shipped with cmd/bd/version.go bumped to 1.0.5 but without
the Docusaurus version snapshot, so check-version-consistency (via
scripts/check-docs-version.sh) went red on main: versions.json and
docusaurus.config.ts lastVersion were still 1.0.4 and
website/versioned_docs/version-1.0.5 was missing.

Create the 1.0.5 docs snapshot to restore consistency:
- docusaurus docs:version 1.0.5 (versions.json + versioned_docs + sidebar)
- set docusaurus.config.ts lastVersion to 1.0.5
- regenerate versioned CLI reference (stamps "Reference for bd v1.0.5")
- regenerate website/static/llms-full.txt

Verified: scripts/check-versions.sh and scripts/check-doc-flags.sh pass.

Refs: mybd-4qku

Agent-Signature: claude-opus-4-8-medium on behalf of matt wilkie
2026-05-28 21:51:26 -07:00

1 KiB

id title slug sidebar_position
set-state bd set-state /cli-reference/set-state 999

Generated from bd help --doc set-state

bd set-state

Atomically set operational state on an issue.

This command:

  1. Creates an event bead recording the state change (source of truth)
  2. Removes any existing label for the dimension
  3. Adds the new dimension:value label (fast lookup cache)

State labels follow the convention <dimension>:<value>, for example: patrol:active, patrol:muted mode:normal, mode:degraded health:healthy, health:failing

Examples: bd set-state agent-abc patrol=muted --reason "Investigating stuck worker" bd set-state agent-abc mode=degraded --reason "High error rate detected" bd set-state agent-abc health=healthy

The --reason flag provides context for the event bead (recommended).

bd set-state <issue-id> <dimension>=<value> [flags]

Flags:

      --reason string   Reason for the state change (recorded in event)