edit previous message bug after using /status command in 0.44

Resolved 💬 2 comments Opened Oct 4, 2025 by thorizer Closed Nov 6, 2025
💡 Likely answer: A maintainer (miraclebakelaser, contributor) responded on this thread — see the highlighted reply below.

What version of Codex is running?

0.44

Which model were you using?

gpt5-high

What platform is your computer?

linux ubuntu 24

What steps can reproduce the bug?

after i use /status, i can't edit previous message that came before that anymore, but i can edit the previous message that came after. context is not showing anymore

What is the expected behavior?

it should go back to the previous message

What do you see instead?

pessing escape many times does not do anything

Additional information

_No response_

View original on GitHub ↗

2 Comments

miraclebakelaser contributor · 10 months ago
miraclebakelaser contributor · 9 months ago

fwiw you can work around this bug by exiting codex and resuming the codex session (codex resume <session-id>). The status dialog does not appear in the resumed conversation, allowing for full conversation backtracking.