CLI: Often cannot press up to recall session prompt history

Resolved 💬 6 comments Opened Dec 6, 2025 by aehlke Closed Mar 29, 2026

💡 Likely answer: A maintainer (etraut-openai, contributor) responded on this thread — see the highlighted reply below.

What version of Codex is running?

0.65.0

What subscription do you have?

Pro

Which model were you using?

_No response_

What platform is your computer?

_No response_

What issue are you seeing?

Often when I press up, I can get the last message I sent, but can't continue pressing up to get older ones. I haven't figured out what triggers this to happen yet.

What steps can reproduce the bug?

Press up multiple times. It only happens conditionally - I haven't figured out repro steps yet.

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

6 Comments

etraut-openai contributor · 8 months ago

Thanks for the bug report.

Could you share which platform are you on and which terminal emulator are you using?

aehlke · 8 months ago

Thanks for the bug report. Could you share which platform are you on and which terminal emulator are you using?

macOS Tahoe

iTerm2

muyuanjin contributor · 8 months ago

I often encounter messages starting with '/', for example, when manually sending a / test (note the space between the slash and "test"), I cannot continue to press up to recall session prompt history.

aehlke · 8 months ago

I often encounter messages starting with '/', for example, when manually sending a / test (note the space between the slash and "test"), I cannot continue to press up to recall session prompt history.

yes I found this reproduces it: if I have one where I pasted for instance a path that begins with / then I cannot press up to go past that message in the history

448523760 contributor · 8 months ago

I see this issue caused by tui enter the ActivePopup::Command after recall history that is start with "/".

handle_key_event_without_popup is where history navigation (Up / Down) is handled via history.should_handle_navigation(...)and history.navigate_up/down(...)
When the slash popup is active (ActivePopup::Command, handle_key_event_with_slash_popup is used instead, so [Up]is consumed by the popup and never reaches the history logic.

etraut-openai contributor · 5 months ago

This issue hasn't received any upvotes or additional posts in four months. I think it is fixed, so I'm going to close it. If you're seeing something similar, please create a new bug report with details.