›_ Codex Issues
Codex Issues / #13590

Dictation stops (and appears to cancel) when command approval prompt appears during a session

Resolved 💬 2 comments Opened Mar 5, 2026 by CasperKristiansson Closed Jun 22, 2026

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

26.303.1606

What subscription do you have?

Pro

What platform is your computer?

Darwin 25.3.0 arm64 arm

What issue are you seeing?

When using voice dictation in the Codex app, if a “command approval” prompt appears (e.g., approve running a command), dictation immediately stops. It seems to quit/cancel the dictation session rather than pausing it or finishing it.

This is especially disruptive if I’ve been dictating for a while: I have to restart dictation. This has been giving me a headache when I have been dictating for multiple minutes and essentially lose the progress.

What steps can reproduce the bug?

  1. Run a prompt that will trigger an approval prompt
  2. While it is running, start dictating
  3. When it shows that I need to approve, the input box disappears, and the dictation has stopped

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

2 Comments

codefactory-hub · 4 months ago

I’m seeing a closely related form of this with agent UI updates, not only command approval prompts.

Environment:

  • Codex app: 26.422.30944
  • Platform: macOS 26.4.1 build 25E253
  • Timezone: America/Denver

Scenario:

  1. An agent is already running.
  2. I start dictating a steering/interruption message into the composer.
  3. While dictation or transcription is in progress, the agent comes back with a question or another UI state change.
  4. The composer/dictation UI is interrupted, and the dictated content is lost.

This feels like the same underlying class of bug as approval prompts: Codex UI changes can unmount or replace the active composer while dictation is in progress, and the recording/transcription state is not durable enough to survive that.

This also looks related to:

  • #13982, where dictation is lost after leaving the chat before transcription finishes.
  • #18344, where recording/sending voice and then switching threads loses the message.
  • #18223, where long voice input can be silently lost with no recoverable draft/audio.
  • #16819, where dictated content is deleted/lost.

Expected behavior:

  • An agent question, approval prompt, or other mid-run UI update should not discard active voice input.
  • If dictation cannot remain attached to the visible composer, Codex should persist the audio/transcription job and expose a recoverable draft.
  • At minimum, Codex should warn before canceling and discarding unsent dictated content.
vmeylan · 2 months ago

Additional current reproduction, June 11, 2026:

During a long-running Codex Desktop session on macOS, the agent requested command approval while I was recording a voice message. The approval UI appeared over the active composition flow. When I clicked the approval, the in-progress voice message/dictation was cancelled/interrupted, so the dictated content was lost and I had to start again.

The practical impact is that voice input is unsafe while the agent is working in on-request / approval-gated mode: the user can be mid-sentence, a sandbox/command approval appears, and responding to the approval destroys the active voice capture.

Expected behavior remains that approval prompts should be non-destructive to active dictation. At minimum, Codex should preserve the audio/transcript draft, pause and resume recording, or queue the approval until active voice capture is stopped.