Windows Computer Use cannot determine the current Microsoft Edge 151 URL on Windows 11
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
Environment
- ChatGPT/Codex desktop:
26.908.9136.0 - Windows Computer Use JS package:
@oai/sky 0.6.32 - Windows 11:
25H2, build26200.9457 - Microsoft Edge:
151.0.4129.107
Actual behavior
When the official Windows Computer Use API targets the unique live Edge window and calls get_window_state, the turn stops 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.
Minimal reproduction
- Open
https://example.com/in Microsoft Edge. - Use
sky.list_windows()and select the single returnedMSEdgewindow. - Rehydrate that exact returned window with
sky.get_window(), activate it, and callsky.get_window_state({ window, include_screenshot: true, include_text: true }). - The URL-confidence error occurs before any screenshot or input can proceed.
Expected behavior
Computer Use should confirm the visible HTTPS URL and return the Edge window state while preserving the URL safety check.
Diagnostics completed
- Windows UI Automation reads the full visible HTTPS URL from Edge's omnibox (
AutomationId: view_1021,ClassName: OmniboxViewViews). - The visible
RootWebAreaURL matches the omnibox URL. - The failure also reproduces on
example.com, so page iframes are not the cause. - It reproduces with the Computer Use locale set to both
zh-CNanden-US; the original setting was restored. - Codex restart, fresh native pipe, fresh JavaScript sessions, and fresh live-window enumeration do not resolve it.
- Installed Computer Use binaries and JS client match the current official Codex package.
- The Edge browser-extension control path works, but it is a separate path and does not repair Windows Computer Use URL recognition.
Impact
Windows Computer Use cannot control Edge on this machine, including a simple search and page translation. Other Windows desktop-app control works, so the failure is isolated to browser URL recognition.
Reproduction identifiers
- Codex session ID:
01a08c3f-613e-71a0-be3e-4d78e18248c2 - Reproduction turn ID:
01a0ab16-9e50-7d93-a300-c89f3f8b33d8
A redacted diagnostic PDF containing exact reproduction events, environment details, sandbox-log evidence, and source hashes was already submitted privately through OpenAI Support. It can be provided privately to the engineering team if needed.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure with sky.list_windows(), sky.get_window(), and sky.get_window_state() against the live Edge window. Trace the Windows URL-confidence path and compare its result with the UI Automation omnibox and RootWebArea URLs described here. Done means get_window_state returns the validated HTTPS URL and state without bypassing the URL safety check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, rust
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100