Bug report: Chrome plugin is installed and enabled, but browser automation calls time out

Summary

Codex Chrome plugin appears installed and enabled, and the native host manifest check passes, but browser automation calls time out before any page can be opened or any tab list can be read.

This happens even for the minimal task:

@chrome open google.com

Environment

• OS: Windows
• Codex app: Windows app, observed package path includes OpenAI.Codex_26.506.2212.0_x64
• Chrome plugin cache version: openai-bundled/chrome/0.1.7
• Codex Chrome Extension version: 1.1.4_0
• Chrome: Chrome/147.0.7727.138
• Native host: com.openai.codexextension

Expected behavior

Codex should be able to use the Chrome plugin to:

• list open Chrome tabs
• create a new controlled tab
• open https://www.google.com

Actual behavior

All Chrome automation calls time out. Examples:

const { setupAtlasRuntime } = await import(".../scripts/browser-client.mjs");
await setupAtlasRuntime({ globals: globalThis });
globalThis.browser = await agent.browsers.get("extension");
const tabs = await browser.user.openTabs();

Result:

js execution timed out; kernel reset, rerun your request

Same result when trying:

globalThis.tab = await browser.tabs.new();
await tab.goto("https://www.google.com");

Checks already performed

Chrome is installed and running.

scripts/check-extension-installed.js --json reports:

{
  "installed": true,
  "registered": true,
  "enabled": true,
  "disabled": false,
  "versions": ["1.1.4_0"],
  "exitCode": 0
}

scripts/check-native-host-manifest.js --json reports:

{
  "exists": true,
  "nameMatches": true,
  "hasExpectedOrigin": true,
  "registryMatchesManifestPath": true,
  "correct": true,
  "problem": null
}

I also tried:

• reinstalling the Chrome extension
• reinstalling the Codex Chrome plugin
• restarting Codex
• restarting Chrome
• killing stale extension-host.exe processes
• opening a new Chrome window and retrying

The behavior did not change.

Important comparison

A separate local Chrome instance launched with a dedicated profile and remote debugging port works correctly.

Example:

chrome.exe --remote-debugging-port=9223 --user-data-dir=<separate-profile>

Then http://127.0.0.1:9223/json/version responds normally, and pages can be inspected through the DevTools protocol.

So Chrome itself and the machine's browser automation capability appear to work. The failure seems specific to the Codex Chrome plugin/native-host automation path.

Reproduction steps

1. Install Chrome plugin from the Codex app.
2. Confirm Chrome extension is installed and enabled.
3. Ask Codex:

@chrome open google.com

1. Observe timeout.

Request

Please advise how to collect deeper logs for the Chrome plugin/native host handshake, or whether this is a known issue with the current Windows Codex app / Chrome plugin combination.