Repository navigation
Windows Computer Use: screenshot capture timeout and coordinate input geometry unavailable #49680
Description
Summary
Windows Computer Use can discover application windows and read accessibility text, but screenshot capture times out and clicks fail because input geometry is unavailable. This blocks operating native Windows applications.
Environment
- Windows desktop app
- Computer Use plugin: 26.928.20755
- Target apps: Soften SIEM Rev.0015 and Microsoft Outlook
- Reproduced on September 29 and 30, 2026
- Feedback ID: 01a0cfd1-7ba2-79e1-a1e2-6d69c9ffa369
- Desktop app version and Windows build: not yet collected
Reproduction
- Open a native Windows application.
- Use Computer Use to list applications/windows: this succeeds.
- Read the Soften window accessibility text without a screenshot: this succeeds.
- Request a screenshot of the window: this fails.
- Refresh the window list, reacquire and activate the window, then retry capture: this still fails.
- Try clicking the visible/accessibility-listed Filtrar button: this fails.
Observed errors
Screenshot capture:
FrameArrived timed out: timed out waiting on channel
window capture timed out: timed out waiting on channel
Click:
coordinate input geometry is unavailable
Screenshot capture also failed in Outlook on September 29. Resetting the tool session and retrying did not resolve it. No invoice was changed by the failed click test.
Expected behavior
Capture the selected native application window and click its controls.
Additional context
The cause is unknown. Because capture also failed in Outlook, the observations are not limited to Soften. No private invoices, customer information, credentials, screenshots or raw logs are attached.
Activity
github-actions commentedon Sep 30, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
angelcamach0 commentedon Oct 3, 2026
I can reproduce the same symptoms on Windows with Spotify and another desktop application.
FrameArrived timed out: timed out waiting on channelorwindow capture timed out: timed out waiting on channel.coordinate input geometry is unavailable.The issue affects multiple applications. The native helper was not instrumented, so I cannot confirm the underlying cause. No experimental patch or system-setting change was applied.
afonseca08 commentedon Oct 7, 2026
Reproduced on October 6, 2026 in Brave on Windows 10 Home 22H2, build 19045.7725, using Computer Use plugin 26.930.61225 and the supported @oai/sky Node REPL. Desktop app and Brave versions were not independently collected.
In a fresh JavaScript session, window enumeration and accessibility-only state reads succeeded. The Google Analytics exploration list exposed the requested exploration as element 112. Clicking that observed element failed with
coordinate input geometry is unavailable. An immediate accessibility refresh confirmed the list remained open.Screenshot-only capture then failed with
FrameArrived timed out: timed out waiting on channel. After rediscovering, reacquiring, activating and reacquiring the window again, one retry failed withwindow capture timed out: timed out waiting on channel. No screenshot was returned. This reproduces all three error messages in this issue in a browser window. Related Windows 10 capture report: #51245.afonseca08 commentedon Oct 8, 2026
Follow-up to my October 6 reproduction: screenshot capture still fails on October 7, 2026, with the newer Computer Use plugin 26.1002.52244 (previously 26.930.61225). The current Codex desktop app reports version 26.1002.52244, build 13536, production channel; its updater reports up to date.
Environment remains Windows 10 Home 22H2, build 19045.7725. This time the target was a newly launched blank Notepad window, using the supported
@oai/skyNode REPL.Runtime initialization, app/window enumeration, and Notepad launch succeeded.
sky.get_window_state({window, include_screenshot:true, include_text:true})failed withFrameArrived timed out: timed out waiting on channel. After refreshing window discovery, reacquiring the returned Notepad window, and activating it, the same capture request failed withwindow capture timed out: timed out waiting on channel.No screenshot was returned. Clicking, typing, and accessibility-only reads were not tested in this run, so this update confirms persistence of the capture failures only. It adds a native Notepad reproduction to my previous Brave reproduction. Related: #51245.
leszek1985 commentedon Oct 14, 2026
Reproduced on Windows 10 with desktop app 26.1007.71326, build 20398, production channel. The updater reports up to date. GPUs: Intel HD Graphics 4600 and NVIDIA Quadro K4100M.
Window discovery and accessibility-only reads in File Explorer succeed. Screenshot capture repeatedly fails with
FrameArrived timed out: timed out waiting on channelandwindow capture timed out: timed out waiting on channel. Clicking an accessibility-listed element also failed withcoordinate input geometry is unavailable.Restarting Windows and the app did not resolve the issue. Assigning both codex-computer-use.exe and codex-computer-use-swift.exe to the power-saving Intel GPU, followed by restarting the app, also did not resolve it. No root cause has been confirmed.
Llh320 commentedon Oct 15, 2026
I can reproduce the same native Windows capture failure.
01a13dd3-1edf-7ad1-9b41-e690bdf0a7d3get_window_state(..., include_screenshot: true)fails with:FrameArrived timed out: timed out waiting on channelI tested both legacy Windows sandbox implementations:
sandbox = "elevated": failssandbox = "unelevated": fails with the same errorI also performed a desktop app Reset and an official desktop-app uninstall/reinstall. The behavior did not change.
CODEX_HOMEis unset at process, user, and machine scope.Additional logging observation:
%USERPROFILE%\.codex\.sandbox\sandbox.logdoes not exist.sandbox.2026-10-15.log, last modified at2026-10-15 17:08:55 +08:00.get_window_statefailure occurred later, at2026-10-15 18:55:33 +08:00, so the available sandbox log did not cover the failure event.This appears consistent with the issue symptoms, but I am not asserting a root cause.