Skip to content
| Marketplace
Sign in
Visual Studio Code>Other>Codex notificationNew to Visual Studio Code? Get it now.
Codex notification

Codex notification

nouri

|
10 installs
| (0) | Free
Workspace-scoped Codex task and question alerts, plus Claude Code response and input notifications.
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

Codex notification

Desktop and editor alerts for Codex in Antigravity / VS Code, scoped to the current workspace.

Install and configure

  1. Install version 0.2.1 using Extensions → Install from VSIX, or update from your registry. Reload the editor.
  2. If setup is missing, accept the startup setup prompt or click Codex alerts: setup needed in the status bar. You can also run Codex notification: Enable Task Signals in This Workspace. This appends a short, idempotent status-reporting section to AGENTS.md, preserving existing instructions. Start a new Codex chat so it loads the instructions.
  3. Run Codex notification: Choose Notification Mode: questions only, completed tasks only, or both.
  4. Run Codex notification: Test Completion Notification and Codex notification: Test Question Notification to test each delivery path. Tests check alert delivery, not automatic event detection. For native macOS alerts, enable notifications and sound for terminal-notifier in System Settings. Windows may show SnoreToast. Linux requires notify-send.

Accurate event handling

Ordinary Codex turn endings do not produce completion notifications. Subagents, CLI sessions, and sessions outside the current workspace are ignored. Interrupted work, pending questions, new user input, and continued turns cancel candidate completion alerts.

Structured synchronous question prompts are tracked until their matching answer. Async prompts must first be accepted; a subsequent user message clears them. A short settling window suppresses questions already answered or canceled before delivery. Explicit waiting-for-input signals also support ordinary prose questions.

Task completion requires Codex to explicitly declare that the entire task is complete, relevant checks have passed, and no required work, approval, clarification, deployment or external verification remains pending. It is a declaration by the agent, not independent verification of success. Without workspace task signals, completion alerts stay silent. Enable them only in workspaces where you want this behavior.

The workspace instructions use hidden Markdown comments on their own line:

<!-- codex-notification:question -->
<!-- codex-notification:task-complete -->

These are recognized only in the final task-complete record and outside code fences. Question signals take precedence over completion signals. A plain task_complete record with no signal is ignored.

Settings

Setting (codexAttention.) Default Purpose
notificationMode both both, questionsOnly, or taskCompleteOnly.
enabled true Monitor this workspace's local IDE chats.
desktopNotifications true Native OS notifications.
editorNotifications true Editor notification banners.
sound true Request native sound on macOS/Windows; OS settings still apply.
backgroundOnly false Only alert while this editor window is unfocused.
notifyOnComplete true Additional switch for explicitly declared task completion.
notifyOnQuestion true Additional switch for unanswered input prompts.
home empty Absolute local Codex home; defaults to CODEX_HOME, then ~/.codex.

Notifications appear even while the editor is focused by default (backgroundOnly: false). Click the status-bar bell to pause/resume. When completion setup is missing, the status bar offers setup instead. Open Codex opens the official Codex sidebar; it does not select a particular chat. Multiple main chats in the same workspace may each produce relevant alerts. Empty editor windows produce no session alerts. Remote-host records must be available locally to be monitored.

Privacy and compatibility

The extension reads local sessions/**/rollout-*.jsonl incrementally. It retains only local file offsets, bounded partial-record buffers, boolean eligibility, pending-question metadata, and hashed deduplication keys. Notifications use fixed generic text; no prompts, responses, account details, paths, or session IDs are exposed. It does not read auth files, send network requests, approve actions, or transmit telemetry. Claude hooks are installed only through the explicit workspace setup command.

The rollout schema is not a stable public API; detection must be rechecked after Codex changes. Questions that provide neither a supported structured prompt nor the explicit waiting-for-input signal are not detected. Already issued OS alerts cannot be retracted if a question is answered later.

Native helpers are distributed through node-notifier with network fallbacks disabled. The macOS helper is a universal build from unmodified terminal-notifier 3.1.0 source; provenance and licenses are in vendor/. Desktop delivery depends on OS permissions and Focus/Do Not Disturb. Windows/Linux delivery needs separate platform testing.

Development

Run npm ci --ignore-scripts, npm test, then npx --yes @vscode/vsce package. Build the generated macOS helper as described in vendor/README.md before packaging from a clean checkout. Never bundle conversation records or workspace AGENTS.md files.

MIT. Independent project; not affiliated with or endorsed by OpenAI.

Claude Code alerts included in this extension

Version 0.3.0 combines Codex and Claude notifications under the existing codex-attention extension ID. A separate Claude notification extension is not required.

Run Codex notification: Enable Claude Hooks in This Workspace, then start a new Claude Code session. Node.js must be on its PATH. Test with Test Claude Response Notification and Test Claude Input Notification.

Claude response alerts mean the main agent finished responding and its response is ready for review; they do not certify task completion. Permission, idle and elicitation notifications mean attention is needed. Timing follows Claude Code hooks. User interrupts, subagent stops and Stop events with active background work are ignored.

Both providers share the existing desktop/editor delivery, sound, backgroundOnly and pause controls. The notification mode applies to both. Claude-specific settings are codexAttention.claude.enabled, codexAttention.claude.notifyOnReady and codexAttention.claude.notifyOnInput. Existing Codex settings and command IDs are retained.

Setup merges marked Stop and Notification hooks into .claude/settings.local.json, preserves unrelated settings and your status line, and backs up existing settings. It replaces the earlier standalone Claude notification bridge handlers, preventing duplicate delivery from those handlers. Disable or uninstall the development claude-attention extension if previously installed. Organization policies may disable hooks; this extension does not override them.

The hook processes stdin locally and stores only event kind, timestamp and a hashed workspace routing scope in local extension storage. It never retains raw hook input, messages, tool arguments, session IDs or credentials. The IDE must remain open on the same accessible machine. To disconnect, remove only handlers marked Claude notification bridge from your local Claude settings.

Official hook reference: https://code.claude.com/docs/en/hooks

  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
  • Your Privacy Choices
  • Consumer Health Privacy
© 2026 Microsoft