TUI shortcut to jump between user prompts in the transcript
What feature would you like to see?
Add keyboard shortcuts in the Codex CLI TUI to jump between user prompt blocks in the current transcript, so users can quickly revisit the assistant output that followed a previous prompt.
For example:
- Jump to previous user prompt:
Alt+Upor another available shortcut - Jump to next user prompt:
Alt+Downor another available shortcut - Keep the selected prompt and the assistant output immediately below it visible
- Ideally support repeated jumps through the whole visible/current session transcript
Why is this useful?
In longer Codex CLI sessions, it is common to ask several prompts and later want to review the output underneath one of the recent prompts. Today, this usually requires manual terminal scrollback or text search. That works, but it is slow and imprecise when the transcript is long or when prompts have similar wording.
Prompt-to-prompt navigation would make it much easier to inspect earlier answers, compare outputs from recent prompts, and recover context without leaving the keyboard.
Related but different issues
This overlaps with existing navigation/history requests, but I think it is a distinct workflow:
- #2622 asks for interactive reverse search through prompt history, mainly to find and reuse previous prompts.
- #1064 asked for broader in-TUI scroll navigation such as PageUp/PageDown and Home/End.
- #14277 discusses scrollback preservation with
--no-alt-screenin xterm.js-based terminals.
This request is specifically about navigating between user prompt anchors inside the current Codex CLI transcript, with the goal of quickly reaching the assistant output under each prompt.
Suggested UX
One possible behavior:
- User presses the shortcut for previous prompt.
- The TUI scroll position moves to the previous user prompt block.
- The prompt is placed near the top of the viewport, leaving the following assistant output visible below it.
- Repeating the shortcut moves to older prompts; the opposite shortcut moves forward again.
Are you interested in implementing this feature?
No, but I would be happy to test and provide feedback.
This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗