Double-Esc triggers conversation rewind too easily and lacks a safety mechanism

Problem

Esc Esc immediately enters conversation backtracking/history editing.

This is easy to trigger accidentally, especially for developers who use Vim or Vim-style keybindings, where repeatedly pressing Esc is a common reflex to ensure Normal mode.

In multi-window or multi-monitor workflows, it's easy to misjudge which window has focus and accidentally trigger a conversation rewind.

Why this matters

Rewinding conversation state is a high-impact action, but it currently happens immediately with no confirmation and no obvious undo path.

An accidental Esc Esc can interrupt an active workflow and force users to reconstruct conversation context built over multiple interactions.

Suggested improvement

Claude Code uses a safer pattern: Esc Esc opens a history picker, and no state changes occur until the user explicitly selects a checkpoint.

Codex could consider:

• Opening a history picker before rewinding (preferred)
• Requiring confirmation before a state-changing rewind
• Allowing the shortcut to be remapped or disabled

This would make accidental activation much less likely while preserving the functionality.