codex - 💡(How to fix) Fix Codex Desktop Chrome plugin hangs during extension backend bootstrap/openTabs on Windows

Official PRs (…)
ON THIS PAGE

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Error Message

Observed error:

Code Example

js execution timed out; kernel reset, rerun your request
This happens before any navigation or page interaction. I do not get far enough to call browser.tabs.new(), browser.tabs.list(), or tab.goto(...).

Environment details:

OS: Windows 10 Pro, 64-bit
Windows version: 2009
OS HAL: 10.0.26100.1
Shell: PowerShell
Codex CLI: codex-cli 0.129.0-alpha.15
Chrome plugin cache path: C:\Users\Administrator\.codex\plugins\cache\openai-bundled\chrome\0.1.7
Google Chrome: 147.0.7727.102
Chrome path: C:\Program Files\Google\Chrome\Application\chrome.exe
Default browser: Microsoft Edge (MSEdgeHTM)
Codex Chrome Extension ID: hehggadaopoacecdllhhajmbjkdcmajg
Codex Chrome Extension version: 1.1.4_0
Chrome profile checked by plugin scripts: C:\Users\Administrator\AppData\Local\Google\Chrome\User Data\Default

### What steps can reproduce the bug?

---

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

node scripts/chrome-is-running.js --json
node scripts/check-extension-installed.js --json
node scripts/check-native-host-manifest.js --json
The checks report Chrome running, extension installed/enabled, and native host configuration correct.

In the Node REPL tool, run:
const pluginRoot = "C:/Users/Administrator/.codex/plugins/cache/openai-bundled/chrome/0.1.7";

if (!globalThis.agent) {
  const { setupAtlasRuntime } = await import(`${pluginRoot}/scripts/browser-client.mjs`);
  await setupAtlasRuntime({ globals: globalThis });
}

if (!globalThis.browser) {
  globalThis.browser = await agent.browsers.get("extension");
}

await browser.nameSession("Chrome access test");
const tabs = await browser.user.openTabs();
The command hangs until the Node REPL tool times out:
js execution timed out; kernel reset, rerun your request

**What is the expected behavior?**

---

const tabs = await browser.user.openTabs();
After that, normal Chrome browser automation should be available.


**Additional information**
RAW_BUFFERClick to expand / collapse

What version of the Codex App are you using (From “About Codex” dialog)?

26.506.21252

What subscription do you have?

CHATGPT PLUS

What platform is your computer?

10.0.26100.1 x64 Windows 10 Pro 64-bit

What issue are you seeing?

The Codex Desktop Chrome plugin hangs while trying to establish the Chrome extension backend session.

Chrome is running, the Codex Chrome Extension is installed and enabled, and the native messaging host checks pass. However, when Codex tries to initialize browser automation or read open tabs, the Node REPL execution hangs until it times out.

Observed error:

js execution timed out; kernel reset, rerun your request
This happens before any navigation or page interaction. I do not get far enough to call browser.tabs.new(), browser.tabs.list(), or tab.goto(...).

Environment details:

OS: Windows 10 Pro, 64-bit
Windows version: 2009
OS HAL: 10.0.26100.1
Shell: PowerShell
Codex CLI: codex-cli 0.129.0-alpha.15
Chrome plugin cache path: C:\Users\Administrator\.codex\plugins\cache\openai-bundled\chrome\0.1.7
Google Chrome: 147.0.7727.102
Chrome path: C:\Program Files\Google\Chrome\Application\chrome.exe
Default browser: Microsoft Edge (MSEdgeHTM)
Codex Chrome Extension ID: hehggadaopoacecdllhhajmbjkdcmajg
Codex Chrome Extension version: 1.1.4_0
Chrome profile checked by plugin scripts: C:\Users\Administrator\AppData\Local\Google\Chrome\User Data\Default

### What steps can reproduce the bug?

```markdown
1. Install/enable the Chrome plugin in Codex Desktop.
2. Install/enable the Codex Chrome Extension in Google Chrome.
3. Confirm that Google Chrome is running.
4. Run the bundled plugin checks from:

```powershell
cd C:\Users\Administrator\.codex\plugins\cache\openai-bundled\chrome\0.1.7

node scripts/chrome-is-running.js --json
node scripts/check-extension-installed.js --json
node scripts/check-native-host-manifest.js --json
The checks report Chrome running, extension installed/enabled, and native host configuration correct.

In the Node REPL tool, run:
const pluginRoot = "C:/Users/Administrator/.codex/plugins/cache/openai-bundled/chrome/0.1.7";

if (!globalThis.agent) {
  const { setupAtlasRuntime } = await import(`${pluginRoot}/scripts/browser-client.mjs`);
  await setupAtlasRuntime({ globals: globalThis });
}

if (!globalThis.browser) {
  globalThis.browser = await agent.browsers.get("extension");
}

await browser.nameSession("Chrome access test");
const tabs = await browser.user.openTabs();
The command hangs until the Node REPL tool times out:
js execution timed out; kernel reset, rerun your request

**What is the expected behavior?**

```markdown
The Chrome plugin should establish the extension backend session and return the currently open Chrome tabs via:

```js
const tabs = await browser.user.openTabs();
After that, normal Chrome browser automation should be available.


**Additional information**

```markdown
Bundled setup checks pass.

`node scripts/chrome-is-running.js --json` reports:

```json
{
  "platform": "win32",
  "running": true
}
node scripts/check-extension-installed.js --json reports:

{
  "extensionId": "hehggadaopoacecdllhhajmbjkdcmajg",
  "preferencesPath": "C:\\Users\\Administrator\\AppData\\Local\\Google\\Chrome\\User Data\\Default\\Secure Preferences",
  "profilePath": "C:\\Users\\Administrator\\AppData\\Local\\Google\\Chrome\\User Data\\Default",
  "installed": true,
  "registered": true,
  "enabled": true,
  "disabled": false,
  "exitCode": 0,
  "versions": ["1.1.4_0"]
}
node scripts/check-native-host-manifest.js --json reports:

{
  "manifestPath": "C:\\Users\\Administrator\\AppData\\Local\\OpenAI\\extension\\com.openai.codexextension.json",
  "registryKey": "HKCU\\Software\\Google\\Chrome\\NativeMessagingHosts\\com.openai.codexextension",
  "registryManifestPath": "C:\\Users\\Administrator\\AppData\\Local\\OpenAI\\extension\\com.openai.codexextension.json",
  "expectedHostName": "com.openai.codexextension",
  "actualHostName": "com.openai.codexextension",
  "expectedExtensionId": "hehggadaopoacecdllhhajmbjkdcmajg",
  "expectedOrigin": "chrome-extension://hehggadaopoacecdllhhajmbjkdcmajg/",
  "allowedOrigins": [
    "chrome-extension://hehggadaopoacecdllhhajmbjkdcmajg/"
  ],
  "exists": true,
  "nameMatches": true,
  "hasExpectedOrigin": true,
  "registryMatchesManifestPath": true,
  "correct": true,
  "problem": null
}

### What is the expected behavior?

_No response_

### Additional information

_No response_

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix Codex Desktop Chrome plugin hangs during extension backend bootstrap/openTabs on Windows