Codex Desktop falsely reports @chrome plugin unavailable when bundled Chrome plugin is installed

What happened?

In Codex Desktop on Windows, I invoked the Chrome plugin explicitly:

[@chrome](plugin://chrome@openai-bundled) 打开百度

The assistant initially said the Chrome plugin was unavailable and fell back to opening Baidu with the default browser via a shell command. That was incorrect: the Chrome plugin was installed locally and could be used successfully after manually locating the trusted bundled marketplace path.

Expected behavior

When a user explicitly invokes @chrome or plugin://chrome@openai-bundled, Codex should route to the Chrome plugin/skill, or at least check the bundled marketplace Chrome plugin path before saying Chrome is unavailable.

Actual behavior

The agent inferred that Chrome was unavailable from the active plugin/tool list and did not inspect the installed bundled Chrome plugin paths until challenged.

Reproduction steps

1. In Codex Desktop on Windows, invoke:

[@chrome](plugin://chrome@openai-bundled) 打开百度

1. Observe that the agent may say the Chrome plugin is unavailable and use a shell/default-browser fallback.
2. Inspect local plugin paths and find Chrome present under:

C:\Users\111\.codex\plugins\cache\openai-bundled\chrome\0.1.7

1. Importing from the cache path fails as untrusted with:

privileged native pipe bridge is not available; browser-client is not trusted. Load browser-client from the openai-bundled marketplace directory.

1. Importing from the trusted bundled marketplace path succeeds:

C:\Users\111\.codex\.tmp\bundled-marketplaces\openai-bundled\plugins\chrome\scripts\browser-client.mjs

1. After calling setupAtlasRuntime({ globals: globalThis }) and agent.browsers.get("extension"), Chrome opens Baidu successfully.

Evidence

Successful Chrome result after using the trusted path:

{
  "title": "百度一下，你就知道",
  "url": "https://www.baidu.com/"
}

Environment

• Product: Codex Desktop app / Codex Chrome plugin
• OS: Microsoft Windows 11 Home China, 64-bit, version 10.0.26200, build 26200
• Chrome version: 148.0.7778.97
• Time observed: 2026-05-13 16:22:59 +08:00

Impact

This creates false negatives for installed plugins. A user can have the Chrome plugin installed and working, but Codex may still claim it is unavailable if the plugin is not exposed in the active plugin list for that turn.