What version of the Codex App are you using (From "About Codex" dialog)?
No response
What subscription do you have?
No response
What platform is your computer?
No response
What issue are you seeing?
Sometimes the message edit icon is not visible, and there is no reliable way to rewind, rollback, or restore to a checkpoint from the UI.
In other tools such as Cursor and Claude Code, editing/rewinding/checkpoint restore is reliable enough to recover from a bad turn. In Codex, when the edit affordance is missing or hard to find, there is no obvious fallback path to return to a previous state.
Feedback ID: b625d0e2-54ae-4fef-8281-d3ce87ef54c0
Additional feedback: /feedback currently does not allow attaching screenshots, which makes this kind of UI bug harder to report with evidence.
Possibly related existing issues:
What steps can reproduce the bug?
No response
What is the expected behavior?
- The edit icon should be consistently visible/discoverable when message editing is available.
- Codex should provide a reliable rewind/rollback/checkpoint restore flow.
- Users should have a clear way to recover from an undesirable turn, similar to the reliable checkpoint flows in Cursor or Claude Code.
/feedback should allow attaching screenshots for UI reports.
Additional information
No response
What version of the Codex App are you using (From "About Codex" dialog)?
No response
What subscription do you have?
No response
What platform is your computer?
No response
What issue are you seeing?
Sometimes the message
editicon is not visible, and there is no reliable way to rewind, rollback, or restore to a checkpoint from the UI.In other tools such as Cursor and Claude Code, editing/rewinding/checkpoint restore is reliable enough to recover from a bad turn. In Codex, when the edit affordance is missing or hard to find, there is no obvious fallback path to return to a previous state.
Feedback ID:
b625d0e2-54ae-4fef-8281-d3ce87ef54c0Additional feedback:
/feedbackcurrently does not allow attaching screenshots, which makes this kind of UI bug harder to report with evidence.Possibly related existing issues:
What steps can reproduce the bug?
No response
What is the expected behavior?
/feedbackshould allow attaching screenshots for UI reports.Additional information
No response