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
I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
Description:
Add a slim sidebar on the right side of the TUI that lists only the user's own inputs (prompts) from the current conversation as clickable entries. Clicking an entry jumps directly to that message in the chat history.
Alternatively: a keyboard shortcut that opens a list of previous user messages within the current session, with an option to jump to any selected message.
How this differs from #31633:
Issue #31633 proposes a full conversation navigation bar with markers for every message (user, assistant, code blocks, errors). This request is narrower in scope: show only user messages, providing a lightweight "my prompts" index without the visual noise of marking every assistant response.
Use case: In long multi-turn sessions, scrolling back to find a specific earlier prompt is tedious. A compact list of just your own inputs gives a quick overview and instant navigation.
+1, this would be a huge quality-of-life win. I hit this all the time in long debug/refactor sessions — I need to jump back to a specific earlier prompt to recall the exact requirement or error, and PageUp-scrolling is slow and lossy.
I really like the narrower scope here (just my own messages) vs. the full conversation navigation bar in #31633. In practice that's the 90% case — when I want an assistant response, I usually remember which question it was answering, so an index of only my own prompts is both lighter and more discoverable.
Strong +1 on the narrow scope here, specifically listing only the user's own prompts and jumping to where each one occurred in the transcript.
Worth distinguishing this from #11963. That issue bundles viewing a past prompt with resending, rewinding, and forking, which pulls in session state mutation and undo semantics. This request is read only navigation: it just moves the viewport to where a prompt already is, with zero session mutation. Keeping the two separate means this can ship without waiting on the harder rewind design.
A minimal first cut could be keyboard only: jump to the previous or next user prompt relative to the current scroll position, with a brief highlight on landing. The sidebar/picker would be a natural follow up built on the same derived prompt index, which keeps each PR small and reviewable.
I would be happy to implement this. Since CONTRIBUTING requires design sign off on UI features, would the core team be open to this as a separate, read only feature distinct from #11963? And if so, any preference on (a) the default keybinding and (b) reusing the existing command palette for the picker versus a dedicated dialog?
I'd like to work on this. I'm planning to implement a compact "My Messages" section in the existing TUI right sidebar, showing only user prompts and reusing the existing message jump/navigation logic. I'll keep the initial PR scoped to prompt listing + jump navigation. Is this direction acceptable?
Activity
github-actions commentedon Jun 13, 2026
This issue might be a duplicate of existing issues. Please check:
If your request is genuinely distinct from the above, please clarify how it differs.
skywalker-35 commentedon Jul 1, 2026
+1, this would be a huge quality-of-life win. I hit this all the time in long debug/refactor sessions — I need to jump back to a specific earlier prompt to recall the exact requirement or error, and PageUp-scrolling is slow and lossy.
I really like the narrower scope here (just my own messages) vs. the full conversation navigation bar in #31633. In practice that's the 90% case — when I want an assistant response, I usually remember which question it was answering, so an index of only my own prompts is both lighter and more discoverable.
Happy to test or review a PR when one lands.
thatdudealso commentedon Jul 22, 2026
Strong +1 on the narrow scope here, specifically listing only the user's own prompts and jumping to where each one occurred in the transcript.
Worth distinguishing this from #11963. That issue bundles viewing a past prompt with resending, rewinding, and forking, which pulls in session state mutation and undo semantics. This request is read only navigation: it just moves the viewport to where a prompt already is, with zero session mutation. Keeping the two separate means this can ship without waiting on the harder rewind design.
A minimal first cut could be keyboard only: jump to the previous or next user prompt relative to the current scroll position, with a brief highlight on landing. The sidebar/picker would be a natural follow up built on the same derived prompt index, which keeps each PR small and reviewable.
I would be happy to implement this. Since CONTRIBUTING requires design sign off on UI features, would the core team be open to this as a separate, read only feature distinct from #11963? And if so, any preference on (a) the default keybinding and (b) reusing the existing command palette for the picker versus a dedicated dialog?
hadiMh commentedon Aug 13, 2026
I'd like to work on this. I'm planning to implement a compact "My Messages" section in the existing TUI right sidebar, showing only user prompts and reusing the existing message jump/navigation logic. I'll keep the initial PR scoped to prompt listing + jump navigation. Is this direction acceptable?
github-actions commentedon Oct 13, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.