CLI's transcript mode should allow for vim commands (/, ?, gg, G, u, d, etc) like `less`

Resolved 💬 4 comments Opened Jan 25, 2026 by vpuri3 Closed May 10, 2026
💡 Likely answer: A maintainer (etraut-openai, contributor) responded on this thread — see the highlighted reply below.

What feature would you like to see?

see title

Additional information

_No response_

View original on GitHub ↗

4 Comments

etraut-openai contributor · 7 months ago

Can you provide more details about your feature request? In its current form, it's unlikely to receive many upvotes, and it will eventually be closed. We generally prioritize feature requests based on community feedback (upvotes), so make sure your feature request description and title are compelling.

swordfish444 contributor · 7 months ago

@etraut-openai Adding some concrete detail / scope to help this get traction:

  • Desired UX: in --transcript / transcript viewer, support the common less/vim nav+search keys: j/k, d/u (half-page), g/G (top/bottom), / + n/N (search), maybe q to exit.
  • - Minimal/low-risk implementation: let users pipe transcript output to a pager ($PAGER, fallback less -R) so they immediately get these keys without reimplementing a pager. e.g. codex … --transcript | ${PAGER:-"less -R"}
  • - - Related older asks that look like the same UX request: #2958 and #3935 (both were closed largely due to low engagement).

Happy to help refine acceptance criteria if you want to keep this open vs closing as underspecified.

oxysoft · 5 months ago

Cross-linking #14386 because it extends the same mental model into the live reply surface.

This issue asks for transcript-mode navigation/search to feel more like less/vim. #14386 asks for a modal keyboard surface over structured assistant replies themselves, with semantic unit navigation and actions like quote/append/send.

Together they reinforce the broader TUI expectation: generated content should be navigable and operable with real keyboard mechanics, not just passively displayed.

etraut-openai contributor · 3 months ago

This feature request hasn't received enough upvotes, so I'm going to close it.