[macOS Intel] Unable to enable “Locked use”: managed Computer Use service fails to spawn
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What version of the Codex App are you using (From “About Codex” dialog)?
26.814.41957 (6744)
What subscription do you have?
ChatGPT Plus
What platform is your computer?
Darwin 23.6.0 x86_64 i386
What issue are you seeing?
Summary
Enabling Settings → Computer use → Locked use immediately turns the setting back off and displays the following error:
Unable to update “Locked use” setting.
The regular Google Chrome and Microsoft Excel controls can be enabled successfully.
Environment
- Codex App: 26.814.41957 (6744)
- macOS: 14.8.5
- Kernel/architecture: Darwin 23.6.0, Intel x86_64
- MDM enrollment: No
Steps to reproduce
- Open the Codex/ChatGPT desktop app.
- Go to Settings → Computer use.
- Enable Locked use.
- Observe that the toggle returns to the disabled state and an error message appears.
Expected behavior
Locked use should be enabled, and the required macOS authorization component should be installed and started.
Actual behavior
The setting is not saved, and no managed Computer Use service is started.
Diagnostics
The Codex desktop log reports:
Failed to reconcile managed Computer Use service: Failed to spawn managed Computer Use service
The macOS unified log reports:
AMFI: constraint violation: sky.node has entitlements but is not a main binary
It also reports that the following application-group entitlement is ignored:
2DC432GLL2.com.openai.sky.CUAService
An XPC bootstrap lookup subsequently fails with:
No such process
The main application and sky.node both pass code-signature verification, and the application is notarized. No corresponding managed Computer Use service process is running.
Additional context
This appears to be a packaging or compatibility issue affecting the native Computer Use component on Intel macOS Sonoma. The failure happens while spawning the managed Computer Use service, before the Locked use setting can be enabled.
What steps can reproduce the bug?
see up
What is the expected behavior?
No response
Additional information
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce from Settings → Computer use → Locked use on Intel macOS Sonoma, then inspect the managed Computer Use service reconciliation and spawn path. Start with the Codex desktop log and macOS unified log entries for the AMFI entitlement violation and failed XPC bootstrap lookup. Done means the service starts successfully and Locked use remains enabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100