openai / openai/codex

Desktop CUA: Safari approval review times out; drag/scroll report noWindowsAvailable despite readable window

Open
#45,387 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app bug computer-use tool-calls
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

Summary

Codex desktop computer use intermittently stalls on harmless, explicitly authorized Safari navigation, then native drag/scroll fails with noWindowsAvailable while accessibility snapshots and keyboard actions work.

Environment

macOS; desktop app version 26.903.71938; unified-computer-use mcp__cua_repl. Observed September 14, 2026.

Reproduction

  1. Obtain Safari with cua.getApp("com.apple.Safari").
  2. Navigate to a local development page using pressKey("super+l"), typeText("http://127.0.0.1:3002"), pressKey("Return"), then getAXState().
  3. Multiple attempts, including after explicit user authorization, take about 90 seconds and return: "The automatic permission approval review did not finish before its deadline."
  4. Splitting address-bar focus into a separate call eventually allowed navigation. Root cause is unknown; this is an observed workaround, not proof batching causes it.
  5. On the loaded page, getAXStateAndScreenshot() succeeds, semantic clicks and keyboard input work, but native app.drag([x1,y1],[x2,y2]) and app.scroll(...) return "Computer Use server error -10005: noWindowsAvailable" immediately. Raising the window using its exposed Raise action did not resolve dragging.

Expected

Authorized local navigation should complete or return an actionable error promptly. Native pointer actions should resolve the same Safari window as successful accessibility/screenshot calls.

Impact

Blocks real mouse/slider testing and repeatedly suggests user approval despite existing explicit authorization. No browser security warnings were bypassed and no approval settings were weakened.

Evidence scope

Sanitized reproduction only; no private project sources, browsing history, credentials, or session logs attached. A separate stale local production-build mismatch was fixed by restarting the preview and is not attributed to this Codex bug.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the Safari flow with cua.getApp("com.apple.Safari"), getAXState(), getAXStateAndScreenshot(), app.drag(), and app.scroll(). Compare the authorization-review timeout and noWindowsAvailable failures with the successful accessibility and keyboard actions. Done means authorized navigation completes promptly and native pointer actions resolve the same readable Safari window, or return an actionable error.

Written by the indexing model from the issue text.

Assessment

Tech stack
macos, rust
Domain
accessibility, desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.