Fix TUI duplicate bead display and planning keybind#264
Merged
newhook merged 1 commit intonewhook:mainfrom Feb 3, 2026
Merged
Conversation
- Fix root issue appearing twice in work details (as root and unassigned) - Add friendly error when worktree is still being created - Make 'p' key context-aware: plan for unassigned beads, PR otherwise
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes three TUI issues reported by a user:
[p] planfor unassigned beads but 'p' was mapped to create PRChanges
internal/progress/fetch.go: Skip root issue when populating UnassignedBeadsinternal/tui/tui_plan_work.go: Add friendly error when worktree still being createdinternal/tui/tui_panel_work_details.go: Add WorkDetailActionPlan and context-aware 'p' handlinginternal/tui/tui_panel_work_overview.go: Add methods to detect unassigned bead selectioninternal/tui/tui_plan.go: Handle WorkDetailActionPlan to spawn planning sessionTest plan
Create work from single bead, verify no duplicate in work details panel
Press 'r' immediately after work creation, verify friendly error message
Add unassigned bead to work, select it, press 'p', verify planning session starts
Notes
The 'p' key behavior may need further review - currently it is context-sensitive (plan for unassigned beads, PR otherwise). The status bar shows
[p]rfor work-level actions but the unassigned bead panel shows[p] plan. A future PR may want to unify this or use different keys.Screenshots
Before
After