codex - 💡(How to fix) Fix Codex Desktop approval notification opens blank/error route for ambient suggestion command [1 comments, 2 participants]

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. error Conversation state not found conversationId=<redacted>

TL;DR

The issue can be mitigated by modifying the Codex App's behavior to handle background ambient suggestion tasks differently, potentially by suppressing desktop notifications for inaccessible tasks.

Guidance

• Investigate the conversationId and requestId values in the observed logs to understand why the conversation state is not found, leading to the error.
• Review the Sentry breadcrumbs to analyze the repeated 403 errors when accessing task resources, which might indicate a permission or authentication issue.
• Consider implementing a check to ensure that only accessible tasks trigger desktop notifications, preventing the approval notification from targeting hidden or stale task routes.
• Examine the background task prompt and example requested commands to determine if there's a specific condition or setting that triggers the unwanted notifications.

Example

No code snippet is provided due to the lack of specific implementation details in the issue.

Notes

The root cause of the issue seems to be related to the handling of background tasks and conversation states within the Codex App, but without more information about the app's internal logic and configuration, a definitive fix cannot be provided.

Recommendation

Apply a workaround to suppress desktop notifications for background ambient tasks whose conversation/task is not accessible in the app, as this seems to be the most direct way to mitigate the issue given the current information.