The unsling command had two bugs: 1. It used the local beads directory instead of the target agent's rig 2. It looked for status=hooked beads instead of the agent bead's hook_bead field Changes: - unsling.go: Rewrote to use agent bead's hook_bead field (matches how sling works) - unsling.go: Now uses target agent's rig beads path, not local - status.go: Prefer SQLite columns (issue.HookBead, issue.AgentState) over parsing description text, with fallback for legacy beads - beads.go: Added AgentState field to Issue struct for SQLite column access This fixes the issue where `gt unsling gastown/crew/joe` would say "no work hooked" even when gt status showed joe had a hook. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
5.7 KiB
5.7 KiB