Computer Use loses scrolling/input control across macOS apps

Open 💬 0 comments Opened Aug 14, 2026 by Poole33

What version of the Codex App are you using (From “About Codex” dialog)?

26.810.41047

What subscription do you have?

Plus

What platform is your computer?

macOS 26.2 (Build 25C56) Apple Silicon

What issue are you seeing?

  1. Launch the Codex desktop app and enable Computer Use.
  2. Open any application with scrollable content.
  3. Confirm that Computer Use can discover the application window and read its UI/accessibility tree.
  4. Ask Computer Use to scroll down one page.
  5. Observe that the scroll action fails with noWindowsAvailable (-10005) or times out.
  6. Remove/reconfigure Computer Use and repeat the test.
  7. The action may work briefly, then fail again after several interactions.

What steps can reproduce the bug?

| Target | What still works | What fails |
| --- | --- | --- |
| iPhone Mirroring | Window discovery and screen capture | Click/scroll may return noWindowsAvailable (-10005) |
| Google Chrome | Tab discovery (title and URL) | Claiming a tab, screenshots, and scrolling can time out |
| WPS Office | Accessibility tree and native scrollbars are visible | Scrolling an identified scrollbar returns noWindowsAvailable (-10005) |

The WPS Office reproduction is significant because it is a regular native macOS application, which suggests that this is not specific to iPhone Mirroring or a particular web page.

What is the expected behavior?

Once Computer Use has successfully discovered a target window, it should send scroll events to that window. If the underlying window reference becomes stale, the control layer should rediscover and rebind to the active window automatically.

Actual behavior

The read path and input path become inconsistent:

  • Window discovery, screenshots, and accessibility-tree reads continue to work.
  • Scroll/click actions fail with noWindowsAvailable (-10005) or time out.
  • The issue affects multiple unrelated applications, not just one page or app.

Additional information

_No response_

View original on GitHub ↗