Forumics logo Forumics
Issue 01

Back to issue

All Codex known issues

CLAIM C170 Supported 2026-11-20

GitHub issue #53321 in openai/codex, opened 2026-10-12 by wangbaibaihanbao-star, records a report that Computer Use on Windows 10 can enumerate WeChat and QQ windows and read accessibility text, but window screenshot capture repeatedly times out with FrameArrived timed out and window capture timed out, and clicking a freshly observed accessibility element fails because coordinate input geometry is unavailable; the blocked workflow is navigating chat history; the report states the first failing version and root cause have not been established, and that an earlier sandbox startup file-lock error is not asserted to have the same cause.

Verbatim Excerpts from Cited Records
“Computer Use on Windows can enumerate WeChat and QQ windows and read accessibility text, including currently displayed messages and file names, but window screenshot capture repeatedly times out. Clicking a freshly observed accessibility element also fails because capture geometry is unavailable. This blocks a desktop workflow that requires navigating chat history.”
— wangbaibaihanbao-star · openai/codex (issue 53321 opening body, Summary section) · 2026-10-12T09:03:28Z ·GitHub Issue ↗
“FrameArrived timed out: timed out waiting on channel window capture timed out: timed out waiting on channel”
— wangbaibaihanbao-star · openai/codex (issue 53321 opening body, Actual behavior section) · 2026-10-12T09:03:28Z ·GitHub Issue ↗
“coordinate input geometry is unavailable”
— wangbaibaihanbao-star · openai/codex (issue 53321 opening body, Actual behavior section) · 2026-10-12T09:03:28Z ·GitHub Issue ↗
“The user reports that this desktop workflow previously worked. The first failing version and root cause have not been established. An earlier sandbox startup/file-lock error was observed, but command execution now works and the ongoing capture failure remains; these are not asserted to have the same cause.”
— wangbaibaihanbao-star · openai/codex (issue 53321 opening body, closing note after Troubleshooting section) · 2026-10-12T09:03:28Z ·GitHub Issue ↗
Counter-record: Issue open as of the fetch; 26 comments were read. github-actions[bot] flagged potential duplicates 52754, 53120, 53145, 53252 and 52993. The other 25 comments are all follow-ups by the author from 2026-10-12 to 2026-11-19 reporting capture still times out and asking for maintainer acknowledgment, the primary tracking issue, and a supported workaround or fix release. Related issue 35446 has November 5 and November 16 reproductions on Sky 0.7.17 and desktop 26.1111.21308. No maintainer response or assigned owner appears in the surveyed thread. The claim documents only the original report, not a verified current state. Falsification probe: If GitHub issue #53321 is deleted without archive, if the author edits the opening body so the quoted sentences no longer match verbatim, or if the author posts a retraction of the report, this claim drops to Withdrawn. Audit verification: Verified 100% continuous verbatim substring against official GitHub REST API by scripts/verify_claim_verbatim.py.

See also: Codex vs Cursor head-to-head comparison on 9bests