VS Code extension (Cursor host): no reliable completion ding / notify config appears ignored
Resolved 💬 11 comments Opened Feb 27, 2026 by flutterrausch Closed Feb 27, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
Summary
In the OpenAI Codex VS Code extension (openai.chatgpt, tested in Cursor host), completion notifications are not configurable in a way that yields one ding per finished request.
The same ~/.codex/config.toml notification settings used by CLI/TUI appear ignored in extension app-server sessions.
Environment
- Date observed: 2026-02-27
- Extension:
openai.chatgpt-0.5.78-universal - Cursor:
2.5.26(VS Code-compatible host) - codex binary used by extension: bundled app-server binary
- macOS:
26.3(Darwin25.3.0)
Config used
notify = ["zsh", "/Users/ingo/Developer/dotfiles/ai/notify_log_codex.zsh"]
[tui]
notification_method = "bel"
notifications = ["agent-turn-complete"]
Repro
- Configure
notifyhook to write payloads to~/.codex/notify-debug.log. - Confirm script works manually.
- Start extension session and run turns.
- Check
~/.codex/notify-debug.log.
Expected
- A supported completion notification path for extension sessions (ideally event-filterable to turn completion only).
Actual
- No notify hook invocations for extension turns.
- No completion ding.
- Extension logs show app-server activity, but no evidence that config-based notify is wired for this surface.
Additional observed logs
- Frequent:
Received broadcast but no handler is configured method=thread-stream-state-changed- Also saw state DB warnings in extension logs:
failed to open state db ... migration 18 was previously applied but is missing in the resolved migrations
Request
- Document notification support matrix for extension sessions vs CLI/TUI.
- Add explicit extension-level setting for completion sound (single ding per completed request).
- If CLI
notify/[tui]settings are intentionally not used by extension, surface that clearly in logs/docs.
11 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Both by me, close which you want.
The
tui.notificationsis specific to the TUI, so it doesn't apply to the extension or app.The
notifyhook does work with the extension.First sentence - with subagents, I get like a dozen dings from "notify", which is not helpful.
Please add another hook that works in both, or sth. TUI is not an option anymore since app and ext got really good (I can actually edit my prompt now : ).
We are actively working on a more general event hooks mechanism. The
notifyhook will be deprecated as soon as we have that in place.See https://github.com/openai/codex/issues/2109 and https://github.com/openai/codex/issues/3962.
I just tried Cursor and Codex app, and both their notifications don't work. Sorry that I've missed that before.
Hooks seem to be the only stable thing for both actual Cursor, and and Codex (tried months ago on TUI).
Looking forward and thanks for your answers ❤️
Have you tried configuring notifications in the app rather than trying to use a low-level hook?
<img width="738" height="190" alt="Image" src="https://github.com/user-attachments/assets/49f947a2-54ac-4710-b887-024ebcab3dc1" />
One of the (many) reasons we created the app is because notifications are difficult to do right in the TUI and IDE Extension given the limitations of terminals and VS Code.
Yes, this setting (and notifications/audio), does not work. I guess Tahoe is broken.
@flutterrausch, are you sure that you have enabled notifications for the Codex app in your Mac System Settings? Your settings should look like this.
<img width="495" height="505" alt="Image" src="https://github.com/user-attachments/assets/561905e2-a6cd-42de-9a68-c24010f0c193" />
Yep, had sound only, tried alerts and stuff too, nothing. MacOS broken it seems.
Can be closed, hooks are working, thanks.