Repository navigation
Feature request: message navigation gutter in the TUI (jump to user prompts like DeepSeek web) #42523
Closed as not planned
Description
Motivation
In long sessions, finding a specific earlier user prompt requires scrolling through the whole conversation. DeepSeek's web UI has a persistent right-side gutter with marks for each user message; hovering shows the first words of the prompt and clicking jumps to it. This makes navigating a long session much easier.
Request
Add an equivalent to the OpenCode TUI (and web UI): a thin gutter/rail beside the chat showing a marker per user message. On hover, show a tooltip with the start of the prompt; on click/select, scroll the conversation to that message.
Why it helps
- Faster orientation in long sessions (dev sessions can have hundreds of turns)
- Consistent mental model: "each marker = one prompt I wrote"
- Complements the existing
/, session list, and command palette navigation
Acceptance criteria (suggested)
- One marker per user message, always visible while the session has user messages
- Hover reveals a tooltip preview of the prompt's first words
- Selecting a marker scrolls the chat to that message
- Works in both TUI and web UI
Notes
- Environment: Windows, standalone
opencode-cli.exe(v1.3.13, Bun-bundled). The TUI is built on@opentui; the web UI on Svelte/WebView2. - Open to any simpler alternative you'd recommend (e.g., a
/jumpcommand with fuzzy search over user prompts).
Metadata
Metadata
Assignees
Labels
No labels
Activity
github-actions commentedon Aug 14, 2026
This issue doesn't fully meet our contributing guidelines.
What needs to be fixed:
[FEATURE]:and include the required verification checkbox confirming you've searched for duplicatesPlease 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:
If you believe this was flagged incorrectly, please let a maintainer know.
github-actions commentedon Aug 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.