openclaw - 💡(How to fix) Fix Codex Computer Use approval denied via MCP elicitation from Discord/OpenClaw session while direct Codex chat works [2 comments, 3 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
openclaw/openclaw#75696Fetched 2026-05-02 05:31:32
View on GitHub
Comments
2
Participants
3
Timeline
8
Reactions
2
Author
Timeline (top)
mentioned ×3subscribed ×3commented ×2

Codex Computer Use works from a direct Codex Desktop chat, but fails when invoked through an OpenClaw Discord/Codex harness session with:

Computer Use approval denied via MCP elicitation for app 'com.google.Chrome'

The same Mac, same Codex app, and same Computer Use helper can read Chrome/Finder/Discord successfully from a normal Codex Desktop thread. This makes it look like the issue is not macOS Accessibility/Screen Recording permissions, but the MCP elicitation / approval bridge path used by OpenClaw channel sessions.

Error Message

From direct Codex Desktop chat:

Root Cause

Codex Computer Use works from a direct Codex Desktop chat, but fails when invoked through an OpenClaw Discord/Codex harness session with:

Computer Use approval denied via MCP elicitation for app 'com.google.Chrome'

The same Mac, same Codex app, and same Computer Use helper can read Chrome/Finder/Discord successfully from a normal Codex Desktop thread. This makes it look like the issue is not macOS Accessibility/Screen Recording permissions, but the MCP elicitation / approval bridge path used by OpenClaw channel sessions.

Code Example

Computer Use approval denied via MCP elicitation for app 'com.google.Chrome'

---

Computer Use approval denied via MCP elicitation for app 'com.google.Chrome'
RAW_BUFFERClick to expand / collapse

Summary

Codex Computer Use works from a direct Codex Desktop chat, but fails when invoked through an OpenClaw Discord/Codex harness session with:

Computer Use approval denied via MCP elicitation for app 'com.google.Chrome'

The same Mac, same Codex app, and same Computer Use helper can read Chrome/Finder/Discord successfully from a normal Codex Desktop thread. This makes it look like the issue is not macOS Accessibility/Screen Recording permissions, but the MCP elicitation / approval bridge path used by OpenClaw channel sessions.

Environment

  • macOS
  • Codex Desktop with bundled computer-use@openai-bundled
  • OpenClaw Discord channel session using Codex harness
  • Computer Use plugin is available in Codex direct chat
  • macOS Privacy & Security permissions are granted for Codex / Codex Computer Use / SkyComputerUseClient

Observed behavior

From direct Codex Desktop chat:

  • get_app_state works for Google Chrome
  • get_app_state works for Finder
  • get_app_state works for Discord

From OpenClaw/Discord routed Codex session:

Computer Use approval denied via MCP elicitation for app 'com.google.Chrome'

Earlier attempts also failed for Finder with the same approval-denied class of error.

No approval UI appears in the Discord/OpenClaw path. In Codex Desktop settings, Settings > Computer Use > Always allowed apps is empty.

Expected behavior

OpenClaw should either:

  1. surface/bridge the Codex Computer Use MCP elicitation approval back to the originating chat, or
  2. document that Codex Computer Use app-control approvals cannot currently be completed from channel-routed Codex harness sessions, or
  3. provide a way to pre-authorize / persist app approvals for channel-routed sessions.

Why this looks OpenClaw/Codex-harness related

OpenClaw docs say Codex Computer Use is a Codex-native MCP plugin and OpenClaw does not bypass Codex permissions.

The Codex harness docs also mention that Codex MCP tool approval elicitations are routed through OpenClaw's plugin approval flow only for some approval kinds, and other MCP elicitation requests fail closed. This behavior seems consistent with the observed approval denied via MCP elicitation.

Related

extent analysis

TL;DR

The issue can be mitigated by exploring alternative approval flows or configurations that allow Codex Computer Use to function through OpenClaw Discord/Codex harness sessions.

Guidance

  • Investigate the OpenClaw plugin approval flow to understand how MCP elicitation requests are handled and if there are any specific requirements or limitations for Codex Computer Use.
  • Review the Codex harness documentation to see if there are any known issues or workarounds for MCP tool approval elicitations failing closed.
  • Check the Settings > Computer Use > Always allowed apps configuration in Codex Desktop to see if adding specific apps (e.g., com.google.Chrome) to the list allows them to bypass the approval process.
  • Consider reaching out to the OpenClaw and Codex communities or support teams for further guidance on integrating Codex Computer Use with OpenClaw Discord/Codex harness sessions.

Notes

The issue seems to be related to the interaction between Codex Computer Use, OpenClaw, and the MCP elicitation approval flow. Without more information on the specific configurations and versions used, it's difficult to provide a definitive solution.

Recommendation

Apply workaround: Explore alternative approval flows or configurations, as the issue seems to be related to the integration of Codex Computer Use with OpenClaw Discord/Codex harness sessions, and a straightforward fix may not be available.

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…

FAQ

Expected behavior

OpenClaw should either:

  1. surface/bridge the Codex Computer Use MCP elicitation approval back to the originating chat, or
  2. document that Codex Computer Use app-control approvals cannot currently be completed from channel-routed Codex harness sessions, or
  3. provide a way to pre-authorize / persist app approvals for channel-routed sessions.

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix Codex Computer Use approval denied via MCP elicitation from Discord/OpenClaw session while direct Codex chat works [2 comments, 3 participants]