What version of the Codex App are you using?
Unknown from local package lookup. Get-AppxPackage did not return a Codex package in this environment.
Embedded CLI/runtime observed:
codex-cli 0.130.0-alpha.5
What subscription do you have?
Unknown.
What platform is your computer?
Microsoft Windows NT 10.0.26200.0
User timezone/region context: Africa/Casablanca / Morocco. The user is trying to determine whether this is a Windows limitation, region availability issue, or account/workspace rollout issue.
What issue are you seeing?
The Chrome plugin is not discoverable in Codex Desktop Plugins, even though the official Codex Chrome extension docs say it should be added from Codex -> Plugins -> Add the Chrome plugin.
Local plugin cache inspection shows no Chrome plugin currently available:
~/.codex/plugins/cache/openai-curated:
atlassian-rovo
build-web-apps
canva
gmail
google-calendar
granola
hyperframes
openai-developers
outlook-email
remotion
sharepoint
~/.codex/plugins/cache/openai-bundled:
browser-use
A tool search inside the Codex session exposed plugin/app surfaces such as Canva, OpenAI Platform, and GitHub, but no Chrome or Browser plugin surface for direct use.
What steps can reproduce the bug?
- Open Codex Desktop on Windows.
- Go to Plugins.
- Search for Chrome / Codex Chrome extension / browser.
- Observe that the Chrome plugin is not available to add.
- Inspect local plugin cache under
~/.codex/plugins/cache.
- Observe that
openai-bundled contains browser-use only and openai-curated does not contain Chrome.
What is the expected behavior?
If Chrome is available for this account/platform/region, Codex Desktop should expose the Chrome plugin in Plugins so the user can install/connect the Chrome extension and use @Chrome for signed-in browser workflows.
If Chrome is intentionally gated by region, workspace controls, subscription, or staged rollout, the Plugins UI/docs should state that clearly instead of making it look like a missing or broken Windows install.
Additional information
Feedback / reference ID from the user:
36ea6cb6-2702-4156-9031-b078a607332f
Related existing issue with a similar symptom from Norway/EU:
Official docs referenced while troubleshooting:
The current local evidence points to availability/gating or plugin marketplace filtering rather than a simple Chrome extension connection problem, because the Chrome plugin is not present in the plugin cache or discoverable from Plugins in the first place.
What version of the Codex App are you using?
Unknown from local package lookup.
Get-AppxPackagedid not return a Codex package in this environment.Embedded CLI/runtime observed:
What subscription do you have?
Unknown.
What platform is your computer?
User timezone/region context:
Africa/Casablanca/ Morocco. The user is trying to determine whether this is a Windows limitation, region availability issue, or account/workspace rollout issue.What issue are you seeing?
The Chrome plugin is not discoverable in Codex Desktop Plugins, even though the official Codex Chrome extension docs say it should be added from Codex -> Plugins -> Add the Chrome plugin.
Local plugin cache inspection shows no Chrome plugin currently available:
A tool search inside the Codex session exposed plugin/app surfaces such as Canva, OpenAI Platform, and GitHub, but no Chrome or Browser plugin surface for direct use.
What steps can reproduce the bug?
~/.codex/plugins/cache.openai-bundledcontainsbrowser-useonly andopenai-curateddoes not contain Chrome.What is the expected behavior?
If Chrome is available for this account/platform/region, Codex Desktop should expose the Chrome plugin in Plugins so the user can install/connect the Chrome extension and use
@Chromefor signed-in browser workflows.If Chrome is intentionally gated by region, workspace controls, subscription, or staged rollout, the Plugins UI/docs should state that clearly instead of making it look like a missing or broken Windows install.
Additional information
Feedback / reference ID from the user:
Related existing issue with a similar symptom from Norway/EU:
Official docs referenced while troubleshooting:
The current local evidence points to availability/gating or plugin marketplace filtering rather than a simple Chrome extension connection problem, because the Chrome plugin is not present in the plugin cache or discoverable from Plugins in the first place.