Skip to content

Comments

feat(mol): add hint to view step instructions in mol current output#1403

Merged
steveyegge merged 1 commit intosteveyegge:mainfrom
aleiby:fix/bd-p00k0-mol-current-step-hint
Jan 31, 2026
Merged

feat(mol): add hint to view step instructions in mol current output#1403
steveyegge merged 1 commit intosteveyegge:mainfrom
aleiby:fix/bd-p00k0-mol-current-step-hint

Conversation

@aleiby
Copy link
Contributor

@aleiby aleiby commented Jan 30, 2026

Summary

When bd mol current displays the step list with "YOU ARE HERE" marker, agents often improvise based on the step title alone without reading the detailed step instructions stored in the step bead's description.

This adds a footer hint after the progress line:

Progress: 1/22 steps complete

💡 Run `bd show feed-stranded-convoys` to see detailed instructions.

The hint shows the current step ID if one is in_progress, otherwise the next ready step ID.

Problem

Step descriptions are stored in formula files and copied to step beads when molecules are poured. bd show <step-id> displays these descriptions. However, agents don't know to run this command because nothing tells them about it.

Evidence: The Deacon patrol saw step title "Feed stranded convoys" and improvised with bd list | grep instead of using gt convoy stranded --json as specified in the step description.

See: steveyegge/gastown#1128

Test plan

  • go build ./cmd/bd - compiles
  • go test ./cmd/bd/... -run "Mol" - all tests pass
  • Manual: run bd mol current on an active molecule and verify hint appears

🤖 Tackled with Claude Code

When bd mol current displays the step list with "YOU ARE HERE" marker,
agents often improvise based on the step title alone without reading
the detailed step instructions stored in the step bead's description.

This adds a footer hint:
  💡 Run `bd show <step-id>` to see detailed instructions.

The hint shows the current step ID if one is in_progress, otherwise
the next ready step ID. This makes it clear how to access the full
step description which contains the actual commands and procedures.

Addresses: steveyegge/gastown#1128
@aleiby aleiby force-pushed the fix/bd-p00k0-mol-current-step-hint branch from 7e407dd to ecfc43c Compare January 31, 2026 01:08
@aleiby aleiby marked this pull request as ready for review January 31, 2026 01:18
Copy link
Owner

@steveyegge steveyegge left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Easy-win: clean UX improvement adding hint to view step instructions. Small, additive, no risk. LGTM.

@steveyegge steveyegge merged commit 82a2354 into steveyegge:main Jan 31, 2026
3 of 7 checks passed
@aleiby aleiby deleted the fix/bd-p00k0-mol-current-step-hint branch January 31, 2026 06:30
groblegark pushed a commit to groblegark/beads that referenced this pull request Jan 31, 2026
…teveyegge#1403)

When bd mol current displays the step list with "YOU ARE HERE" marker,
agents often improvise based on the step title alone without reading
the detailed step instructions stored in the step bead's description.

This adds a footer hint:
  💡 Run `bd show <step-id>` to see detailed instructions.

The hint shows the current step ID if one is in_progress, otherwise
the next ready step ID. This makes it clear how to access the full
step description which contains the actual commands and procedures.

Addresses: steveyegge/gastown#1128
(cherry picked from commit 82a2354)
groblegark pushed a commit to groblegark/beads that referenced this pull request Jan 31, 2026
…teveyegge#1403)

When bd mol current displays the step list with "YOU ARE HERE" marker,
agents often improvise based on the step title alone without reading
the detailed step instructions stored in the step bead's description.

This adds a footer hint:
  💡 Run `bd show <step-id>` to see detailed instructions.

The hint shows the current step ID if one is in_progress, otherwise
the next ready step ID. This makes it clear how to access the full
step description which contains the actual commands and procedures.

Addresses: steveyegge/gastown#1128
(cherry picked from commit 82a2354)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants