You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(gt-4ly): use bd set-state for agent state + read from labels
Replace the removed `bd agent state` call with `bd set-state`, which
writes a dimension:value label (agent_state:<state>) and an event bead
for the audit trail. Labels are indexed and queryable across rigs
("bd list --label agent_state:working").
Update all read paths (GetAgentBead, getAgentBeadInfo) to scan for the
agent_state:* label instead of the dead DB column or description text.
Description text remains as a fallback for legacy beads.
Also fix the second call site in deacon.go (found in competing PR #3283
by EthanJStark — credit for that discovery).
Why bd set-state and not description-only:
- Labels are a generic beads concept (not Gas Town-specific)
- Indexed: bd list --label agent_state:working queries across rigs
- Survives session death; supports crash detection and dashboards
- Description text is unindexed free-form — a fidelity downgrade
The agent_state DB column was removed in beads v0.62.0 when the
agent-as-bead subsystem was extracted as Gas Town infrastructure
(commit 0bd598c, "this belongs in GT, not in beads").
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
0 commit comments