macOS desktop shows "Computer Use plugin unavailable" even though bundled computer-use plugin exists

Open 💬 5 comments Opened Apr 21, 2026 by JOJOMRJ
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

Title: macOS desktop shows "Computer Use plugin unavailable" even though bundled computer-use plugin exists

Summary

On the Codex macOS desktop app, Settings -> Computer Use shows "Computer Use plugin unavailable".

However, the bundled Computer Use plugin files are already present inside the app bundle, so this does not appear to be a missing local installation.

Environment

  • Codex App: 26.417.41555
  • Codex CLI: 0.122.0-alpha.13
  • macOS: 15.6 (24G84)
  • Architecture: arm64 / Apple Silicon
  • Login: ChatGPT account
  • Region: China
  • HOME: /Users/jojo
  • CODEX_HOME: default ~/.codex
  • Note: path does not contain @

What I expected

Computer Use should be available, or at least installable / permission-requesting from the desktop app.

What happened

  • Settings -> Computer Use shows: Computer Use plugin unavailable
  • Restarting Codex does not help
  • Logging out and back in does not help
  • Enabling config flags does not help

Local evidence

The bundled plugin exists here:

  • /Applications/Codex.app/Contents/Resources/plugins/openai-bundled/plugins/computer-use

Helper bundle exists here:

  • /Applications/Codex.app/Contents/Resources/plugins/openai-bundled/plugins/computer-use/Codex Computer Use.app

Executable exists here:

  • /Applications/Codex.app/Contents/Resources/plugins/openai-bundled/plugins/computer-use/Codex Computer Use.app/Contents/MacOS/SkyComputerUseService

Relevant config

My ~/.codex/config.toml includes:

[features]
apps = true
plugins = true

[plugins."computer-use@openai-bundled"]
enabled = true

This did not change the behavior.

Relevant logs

Desktop app logs repeatedly show:

warning [BundledPluginsMarketplace] bundled_plugins_marketplace_resolve_failed errorMessage="Bundled plugins marketplace has no enabled plugins."

Example log file:

  • ~/Library/Logs/com.openai.codex/2026/04/21/codex-desktop-084a64fc-b152-460d-a665-884ac66fe3e8-18274-t0-i1-031853-0.log

Additional diagnostics

I checked the local state DB and found that remote_control_enrollments is empty:

  • ~/.codex/state_5.sqlite

This makes me suspect either:

  1. the bundled plugin is not being recognized/enabled by the desktop app, or
  2. my account is not receiving the server-side enrollment/enablement needed for Computer Use.

Steps to reproduce

  1. Install/open Codex desktop app on macOS
  2. Log in with ChatGPT account
  3. Open Settings -> Computer Use
  4. Observe Computer Use plugin unavailable

Notes

This seems similar to:

  • #18258
  • #18404
  • #18555

But in my case:

  • the machine is Apple Silicon
  • the plugin bundle exists locally
  • the home path does not contain @

Happy to provide more logs if useful.

View original on GitHub ↗

5 Comments

github-actions[bot] contributor · 4 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #18258
  • #18404
  • #18555

Powered by Codex Action

IgorGanapolsky · 3 months ago

I hit a related "Computer Use exists locally but the active runtime cannot use it" failure while fixing an OpenClaw/Codex Mac setup. A few checks that helped separate the layers:

codex mcp list
codex plugin marketplace add /Applications/Codex.app/Contents/Resources/plugins/openai-bundled
codex mcp list

Also check that the runtime actually sees the installed plugin cache, not just the app bundle:

ls ~/.codex/plugins/cache/openai-bundled/computer-use/*/.codex-plugin/plugin.json
ls ~/.codex/plugins/cache/openai-bundled/computer-use/*/.mcp.json

The failure mode I saw was not the same UI string, but the important distinction was:

  • bundled plugin present in /Applications/Codex.app/... did not mean the active agent runtime had the MCP server loaded
  • a stale/isolated Codex home could have plugin config but no usable auth/account state
  • macOS Screen Recording + Accessibility can both be granted while the app-server runtime still cannot see computer-use

For people debugging this class of Mac setup, the useful smoke test is not only "does the file exist?" but "can the active runtime call a Computer Use tool such as list apps / inspect active UI?"

I packaged my full checklist and paid setup service here, but the diagnostics above are the relevant free part for this issue:
https://igorganapolsky.github.io/openclaw-mac-ai-workstation-setup/

IgorGanapolsky · 3 months ago

This is almost always the bundled plugin path being correct but the active
Codex home not having registered it — the cache that Codex reads lives in
your user directory and the install never hydrates it.

codex mcp list
ls -la ~/.codex/plugins/cache/openai-bundled/computer-use/*/.mcp.json
# If absent:
codex plugin marketplace add /Applications/Codex.app/Contents/Resources/plugins/openai-bundled
codex mcp list

If computer-use is still missing after that, you have a second Codex home
(see Symptom 5 in the walkthrough — stale CODEX_HOME from a shell rc that
exported one path while the installer wrote to another).

Walkthrough with all 6 root causes:
https://igorganapolsky.github.io/openclaw-mac-ai-workstation-setup/troubleshooting.html

Free local script that runs all checks and redacts secrets:
clone the repo and run node scripts/self-diagnose.mjs — writes a bundle to
your Desktop you can review or paste into the $19 quick read for a confirmed
root cause.

IgorGanapolsky · 3 months ago

@JOJOMRJ — adding a few more angles on the macOS 15.6 / bundled-plugin-exists state, since the install path itself isn't the gap:

1. Confirm the active macOS user's cache is actually hydrated. The bundled plugin existing under /Applications/Codex.app/... and the runtime being able to use it are different states — the cache populates per macOS user, not per install. Worth verifying directly:

ls ~/.codex/plugins/cache/openai-bundled/computer-use/*/.mcp.json
ls ~/.codex/plugins/cache/openai-bundled/computer-use/*/.codex-plugin/plugin.json

If both are missing for your current shell user, rehydrate:

codex plugin marketplace add /Applications/Codex.app/Contents/Resources/plugins/openai-bundled
codex mcp list

2. SkyComputerUseClient LC_BUILD_VERSION vs your macOS. If the bundled client targets a newer macOS than you're on, registration succeeds but launch fails silently and Codex surfaces the plugin as "unavailable":

/usr/bin/otool -l "/Applications/Codex.app/Contents/Resources/plugins/openai-bundled/computer-use/"*/SkyComputerUseClient \
  | grep -A 2 LC_BUILD_VERSION

If minos is higher than your current macOS, that's the gap and a permission grant or reinstall won't fix it.

3. The marketplace-regeneration bug from #21579. If the above two check out, grep your Codex Desktop logs right after a relaunch for:

bundled_plugins_runtime_marketplace_written pluginCount=2 pluginNames=["browser","latex"]
bundled_plugin_uninstall_requested pluginId=computer-use@openai-bundled reason=not_in_bundled_marketplace_plugin_names

If both lines appear on every startup, that's the same bug @ShalevZorany identified in #21579 — Codex Desktop is regenerating the bundled marketplace as browser+latex only and removing computer-use on every launch. Local fixes don't survive a relaunch in that case; the workaround is to restore openai-bundled from the app bundle after each Codex start.

(Longer write-up of these three failure classes plus the codesign / TCC variants: https://igorganapolsky.github.io/openclaw-mac-ai-workstation-setup/troubleshooting.html?utm_source=codex-issue&utm_medium=funnel&utm_campaign=qr-2026. If you'd rather send a redacted log bundle and get the specific root cause back, the $19 Quick Read does same-day diagnosis: https://igorganapolsky.github.io/openclaw-mac-ai-workstation-setup/speed-to-lead.html)

ShalevZorany · 2 months ago

For what it's worth, this now seems to be working for me after updating Codex.

My guess is that it may have been related to the recent Computer Use / plugin availability rollout in Europe, which now appears to be available. I am actually based in Israel, so the regional behavior was a bit confusing, but after updating Codex the feature is visible and working on my machine.

It may be worth checking again after updating to the latest Codex build.