Codex VS Code extension: notify when agent turn/task completes
What version of the IDE extension are you using?
new
What subscription do you have?
plus
Which IDE are you using?
vs code
What platform is your computer?
mac
What issue are you seeing?
Request
Please add native completion notifications to the Codex VS Code extension.
Problem
When a Codex agent is running inside VS Code, there is currently no visible notification when an agent turn or task completes. This makes it easy to miss finished work, especially when the user switches to another app or another VS Code window.
macOS notification permissions for VS Code and Codex can be enabled, but the VS Code extension does not appear to expose a setting or behavior for “notify when task completes.”
Expected behavior
Add a VS Code extension setting such as:
chatgpt.notifyOnTurnCompletechatgpt.notifyOnTaskComplete
When enabled, the extension should show a native VS Code / OS notification when:
- an agent turn completes
- an agent task completes
- an approval is needed
- optionally, when a task fails or is interrupted
Why this matters
Codex tasks can run for a long time. Users often switch context while waiting. A completion notification would make the VS Code workflow much more practical without requiring users to use Codex App, CLI, or custom global notify hooks.
Current workaround
Codex CLI has a global notify hook, but that is not a good substitute for VS Code extension-native behavior because:
- it is global, not VS Code-specific
- it requires custom scripts
- it does not integrate cleanly with VS Code notification preferences
- it is not discoverable from the extension settings UI
Suggested implementation
Use VS Code’s notification API from the extension when the extension receives the agent turn/task completion event.
A setting could control behavior:
{
"chatgpt.notifyOnTaskComplete": true,
"chatgpt.notifyOnApprovalRequired": true
}
Optionally support:
notify only when VS Code is unfocused
notify always
notify only for long-running tasks
### What steps can reproduce the bug?
new
### What is the expected behavior?
_No response_
### Additional information
_No response_This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗