VS Code Codex approval prompts do not trigger chatUserActionRequired sound or OS notification
What version of the IDE extension are you using?
26.721.41059
What subscription do you have?
pro
Which IDE are you using?
Visual Studio Code 1.130.0
What platform is your computer?
macOS 26.5.2 (build 25F84), arm64
What issue are you seeing?
When the Codex extension asks for terminal approval, the Allow once / Deny confirmation UI appears correctly, but it does not trigger an accessibility signal or a macOS notification.
Configuration (User scope):
- accessibility.signals.chatUserActionRequired.sound = on
- accessibility.signals.chatUserActionRequired.announcement = off
- chat.notifyWindowOnConfirmation = always
What steps can reproduce the bug?
Steps to reproduce:
- Enable the settings above at User scope.
- Run Help: List Signal Sounds and verify that the signal preview is audible.
- Run Developer: Reload Window.
- Start a Codex action that requires terminal approval.
- Wait for the Allow once / Deny confirmation UI.
What is the expected behavior?
Expected behavior:
The approval prompt triggers the chatUserActionRequired sound and an OS notification.
Actual behavior:
The approval UI appears, but no sound is played and no macOS notification is shown. The signal preview itself is audible, so audio output is working.
Accessibility impact:
Users who are not continuously watching the Codex chat can miss pending approval requests, leaving tasks blocked without an audible or OS-level notification.
Additional information
The approval prompt may not be activating the relevant VS Code notification or accessibility-signal event. This is only a hypothesis; the underlying cause has not been established.
2 Comments
Duplicate of #30821 @etraut-openai
The approval prompt is exactly the moment you're not looking at the chat panel, which is what makes this one sting. If you want alerts working while it gets triaged, we maintain https://github.com/DevinoSolutions/ai-agent-notifier, which raises the OS toast itself off the agent's event stream instead of going through VS Code's accessibility-signal path. It'll also push to your phone over ntfy if you're away from the machine. Your repro is a useful hint for whoever picks this up too, signal preview audible but the prompt silent points at the extension never raising the signal rather than at audio routing.