Diagnose Codex Desktop Computer Use, Chrome, and Browser plugin availability problems on Windows.
.\scripts\codex-computer-use-doctor.ps1Preview a conservative repair plan:
.\scripts\codex-computer-use-doctor.ps1 -RepairApply the repair plan:
.\scripts\codex-computer-use-doctor.ps1 -Repair -ApplyCodex Desktop can use Computer Use to operate desktop apps, Chrome to work with logged-in browser sessions, and Browser for in-app web testing. On Windows, users can run into states where Computer Use or Chrome appears installed or connected but the corresponding tool is not available in a Codex thread.
codex-windows-plugin-doctor is a small read-only PowerShell diagnostic tool
focused on the common Windows failure mode: Computer Use, Chrome, or Browser is
configured locally, but Codex cannot expose the expected @computer, @chrome,
or browser-control tools in the active session.
The report is designed to be pasted into a GitHub issue, Reddit post, support thread, or Codex troubleshooting conversation.
- Codex home directory and
config.toml. - Bundled plugin config entries for Browser, Chrome, and Computer Use.
- OpenAI bundled plugin marketplace config.
- Cached plugin directories.
- Plugin skill files for Computer Use, Chrome, and Browser.
- Chrome native messaging host registry entries.
- Codex Chrome extension installation in common Chrome profiles.
- A short next-step repair plan based on the missing signals.
Clone the repository:
git clone https://github.com/UPmeme/codex-windows-plugin-doctor.git
cd codex-windows-plugin-doctorNo dependencies are required beyond Windows PowerShell.
Run:
.\scripts\codex-computer-use-doctor.ps1Generate JSON:
.\scripts\codex-computer-use-doctor.ps1 -JsonSave a report:
.\scripts\codex-computer-use-doctor.ps1 -OutFile .\reports\codex-plugin-report.txt-Apply backs up Codex config first, mirrors the bundled plugin source into the
user .codex directory when a source is found, registers the repaired bundled
marketplace, reinstalls Browser, Chrome, and Computer Use plugins, and asks you
to restart Codex Desktop.
This project is especially aimed at this Windows symptom:
Computer Use is installed in Codex settings, but @computer or @Computer Use
does not expose a desktop-control tool in the current thread.
The same diagnostic also covers related Chrome symptoms:
The Codex Chrome extension says Connected, but Codex cannot control Chrome.
This tool is read-only by default. It does not modify Codex configuration, clear
caches, install extensions, edit registry keys, read credentials, or bypass
workspace policy unless you explicitly pass -Repair -Apply.
Repair mode is intentionally conservative. It backs up local Codex state first and avoids reading credentials. It cannot fix active-thread tool exposure, workspace policy, or rollout restrictions; after repair you still need to restart Codex Desktop and create a fresh thread.
It is not affiliated with OpenAI. It is a community diagnostic helper for users who need a structured local report.
See Computer Use troubleshooting and Windows plugin troubleshooting.
.\tests\smoke.ps1MIT