Codex Desktop approval notification opens blank/error route for ambient suggestion command
What version of the Codex App are you using (From “About Codex” dialog)?
26.422.30944
What subscription do you have?
Enterprise
What platform is your computer?
MacOS / Darwin 25.4.0 arm64 arm
What issue are you seeing?
Codex Desktop repeatedly shows macOS desktop notifications asking for approval to run a command. Clicking the notification opens a blank Codex view with a brief plain-text error that flashes too quickly to read. Approving or denying does not resolve it; restarting Codex causes it to happen again immediately.
This appears to come from background ambient suggestion tasks rather than a visible conversation. The approval notification targets a hidden/stale/inaccessible task route, so the click-through opens an error route instead of the relevant approval UI.
Observed logs:
error Conversation state not found conversationId=<redacted>
[desktop-notifications] show approval conversationId=<redacted> kind=commandExecution requestId=1
[desktop-notifications] notification click open notificationId=approval-2
Sentry breadcrumbs showed repeated 403s:
GET https://chatgpt.com/backend-api/wham/tasks/<redacted> -> 403
GET https://chatgpt.com/backend-api/wham/tasks/<redacted>/turns -> 403
Background task prompt seen in logs:
Generate 0 to 3 ambient suggestions for this local project...
Example requested commands:
pwd
rg --files <project> | sed ... | head -n 200
git log --oneline --decorate -n 15
Expected:
Clicking an approval notification should open the relevant approval UI, or Codex should avoid showing desktop approval notifications for background/ambient tasks whose conversation/task is not accessible in the app.
Privacy:
Local usernames, project paths, task IDs, conversation IDs, and request IDs have been redacted.
What steps can reproduce the bug?
I just open the app and the notifications start coming in.
What is the expected behavior?
I shouldn't get random notifications for approval that don't go anywhere.
Additional information
_No response_
2 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
I’m seeing the same class of issue on Linux/Sway with Mako notifications.
Environment:
Observed notification:
But clicking/opening did not show an actionable approval.
Relevant log pattern:
Conversation state not found conversationId=...[desktop-notifications] show approval ... kind=commandExecution requestId=...[desktop-notifications] forward show kind=permission notificationId=approval-local-...[desktop-notifications] show notification ... kind=permissionI also saw repeated:
[ambient-suggestions-background-refresh] Failed to refresh ambient suggestions ... trigger=backgroundIn one reproduction, background/heartbeat automation log-inspection commands caused several approval notifications (
approval-local-10throughapproval-local-13) tied to a hidden/background conversation. The commands were read-only (find/rgover Codex logs), and there was no visible approval surface by the time I opened Codex.Expected behavior: