Computer Use Plugins Unavailable
Open 💬 4 comments Opened Jun 19, 2026 by brapoport2020
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
What version of the Codex App are you using (From “About Codex” dialog)?
Version 26.616.32156 • Released Jun 18, 2026
What subscription do you have?
ChatGPT Business
What platform is your computer?
Windows 11 x86
What issue are you seeing?
Computer Use Plugins Unavailable. Unable to use Chrome or Computer Use
What steps can reproduce the bug?
Feedback ID: no-active-thread-019ee05b-7a15-7253-9f48-115175b3752e
What is the expected behavior?
Able to use the features I'm paying for. Codex was able to use Chrome up until a week ago.
Additional information
_No response_
4 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
I’m seeing the same issue on Windows.
Codex version:
26.609.71450, released Jun 15, 2026.
Feedback ID:
no-active-thread-019edcd1-f028-7e70-887e-a19ccc7c8a7b
Current behavior:
Settings → Computer use shows “Computer Use plugins unavailable.”
Related errors I saw before this:
What I tried:
Result:
Computer Use still shows “Computer Use plugins unavailable.”
I'm having the same problem.
Environment:
no-active-thread-019eefab-6507-70c2-911d-851973a25729I tried:
Computer use and in-app browser still unavailable
I maintain WinBridge Recovery, an independent Windows Codex Desktop local recovery/diagnostic tool: https://github.com/zemeng5208/winbridge-recovery
The follow-up reports here contain several signals that are worth separating from a pure account/availability problem:
native host registry entry is missing,privileged native pipe bridge is not available; browser-client is not trusted, andfailed to write kernel assets: The system cannot find the path specified. Those can occur when the official bundled assets exist but the user-owned marketplace/cache/runtime/Native Host layers are incomplete or stale after an update.WinBridge v3.1.1 checks the currently installed Store AppX first, then compares the generated
openai-bundledmarketplace, Browser/Chrome/Computer Use versioned caches andlatest, CUA/Node REPL runtime paths,CODEX_CLI_PATH/NODE_REPL_NODE_PATH, the Chrome Native Messaging manifest/registry entry, andchrome-native-hosts-v2.json. If those local layers are inconsistent, it can rebuild the user-owned state from the already installed official package through verified staging, SHA-256 checks, backups and rollback.There is an important boundary: if all of those local layers are healthy and the account/workspace still does not receive Browser/Computer Use because of a rollout/entitlement decision or tool-provisioning issue, WinBridge cannot and should not force it on. The value here is distinguishing and recovering the local broken-state variant without touching authentication or bypassing product gates.
It does not modify WindowsApps ownership/ACLs or bundle/patch OpenAI binaries.