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
{{ message }}
Repository navigation
feat(tui): add thread commands and session graph #32298
Users need a way to explore specific parts of a conversation in isolation without losing context. Currently there is no way to fork a discussion thread from selected text or visualize the relationship between related sessions.
Proposed Solution
Add two new slash commands:
/thread - Creates a child thread from selected text
Captures selected text and parent conversation context
Shows ThreadFooter with navigation (parent/prev/next) and selected text excerpt
Injects parent context as synthetic system reminder on first prompt
/graph - Shows session hierarchy tree
Displays threads and subagents in a tree view
Shows selected text excerpts for each thread
Click-to-navigate to any session
Verification
Typecheck passes: bun typecheck in packages/tui
Unit tests pass: bun test test/util/session.test.ts
The title uses conventional commit format (feat(tui):) instead of the required Feature Request title format, which should start with [FEATURE]:
The issue is missing the Feature Request template structure, specifically the verification checkbox confirming the feature hasn't been suggested before
Please edit this issue to address the above within 2 hours, or it will be automatically closed.
This issue might be a duplicate of existing issues. Please check:
Activity
github-actions commentedon Jun 14, 2026
This issue doesn't fully meet our contributing guidelines.
What needs to be fixed:
feat(tui):) instead of the required Feature Request title format, which should start with[FEATURE]:Please edit this issue to address the above within 2 hours, or it will be automatically closed.
This issue might be a duplicate of existing issues. Please check:
/treecommand for visual session navigation with click-to-navigate between branches — closely overlaps with the proposed/graphcommandIf you believe this was flagged incorrectly, please let a maintainer know.
github-actions commentedon Jun 14, 2026
This issue has been automatically closed because it was not updated to meet our contributing guidelines within the 2-hour window.
Feel free to open a new issue that follows our issue templates.