Feature: navigate/jump to previous user prompts in the current conversation (without terminal scrollback)
Status Open
Maintainer reply None cached
Activity 3 comments · opened May 30, 2026
Problem
In the default (classic) terminal view there's no quick way to jump back to a message I typed earlier in the current conversation. The only option is scrolling the terminal's native scrollback, which is slow and imprecise in long sessions.
Current state
Ctrl+Otranscript mode (with/search andn/Nto move between matches) helps, but only works in fullscreen rendering (/tui fullscreen).- In the default renderer there's no bindable action or message picker to jump between user prompts, and
~/.claude/keybindings.jsondoesn't expose a 'previous/next user message' action for the main conversation (themessageSelector:*actions are scoped to the rewind/summarize dialog).
Request
Add a way to navigate between the user's previous prompts in the current conversation without relying on terminal scrollback — for example a message picker (similar to the rewind/summarize selector) or bindable previousUserMessage / nextUserMessage actions — available in the default renderer, not only in fullscreen mode.
Environment
Claude Code in Ghostty on macOS.
3 Comments
+1 — same need. Requesting bindable
previousUserMessage/nextUserMessage(or Ctrl+Up/Ctrl+Down) in the default renderer and the VS Code extension, not only theCtrl+Ofullscreen transcript where{/}already jump between prompts.+1 — my exact workflow too. In long sessions I end up mouse-wheeling back through huge output blocks just to find where my last prompt was, so I can re-read Claude's answer from the top before replying.
Ctrl+Othen{/}(added in 2.1.139 — thanks!) covers this in transcript view, but the round-trip (switch view, jump, read, exit) is heavy for something I do dozens of times a day in the default renderer.A shape that would feel consistent with the existing bindings:
PgUp/PgDnalready scroll by page andCtrl+Endjumps to the bottom — soCtrl+PgUp/Ctrl+PgDnjumping to the previous/next user prompt would slot right in. Exposing it as bindable actions (e.g.scroll:previousUserMessage/scroll:nextUserMessage) inkeybindings.jsonwould let everyone put it wherever they like.+1 — and a correction to the earlier comments, since it may be making this look partly addressed.
On 2.1.220 there is no
{/}prompt-jump inCtrl+Otranscript view. TheTranscriptcontext binds only scroll actions (ctrl+u/ctrl+dhalf-page,ctrl+b/ctrl+ffull-page,g/shift+g,j/k,space/b,home/end,ctrl+etoggleShowAll,q/escexit), and the keybindings action enum contains no message- or turn-boundary navigation action anywhere — the closest arescroll:*(page/line/top/bottom) andmessageSelector:*, which is scoped to the rewind dialog and rewinds rather than scrolls.So there is currently nothing bindable in
~/.claude/keybindings.jsonfor this, in either renderer. The concrete ask stands: addscroll:previousUserMessage/scroll:nextUserMessageactions available in theScrollcontext, soCtrl+PgUp/Ctrl+PgDncan slot in next to the existingPgUp/PgDnandCtrl+Endbindings.Use case: after a long turn, jumping to my last prompt is the natural way to read everything new from the top.