codex - 💡(How to fix) Fix Approval Policy "Never" says it runs without approval but blocks Computer Use approvals [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#19554Fetched 2026-04-26 05:15:11
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Timeline (top)
labeled ×4commented ×1

Code Example

Computer Use approval denied via MCP elicitation for app 'com.apple.calculator'.
Computer Use approval denied via MCP elicitation for app 'com.apple.podcasts'.
Computer Use approval denied via MCP elicitation for app 'com.apple.finder'.

---

Never
Run without asking for approval
RAW_BUFFERClick to expand / collapse

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

26.422.30944 (build 2080)

What subscription do you have?

Personal account / not sure; no Workspace settings or Admin area visible in Codex Desktop.

What platform is your computer?

Darwin 25.4.0 arm64 arm (macOS 26.4.1 build 25E253)

What issue are you seeing?

In Codex Desktop settings, Approval Policy "Never" is described as:

Run without asking for approval

This reads like actions will run automatically without prompting. In practice, when using the Computer Use plugin, approval-elicited actions fail immediately and no approval dialog appears.

Exact errors observed:

Computer Use approval denied via MCP elicitation for app 'com.apple.calculator'.
Computer Use approval denied via MCP elicitation for app 'com.apple.podcasts'.
Computer Use approval denied via MCP elicitation for app 'com.apple.finder'.

This makes "Never" look like the most permissive option, but the actual behavior appears to be "never allow approvals" / deny any approval-elicited action. This was confusing enough to block use of Computer Use for several days until the approval policy was changed away from "Never".

What steps can reproduce the bug?

  1. Open Codex Desktop settings.
  2. Set Approval Policy to Never.
  3. Note that the UI description says Run without asking for approval.
  4. Ask Computer Use to control a local app, for example:
    • open Calculator and enter 2+2
    • open Podcasts
    • inspect Finder
  5. Observe that no approval prompt appears and the action fails immediately with Computer Use approval denied via MCP elicitation ....
  6. Change Approval Policy away from Never to a policy that allows prompting/approval.
  7. Repeat a Computer Use action. It works after the policy is changed.

What is the expected behavior?

Either the behavior or the UI copy should be changed so the policy is unambiguous.

If Never is intended to mean "do not ask and deny approval-required actions", the description should say that clearly, for example:

Never ask for approval. Actions requiring approval will be blocked.

If Run without asking for approval is the intended meaning, then Computer Use approval prompts should be auto-approved instead of failing immediately.

The current copy makes Never sound like an auto-approve/permissive mode, while the observed behavior is restrictive for approval-elicited actions.

Additional information

Approximate first failing attempts: April 24, 2026 around 15:40-15:45, Asia/Shanghai timezone.

The full Approval Policy dropdown options shown in Codex Desktop are:

  • Untrusted
  • On Request
  • On Failure
  • Never

The confusing option is:

Never
Run without asking for approval

The settings screenshot also shows Sandbox setting: Workspace write, and network access enabled. I understand that the sandbox setting is execution sandboxing and does not necessarily indicate a Business/Enterprise workspace.

I searched existing issues for Approval Policy, Run without asking for approval, and approval denied via MCP elicitation; I did not find an exact duplicate for this copy/UX issue.

A screenshot of the full settings panel showing Approval Policy: Never and the description is available and can be attached.

<img width="830" height="353" alt="Image" src="https://github.com/user-attachments/assets/5eb6fe2a-a9d7-451a-8424-d8e7a18c4abb" />

extent analysis

TL;DR

The "Never" Approval Policy in Codex Desktop settings may need its description changed to reflect its actual behavior of denying approval-elicited actions without prompting.

Guidance

  • Verify the Approval Policy behavior by setting it to "Never" and attempting a Computer Use action that requires approval, observing if the action is denied without a prompt.
  • Check the Codex Desktop settings UI to ensure the description of the "Never" policy accurately reflects its behavior, which appears to be "do not ask and deny approval-required actions".
  • Consider changing the Approval Policy to a different option, such as "On Request" or "On Failure", to allow for approval prompts and successful completion of Computer Use actions.
  • Review the Sandbox setting and network access configuration to ensure they are not contributing to the issue, although the provided information suggests they are not directly related.
  • If the issue persists, attach a screenshot of the settings panel showing the "Approval Policy: Never" and description for further clarification.

Example

No code snippet is provided as the issue appears to be related to the UI description and behavior of the Approval Policy in Codex Desktop settings.

Notes

The exact behavior and intended meaning of the "Never" Approval Policy are unclear, and further clarification from the developers or documentation may be necessary to resolve the issue.

Recommendation

Apply a workaround by changing the Approval Policy to a different option, such as "On Request" or "On Failure", to allow for approval prompts and successful completion of Computer Use actions, as the current "Never" policy description is misleading and causes confusion.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING