Repository navigation
[FEATURE]: Auto-scroll to top of new assistant response instead of bottom #40870
Closed as not planned
Description
Feature hasn't been suggested before.
- I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
Feature request
When the assistant finishes streaming a response that's longer than the viewport, the scroll position stays at the bottom of that response, forcing me to scroll up manually to read it from the top.
Please add either:
- A preference toggle in
Desktop → General(or similar) to auto-scroll to the top of the newest response when it finishes rendering, OR - A dedicated "Jump to Answer Start" button/shortcut as previously requested in [FEATURE]: Add 'Jump to Answer Start' Button #9794.
Related and prior work
- [FEATURE]: Add 'Jump to Answer Start' Button #9794 — [FEATURE]: Add 'Jump to Answer Start' Button. Closed as COMPLETED but based on the last automated comment, it appears to have been auto-closed after 90 days of inactivity rather than actually implemented. The feature is not present in the desktop app v1.18.14.
- Feature Request: Navigation Shortcut to Jump Between User Messages #3337 — Navigation Shortcut to Jump Between User Messages. Also closed similarly. Related but different (jumps between user messages, not to top of assistant response).
- [FEATURE]: Scroll down ui button when !bottom #5783 — Scroll down UI button when !bottom. Already implemented (
Jump to Latestbutton exists at the bottom of long conversations). This request is the mirror-image: a way to jump to the top of the newest response. - [FEATURE]: Add ability to (un)mark points in the thread, to use as "bookmarks" #9227 — Bookmarks in thread. Alternative approach, not equivalent.
None of the above solve the specific problem: I want reading a new response to start from the top of that response, ideally automatically.
Desired behavior
Preferred approach (automatic):
- New toggle: "Scroll to top of new response" (default off, to preserve current behavior).
- When enabled: after the assistant finishes streaming, viewport scrolls so the first line of the newest response is at the top.
Acceptable fallback (manual):
- Reintroduce the "Jump to Answer Start" button from [FEATURE]: Add 'Jump to Answer Start' Button #9794 at the top of each assistant response, OR
- Add a keyboard shortcut like
Cmd+HomeorAlt+↑to jump to the beginning of the latest assistant message.
Why this matters
- Reading top-to-bottom is the natural flow; landing at the bottom of a long response is disorienting.
- On mixed content (explanation + code + tables), the manual scroll adds friction on every turn.
- Users who prefer the current auto-scroll-to-bottom behavior can leave the toggle off.
Environment
- OpenCode Desktop 1.18.14
- macOS 26.5.2
- Verified no scroll-related option exists under Settings → Desktop → General.
- Verified no "jump to previous message" shortcut exists under Settings → Desktop → Shortcuts.
Reacted by llavaa99, YU Wenyan and remotxavier
Activity
llavaa99 commentedon Aug 22, 2026
Also affected by this in the TUI (terminal), not just the desktop app.
After a long response finishes streaming, only the tail of the message is visible. There is no auto-scroll to the beginning of the response, so I have to press PageUp repeatedly to read it from the top.
A
tui.jsonoption (e.g.scroll_to_response_start: true) or a default-bound keybind like "jump to start of latest response" would solve this. Related unbound keybinds that could help:messages_previous/messages_last_user.remotxavier commentedon Sep 18, 2026
Still reproducible on OpenCode Desktop 1.18.31, macOS 27.0. Verified with a long response in the desktop app: cursor lands at the end of the message, requiring manual scroll to the top to read the response from the beginning. Also confirmed on TUI per @llavaa99's earlier comment. Any consideration of a
scroll_to_response_starttoggle in the roadmap?planesandunicorns commentedon Oct 8, 2026
Confirming on OpenCode v2.0.24 (TUI), macOS 27 / arm64, zsh, xterm-256color.
With a response longer than the viewport the transcript lands at the bottom of the new message, so I have to scroll up to read it from the start. A
cli.json/sessionoption (e.g.session.scroll_to_response_start: true) or a default-bound "jump to start of latest response" keybind would solve it — the V2 CLI schema'sscrollgroup only exposesspeed/acceleration, andsessionhas no follow/scroll option.Workaround tried:
session.verbosity: lowreduces the volume but does not change where the view lands.Y15BeTa commentedon Oct 11, 2026
Confirming on macOS 26.6 (arm64) + OpenCode Desktop 2.0.26 — same behaviour here.
One detail that may be useful for the fix:
message.previous/message.nextare scoped to user messages ("Go to the previous user message"), so from the bottom they land on the second-to-last item and cannot reach the start of the last message. So this needs either a new command or a change to the opening scroll position, not just a rebind.I opened #54572 for the "open at the start of the last message" case before finding this issue — happy to have it closed as a duplicate if this one covers it.
opencodejr commentedon Oct 28, 2026
Thanks for the detailed write-up! You're asking for a way to land at the top of a new assistant response once it finishes streaming, either as a toggle or as a "Jump to Answer Start" button or shortcut.
You're on OpenCode Desktop 1.18.14, which is OpenCode v1. v1 is a separate codebase that now only gets fixes for critical bugs (data loss, security problems, crashes with no workaround), so feature requests for it are unlikely to be implemented.
New work happens in OpenCode v2 (2.x, npm package
@opencode/cli), so we'd encourage you to upgrade. If v2 still lacks a good way to jump to the start of the latest response, please reply here or open a new request against v2 with your version.Related issues you mentioned:
If you believe this is critical, or you see the same problem on v2, please reply and let us know.
opencodejr commentedon Oct 29, 2026
We haven't heard back, so I'm closing this as not planned. It's a feature request for OpenCode Desktop 1.18.14 (v1), and v1 only gets fixes for critical bugs.
If OpenCode v2 still doesn't give you a way to jump to the start of the latest assistant response, please open a new request against v2 and include your version. You can also link #9794 there. Thanks again for the detailed suggestion!