codex - 💡(How to fix) Fix When pressing ESC back back enter you can't get back to the last turn [2 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#18830Fetched 2026-04-22 07:51:56
View on GitHub
Comments
2
Participants
3
Timeline
8
Reactions
0
Author
Timeline (top)
labeled ×4commented ×2unlabeled ×2
RAW_BUFFERClick to expand / collapse

What issue are you seeing?

It's too easy to lose a 15+ minute run context and turn by accident and there is no way to redo it deterministically

What steps can reproduce the bug?

After a few turns, press ESC left arrow left arrow enter. Then try to go back to the turn you were on before you did this. Not possible.

What is the expected behavior?

You should be able to revert back to where you were. The visual cue says "Enter to edit message" but it doesn't say "Enter to trash all subsequent messages from transcript and logs" which is what it actually does.

Additional information

No response

extent analysis

TL;DR

Implementing an undo feature or warning users before discarding subsequent messages could resolve the issue of lost run context.

Guidance

  • Identify the specific code handling the "Enter" key press and the ESC key combination to understand how the current state is being discarded.
  • Consider adding a confirmation prompt before discarding subsequent messages to prevent accidental loss of run context.
  • Review the visual cues and messaging to ensure they accurately reflect the consequences of the user's actions, such as adding a warning about discarding messages.
  • Explore implementing an undo feature to allow users to revert back to a previous state if they accidentally discard their run context.

Notes

The exact implementation details are uncertain without more information about the codebase and technology stack being used.

Recommendation

Apply workaround: Implement a confirmation prompt before discarding subsequent messages to prevent accidental loss of run context, as this seems to be a straightforward way to mitigate the issue without requiring significant changes to the existing functionality.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING