Computer Use service fails to start on macOS 13.7.6 #42222

Activity

1. winter671

   added

   appIssues related to the Codex desktop appIssues related to the Codex desktop app

   on Sep 2, 2026
2. github-actions

   added

   bugSomething isn't workingSomething isn't working

   computer-use

   on Sep 2, 2026
3. github-actions commented on Sep 2, 2026

   

   github-actionsBot

   on Sep 2, 2026 – with GitHub Actions

   Contributor

   More actions

   Potential duplicates detected. Please review them and close your issue if it is a duplicate.

   • [macOS] Computer Use crashes in node_repl with sandbox_apply error (exit 71); direct MCP works #41651

   Powered by Codex Action
4. blaketairan commented on Sep 8, 2026

   

   blaketairan

   on Sep 8, 2026 – with ChatGPT Codex Connector

   More actions

   I am seeing a similar native Computer Use failure on an Intel Mac running macOS 15.7.7. I also have a separate Chrome automation problem, described below; I have not established that the two failures share a cause.

   Environment

   • Mac mini (2018), model identifier Macmini8,1
   • Intel Core i7, 3.2 GHz, 6 cores; x86_64
   • macOS Sequoia 15.7.7, build 24G720
   • ChatGPT/Codex desktop app: initially 26.901.41123, subsequently 26.901.51231
   • Google Chrome: 152.0.7977.76
   • Chrome and unified-computer-use bundled plugins: 26.901.51231 after updating

   1. Native Computer Use: service executable missing

   The “Any App” entry is not available in my Computer Use settings, and the agent cannot discover or control native macOS applications.

   Application logs repeatedly reported:

   [managed-computer-use-service] Failed to spawn managed service isRespawn=false
   Failed to reconcile managed Computer Use service
   computerUseEnabled=true
   errorMessage="Failed to spawn managed Computer Use service"
   

   These errors were present before removing the plugin cache and remained after it was restored. The unified-computer-use plugin configuration and resources were downloaded again successfully.

   However, neither of the expected service bundles exists on this installation:

   ~/.codex/computer-use/Codex Computer Use.app
   /Applications/ChatGPT.app/Contents/Resources/cua_node/lib/node_modules/@oai/sky/Codex Computer Use.app
   

   Consequently, Contents/MacOS/SkyComputerUseService is missing at both locations. I rechecked these paths with desktop app 26.901.51231 on September 9, 2026.

   This looks similar to #42514. Could you confirm whether native Computer Use is supported on Intel Macs and whether the x86_64 package should include this service? The evidence currently establishes missing files and startup failure; it does not establish whether the underlying cause is packaging, architecture support, or a separate compatibility issue.

   2. Separate observation: Chrome connects, but external-page content access times out

   During tests on September 7–8, the Chrome extension could connect and list tabs and their URLs. A new https://example.com/ tab was actually opened, but the operation timed out while returning its page state. Attempts to read an existing external page, obtain a DOM snapshot, or capture a screenshot also timed out. Tested call limits ranged from 20 to 55 seconds. One longer attempt returned Debugger unattached.

   In contrast, a local page at http://127.0.0.1:8777/ was readable and controllable: opening its details dialog, reading the result, and closing the dialog all succeeded. This was verified again after reinstalling the extension and plugin on September 8.

   Steps tried without resolving external-page access:

   • Quit and reopen Chrome.
   • Quit and reopen the desktop app, including updating to 26.901.51231.
   • Disable and re-enable the ChatGPT Chrome extension.
   • Reinstall the Codex Chrome plugin and the ChatGPT Chrome extension through the normal installation flow.
   • Verify the native-messaging manifest: the supplied diagnostic returned correct: true with no reported problem after reinstalling.
   • Test fresh tabs as well as existing tabs.

   Expected: the agent should be able to read and interact with permitted external pages, just as it can with the local page.

   Actual: tab discovery works, but external-page content access stalls. I cannot yet tell whether this is a debugger/session issue, a website-access-check/network issue, or another bug. Please let me know if this Chrome behavior should be tracked in a separate issue and which diagnostics would help.

   Personal paths and unrelated browsing/account information have been omitted from this report.