›_ Codex Issues
Codex Issues / #18521

Windows notification Approve / Approve for session clicks do nothing and do not grant the pending approval request

Open 💬 3 comments Opened Apr 19, 2026 by jianzhangg

What version of the Codex App are you using (From “About Codex” dialog)?

26.415.4716.0

What subscription do you have?

Not sure

What platform is your computer?

Windows 11 24H2 (build 26100.4946); OSVersion reports Microsoft Windows NT 10.0.26100.0 x64

What issue are you seeing?

When Codex App shows a Windows notification for an approval request, clicking Approve or Approve for session in the Windows notification itself does nothing.

The current pending approval inside the Codex conversation is not granted, and the request remains blocked until I go back into the conversation and click the approval there again.

The core problem is not that the prompt appears again later. The problem is that the Windows notification action itself does not resolve the current approval request at all.

What steps can reproduce the bug?

  1. Use Codex App on Windows to run any action that requires approval.
  2. Wait for the Windows toast / notification with the approval actions.
  3. Click Approve or Approve for session directly in the Windows notification.
  4. Observe that nothing happens in Codex: the request is still pending and the action is still blocked.
  5. Return to the Codex conversation and click the approval there.
  6. Observe that the request is granted immediately from inside the conversation.

This happens consistently for me.

What is the expected behavior?

Clicking Approve in the Windows notification should immediately grant the current pending request.

Clicking Approve for session should both grant the current request and apply the session-scoped approval behavior for subsequent matching requests.

It should not require a second manual approval inside the Codex conversation.

Additional information

  • This appears specific to the Windows notification action path.
  • This is different from issues where approvals are asked again later. Here, the current request is never granted from the Windows notification action.
  • The notification shows multiple actions, but the approval actions are ineffective for the current request.
  • My practical workaround is to ignore the Windows notification and go back to the Codex conversation to click the approval there.
  • Codex App was installed from Microsoft Store.

View original on GitHub ↗

3 Comments

KhaoticEnigma · 4 months ago

Can confirm this. They do pop and have the correct options, but they do absolutely nothing. At best, sometimes the app opens up when I select a choice so I can at least hit the working version in-app, but this is quite annoying honestly.

NedMalki-Chief · 3 months ago

Adding another confirmed repro on Windows Codex Desktop after the latest update.

Environment:

  • Codex app package: OpenAI.Codex 26.429.2026.0 x64
  • Windows: x64, HAL/build 10.0.26100.1
  • Config signal: approvals_reviewer = "user", [windows] sandbox = "elevated"
  • The session was explicitly given full access/elevated permissions in the app UI.

Observed behavior:

  • Codex shows a Windows approval popup/notification.
  • Clicking Approve does not unblock the pending request.
  • Clicking Approve for session also does not grant the current request or persist approval for the session.
  • The app continues asking for approvals even though this specific session was already granted full/elevated access.

Expected behavior:

  • Approve should grant the current pending request once.
  • Approve for session should grant the current request and remember the session-scoped approval.
  • A full-access/elevated session should not continue prompting for approvals that are covered by that session permission.

Notes:

  • Not attaching raw logs/config because they contain local paths and potentially sensitive workspace data.
  • Local logs are available if a maintainer asks for a specific sanitized excerpt.
dark0fire · 3 months ago

I also have this issue.

Pro subscription.

I work on windows 10 pro.

Installed with installer from website, not microsoft store.

Codex is up-to-date. Even tried booting codex with admin priviledges.