Codex on Windows: Native Computer Use stops because it cannot determine Chrome’s current URL

Hello OpenAI Support,

I am reporting a reproducible issue with native Windows Computer Use in the Codex desktop app. It detects the official Google Chrome window but stops when attempting to inspect it.

Environment:

• Windows 11
• Codex MSIX package version: 26.901.6511.0
• Official Google Chrome: 152.0.7977.82
• ChatGPT Chrome extension: 1.26.901.11451, installed and enabled
• Computer Use/browser plugin version: 26.901.51231
• @oai/sky: 0.6.26
• Reproduced on September 9, 2026

Steps to reproduce:

1. Enable Computer Use and Chrome control in Codex.
2. Open official Google Chrome and navigate to example.com or YouTube.
3. Ask Codex to inspect or operate Chrome through native Windows Computer Use.
4. Chrome is successfully detected by sky.list_apps(), and get_window succeeds.
5. Calling get_window_state with include_screenshot: false and include_text: true stops Computer Use with this message:

“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.”

Expected:
Codex should reliably identify the current URL in supported Chrome and continue permitted browser operations.

Actual:
Native Computer Use repeatedly stops at window inspection. This occurred on multiple websites and persisted after restarting Chrome and Codex. Manually focusing Chrome’s address bar with Ctrl+L did not resolve it.

Diagnostic findings:

• Chrome extension-based control successfully opened YouTube, entered a search, clicked Search, and read result titles and links.
• Codex’s built-in browser also completed that search workflow.
• Native desktop control successfully operated Studio Pro, including creating and saving an empty project.
• Read-only checks of the Chrome native messaging host manifest and current-user registration passed.

These results suggest the failure may involve URL detection in the native Windows browser-control path, but the root cause has not been established. Similar functionality worked for me in older versions; I do not know which update introduced this issue.

Please investigate and advise which Codex diagnostic logs or session identifiers would help isolate the failure.

Start with the native Windows Computer Use path around sky.list_apps(), get_window, and get_window_state, using the reported Chrome and Codex versions as reproduction context. Determine why the current Chrome URL cannot be identified with sufficient confidence and document the diagnostic logs or session identifiers needed; done means supported Chrome inspection no longer stops unexpectedly.