Windows Codex CLI Computer Use cannot determine Chrome URL after Chrome Browser Use confirms active NAVER tab

Summary

On Windows, Codex CLI Computer Use can initialize its standalone @oai/sky
helper and discover the active Chrome window, but the first read-only
get_window_state request terminates the turn because it cannot determine the
current browser URL. In the same fresh Codex session, Chrome Browser Use can
open the same URL, confirm its final origin, inspect its DOM, and identify the
active tab successfully.

This is a current CLI/standalone-helper reproduction of the URL-detection
failure reported in #25271 and recently observed again in #40048.

Environment

• Windows NT 10.0.26200 x64
• Codex CLI 0.149.1
• Codex app package 26.818.8289.0 (installed, status OK; not required to stay open)
• Bundled Chrome and Computer Use plugins 26.818.61809
• @oai/sky 0.6.17-202608171537-pr-1300023-7efba775c041
• Google Chrome 151.0.7922.170
• Codex Chrome extension 1.2.27268.51612_0, installed and enabled
• ChatGPT Pro

Reproduction

1. Start a fresh normal Codex CLI session with the standalone Computer Use

configuration (SKY_CUA_NATIVE_PIPE=0).

1. Run the Browser Use runtime preflight. It exits 0.
2. Through the bundled Chrome Browser Use plugin, select Chrome and call the

real openTabs() RPC. It succeeds.

1. Create one disposable controlled tab and navigate to

https://www.naver.com/.

1. Confirm through Chrome Browser Use that:

• the final origin is exactly https://www.naver.com;
• the title is NAVER;
• recognizable Naver search/logo DOM elements are present;
• the disposable tab is active.

1. Initialize Computer Use normally with await import("@oai/sky").
2. Call list_apps()/list_windows(). Computer Use successfully returns one

targetable NAVER - Chrome window.

1. Call exactly one read-only get_window_state request for that returned

window, with screenshot capture and no click, typing, keypress, scroll,
activation, or retry.

Actual result

The read-only state request fails 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. Stop your work and send a final message noting why Computer Use ended.

The standalone helper connection and window discovery both succeeded. No input
action occurred. The disposable test tab was then closed through its original
Chrome Browser Use binding.

Expected result

Computer Use should obtain enough URL evidence to enforce policy and return the
read-only window state. When the bundled Chrome extension/Browser Use binding
already knows the active controlled tab and its final URL, the Windows Computer
Use URL check should be able to correlate that trusted tab information with the
target Chrome window instead of terminating before capture.

Notes

• This is not a Naver origin denial: Chrome Browser Use navigated to and

inspected the origin successfully in the same test.

• This is not a missing native pipe: standalone @oai/sky initialization and

Chrome window discovery both succeeded.

• Restarting Codex or Chrome is not a reliable remedy; the failure occurs in a

fresh CLI session after a clean preflight.