[macOS][Computer Use] iOS Simulator Save Password prompt cannot be clicked: windowNotFoundAtPosition

[macOS][Computer Use] iOS Simulator Save Password prompt cannot be clicked: windowNotFoundAtPosition

Summary

Native computer use could not dismiss the visible Not Now button on an iOS Save Password system prompt in two of three open Simulator windows. The prompt buttons were absent from the accessibility tree returned by the tool, and screenshot-based coordinate clicks failed with Computer Use server error -10005: windowNotFoundAtPosition.

The same coordinate-click operation dismissed the prompt in the third simulator. A person could manually click the affected buttons and continue. On one affected window, the error persisted after selecting, raising, and centering the window and taking a fresh screenshot.

Environment and component scope

• Desktop host: ChatGPT app 26.901.41600, build 7982, running a Codex task.
• macOS 26.6.2, build 25G83.
• iOS Simulator runtime 26.4; Xcode app labeled 26.4.1.
• Three iPhone Simulator windows open concurrently in the same Simulator application.
• Native computer-use integration: unified-computer-use, exposed through mcp__cua_repl.js and the cua API.
• A separate computer-use backend/plugin version was not captured.

This is an observed failure of the native CUA tool path used from the desktop app. It is not yet established whether the cause is in Codex, the computer-use backend, macOS window hit-testing/coordinate conversion, or Simulator's accessibility integration. Please route to the appropriate component if this repository is not its owner.

Reproduction steps

1. Open three iPhone Simulator windows using iOS 26.4.
2. In each simulator, complete an ordinary account-registration flow using disposable test credentials, causing iOS to display its Save Password prompt.
3. Use the native computer-use integration to select the intended simulator through Simulator's Window menu.
4. Request a fresh accessibility tree. In the affected state, the tool exposes the Simulator window, hardware buttons, toolbar, and menu bar, but not the visible Save Password prompt's Not Now button.
5. Request a fresh screenshot and click Not Now using its image-relative coordinates.
6. If the click fails, raise the selected window, use Window > Center, request another screenshot, and retry the visible button.

These steps describe the observed session, not a standalone minimal repro or a measured failure rate across machines.

Expected result

The tool should be able to dismiss the visible system prompt in the selected, on-screen Simulator window, through an accessible button action or a correctly routed coordinate click.

Actual result and sanitized errors

The coordinate operation used was:

await simulator.click([151, 615]);

Here simulator is a generic name for the existing native Simulator app handle. The coordinates came from the current tool screenshot; they are not universal coordinates for other window sizes.

The same input coordinate pair succeeded for one window but produced these errors for two others:

Computer Use server error -10005: windowNotFoundAtPosition((1800.0, 1853.0))
Computer Use server error -10005: windowNotFoundAtPosition((1403.0, 791.0))

After raising and centering one affected window, a fresh screenshot still showed the prompt, but retrying returned:

Computer Use server error -10005: windowNotFoundAtPosition((1208.0, 1551.0))

The tool's fresh accessibility state identified that Simulator window as focused. Sending Escape to the other affected simulator did not dismiss its prompt. Selecting the intended window, refreshing the accessibility state/screenshot, and the raise/center retry did not resolve the failure.

Impact and workaround

The unattended UI workflow stopped at an ordinary iOS system dialog and needed human intervention. Manually clicking Not Now dismissed the affected prompts; the workflow could then continue.

Possibly related observation

In an iOS share sheet, the native accessibility tree also omitted the visible Copy action and exposed only PopoverDismissRegion plus the Simulator toolbar. A manual Copy action was needed. This has been observed on earlier runs as well, but it is not established that it has the same cause as the Save Password coordinate-click failure.

No screenshots, session transcript, credentials, account identifiers, application-under-test names, project details, local paths, or device UUIDs are included in this report.

Start by tracing the native computer-use path through mcp__cua_repl.js and the cua API, then compare accessibility-tree results with screenshot coordinate handling for multiple Simulator windows. Reproduce the Save Password prompt scenario if possible. Done means the selected on-screen Simulator prompt exposes an actionable button or accepts a correctly routed coordinate click.