Windows Codex Chrome/Computer Use browser control fails: about:blank, JS kernel timeout, and URL detection failure

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

26.818.3698.0

What subscription do you have?

ChatGPT Pro

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

Browser automation is broken on Windows in multiple Codex control modes.

Environment:

• Windows 11 x64
• Codex/ChatGPT app: 26.818.3698.0
• Feedback ID: no-active-thread-01a0271f-cb67-7373-8c80-6bcb446c05fd

Reproduction / observed behavior:

1. Chrome plugin

• example.com can be read, clicked, and navigated successfully.
• On duolie.com, manually opened pages remain stable when Codex is not controlling them.
• After Codex claims the Chrome tab, with no click, refresh, navigation, DOM read, or JavaScript execution, the tab becomes about:blank after approximately 20–30 seconds.
• This reproduces on:
  • https://www.duolie.com/home
  • https://www.duolie.com/login
  • /newtalent/talentlist pages

2. Computer Use

• Tested with both Chrome and Microsoft Edge.
• Computer Use stops immediately with:
  "Computer Use has been stopped for this turn because it could not determine the current browser URL on Windows with enough confidence to enforce policy."

3. Built-in Browser

• example.com renders normally.
• Attempting to click the "Learn more" link fails with:
  "js execution timed out; kernel reset, rerun your request"

4. Previous stale-version issue found and fixed

• chrome-native-hosts-v2.json contained a stale resourcesPath pointing to OpenAI.Codex_26.818.2872.0.
• The stale cache was backed up and regenerated.
• The regenerated cache correctly points to 26.818.3698.0.
• Current Appx package status is OK.
• The current 26.818.3698.0 installation contains npm/index.js and the undici module.
• Chrome plugin navigation on example.com works after this fix.

Expected:
Codex should be able to control Chrome, Computer Use, and the built-in browser reliably on Windows without tabs becoming about:blank, URL-detection failures, or JS execution kernel resets.

Actual:
All three browser-control paths have separate failures as described above.

What steps can reproduce the bug?

Feedback ID: no-active-thread-01a0271f-cb67-7373-8c80-6bcb446c05fd

What is the expected behavior?

Codex should reliably control supported browsers on Windows.

Expected behavior:

1. The Chrome plugin should keep claimed tabs stable and should not cause tabs to become about:blank.
2. Computer Use should be able to identify the current browser URL in Chrome and Microsoft Edge on Windows and continue the task.
3. The built-in browser should be able to click and navigate on a simple page such as example.com without the JavaScript execution kernel timing out.
4. Browser control should continue working after the Codex app updates without stale runtime paths referencing an older app version.

Additional information

This issue has been reproduced repeatedly after restarting Windows and repairing the ChatGPT/Codex app.

Important diagnostic findings:

• Current installed Appx package:
  OpenAI.Codex 26.818.3698.0
  Status: OK

• A stale local browser cache previously referenced:
  OpenAI.Codex_26.818.2872.0

• The stale chrome-native-hosts-v2.json file was backed up and regenerated.

• The regenerated cache now contains 26.818.3698.0 and no longer contains 26.818.2872.0.

• Chrome native messaging host exists and is valid.

• Current npm/index.js exists.

• Current node_modules/undici and undici/package.json both exist.

After fixing the stale path:

• Chrome control works correctly on example.com.
• The remaining failures described in this issue still reproduce.

The duolie.com about:blank behavior was tested without clicking, DOM reads, JavaScript execution, refresh, or navigation:

• /newtalent/talentlist -> about:blank after ~20 seconds
• /home -> about:blank after ~20 seconds
• /login -> about:blank after ~30 seconds
• The same pages remain stable when Codex is not controlling the tab.

No sensitive user data or site content is included in this report.

Start by reproducing the three Windows failures across Chrome plugin, Computer Use, and the built-in browser, then inspect chrome-native-hosts-v2.json, npm/index.js, and the installed undici module. Compare behavior with and without Codex control and verify whether the failures share a browser-control or runtime-path cause. Done means stable claimed tabs, reliable URL detection, successful example.com interaction, and no stale-version regression.