[BUG] Codex Chrome plugin times out: extension socket getInfo/getUserTabs succeed, but setupAtlasRuntime hangs

Open 💬 1 comment Opened May 11, 2026 by 7824s484yf-design

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

26.506.31421 (2620)

What subscription do you have?

ChatGPT Plus

What platform is your computer?

25.4.0 arm64 arm

What issue are you seeing?

Environment

  • macOS
  • Codex Desktop App: 26.506.31421
  • Chrome: 147.0.7727.139
  • Codex Chrome Extension: 1.1.4
  • Chrome extension ID: hehggadaopoacecdllhhajmbjkdcmajg

Problem

The Codex Chrome plugin channel consistently times out. Reinstalling the Chrome plugin and reinstalling/restarting Codex did not fix it.

The Chrome extension and native host appear to be installed correctly, and the low-level socket responds, but Codex's official browser runtime initialization hangs.

What I tried

  • Reinstalled the Codex Chrome plugin from Codex plugin UI
  • Reinstalled/restarted Codex Desktop App
  • Restarted Chrome
  • Opened Chrome with the Default profile
  • Restarted the Chrome extension host process
  • Verified native host manifest
  • Verified extension is installed and enabled

Diagnostics

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

  • installed: true
  • registered: true
  • enabled: true
  • version: 1.1.4_0

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

  • exists: true
  • nameMatches: true
  • hasExpectedOrigin: true
  • correct: true

Low-level socket calls succeed:

  • getInfo returns Chrome extension info:
  • name: Chrome
  • version: 1.1.4
  • type: extension
  • getUserTabs returns Chrome tabs successfully.

But this official initialization path still times out:

const { setupAtlasRuntime } = await import('/Users/a1010/.codex/plugins/cache/openai-bundled/chrome/0.1.7/scripts/browser-client.mjs');
await setupAtlasRuntime({ globals: globalThis });


### What steps can reproduce the bug?

## Environment

- macOS
- Codex Desktop App: 26.506.31421
- Chrome: 147.0.7727.139
- Codex Chrome Extension: 1.1.4
- Chrome extension ID: hehggadaopoacecdllhhajmbjkdcmajg

## Problem

The Codex Chrome plugin channel consistently times out. Reinstalling the Chrome plugin and reinstalling/restarting Codex did not fix it.

The Chrome extension and native host appear to be installed correctly, and the low-level socket responds, but Codex's official browser runtime initialization hangs.

## What I tried

- Reinstalled the Codex Chrome plugin from Codex plugin UI
- Reinstalled/restarted Codex Desktop App
- Restarted Chrome
- Opened Chrome with the Default profile
- Restarted the Chrome extension host process
- Verified native host manifest
- Verified extension is installed and enabled

## Diagnostics

`check-extension-installed.js --json` reports:
- installed: true
- registered: true
- enabled: true
- version: 1.1.4_0

`check-native-host-manifest.js --json` reports:
- exists: true
- nameMatches: true
- hasExpectedOrigin: true
- correct: true

Low-level socket calls succeed:
- `getInfo` returns Chrome extension info:
  - name: Chrome
  - version: 1.1.4
  - type: extension
- `getUserTabs` returns Chrome tabs successfully.

But this official initialization path still times out:

```js
const { setupAtlasRuntime } = await import('/Users/a1010/.codex/plugins/cache/openai-bundled/chrome/0.1.7/scripts/browser-client.mjs');
await setupAtlasRuntime({ globals: globalThis });


### What is the expected behavior?

_No response_

### Additional information

_No response_

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗