ESC from "Toggle voice chat" creates dead history entries.

Open 💬 2 comments Opened Jul 29, 2026 by MikaelAlb
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of the Codex App are you using (From “About Codex” dialog)?

26.721.41059

What subscription do you have?

Plus

What platform is your computer?

Win11

What issue are you seeing?

In ChatGPT desktop with Codex selected, I pressed the default
Ctrl+Shift+V shortcut for “Toggle Voice Chat”.

I did not grant microphone permission and cancelled the Voice flow with
Esc. This left a history entry titled “New chat” that cannot be opened
or archived. Repeating the sequence created a second broken entry.

Opening either entry shows a blank screen with the ChatGPT logo
repeatedly flashing, accompanied by CPU spikes and fluctuating memory
usage.

Also reported in-app: 019fac97-5435-7a50-90f6-d08ca42a7e81

What steps can reproduce the bug?

Feedback ID: 019fac97-5435-7a50-90f6-d08ca42a7e81

What is the expected behavior?

Expected result

Cancelling Voice Chat before granting microphone permission should:

  • close the Voice interface cleanly;
  • discard any provisional empty chat, or leave it in a valid state;
  • not create an unopenable or unarchivable history entry;
  • not cause a repeated loading/rendering loop.

Additional information

I regularly use Ctrl+Shift+V to paste without formatting and this default keymap breaks that convention.
I suggest reconsidering the default keymap to something less bound by other conventions and allow the use of the default shortcut for "paste without formatting" to also work in ChatGPT, which is (at least for me) a very useful and often used function

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 1 month ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #35252
  • #35418

Powered by Codex Action

MikaelAlb · 1 month ago

First suggestion might be related to the specific behavior of the "dead history entries", but not the same core issue persay.
Second is mentioned as a sidenote in this report, but not the core issue