[macOS] Computer Use times out after ~5 seconds when accessing Xcode 27 Device Hub (-10005: timeoutReached)

Summary

Computer Use cannot access Xcode 27's Device Hub (com.apple.dt.Devices). Calling cua.getApp("com.apple.dt.Devices") fails after approximately five seconds with:

Computer Use server error -10005: timeoutReached

Finder can be read successfully both before and immediately after the Device Hub timeout in the same Computer Use session. This blocks using Computer Use to inspect and interact with Device Hub during iOS development.

Environment

• ChatGPT desktop app, Codex task: 26.901.51231 (build 8109, bundle ID com.openai.codex)
• Unified Computer Use plugin installed: 26.901.51231
• Computer Use plugin installed: 1.0.1000926
• macOS: 27.0 (build 26A5425a), Apple Silicon / arm64
• Selected Xcode: 27.0 (build 27A5252f, Xcode-beta.app)
• Device Hub: 27.0 (build 255.2.3.5, bundle ID com.apple.dt.Devices)
• Reproduced on September 7, 2026

Steps to reproduce

In a Codex desktop task with Computer Use available, run these calls sequentially in the same persistent cua_repl session:

const finder = await cua.getApp("com.apple.finder");

This succeeds and returns Finder's accessibility state.

await cua.getApp("com.apple.dt.Devices");

This fails with Computer Use server error -10005: timeoutReached.

Then check Finder again using the existing binding:

await finder.getAXState({ emit: false });

Finder still succeeds.

Observed results

Operation	Result	Measured duration
Initial Finder getApp	Success; accessibility state returned	Not separately instrumented
Device Hub getApp	-10005: timeoutReached	5,069 ms
Finder getAXState immediately afterward	Success; nonempty state returned	298 ms

Earlier attempts to access Device Hub also repeatedly timed out at approximately five seconds. The timings above are from one explicitly measured Finder / Device Hub / Finder comparison.

Expected behavior

Computer Use should return Device Hub's application state and allow subsequent UI interaction. If this target is unsupported or a specific part of state collection fails, an actionable diagnostic would be more useful than a generic five-second timeout.

Scope of diagnosis

The successful Finder control checks show that Computer Use is not globally unavailable in this session. They do not establish why Device Hub times out. No root cause, helper crash, or specific Accessibility/window-capture failure is claimed; those remain to be investigated.

Related reports

• #41914: the same -10005: timeoutReached message after about 5.1 seconds for Citrix Viewer, while Finder works.
• #32284: roughly five-second timeoutReached errors for other macOS app targets.

These are similar symptoms in different targets, not confirmed duplicates or evidence of a shared root cause.

Start by reproducing the sequential cua.getApp calls in a persistent cua_repl session, comparing Device Hub with Finder and reviewing related issues #41914 and #32284. Done means identifying why Device Hub reaches the five-second timeout or providing an actionable diagnostic when the target cannot be accessed.