Skip to content

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

Open

Description

@MikaelAlb

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

Activity

  1. added
    appIssues related to the Codex desktop app
    on Jul 29, 2026
  2. added
    bugSomething isn't working
    windows-osIssues related to Codex on Windows systems
    sessionIssues involving session (thread) management, resuming, forking, naming, archiving
    on Jul 29, 2026
  3. github-actions commented on Jul 29, 2026

    @github-actions
    Contributor
  4. MikaelAlb commented on Jul 29, 2026

    @MikaelAlb
    Author

    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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    appIssues related to the Codex desktop appbugSomething isn't workingperformancesessionIssues involving session (thread) management, resuming, forking, naming, archivingwindows-osIssues related to Codex on Windows systems

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions