macOS Remote Control fails security requirements — CUAService app-group entitlement mismatches provisioning profile
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
Summary
ChatGPT Remote Control on macOS fails during:
Settings → Connections → Remote → Control this Mac → Get started
with:
Couldn't check security requirements. Try again.
The underlying Codex Computer Use (CUA) service launches, but macOS rejects its application-group entitlement because the signed entitlement and embedded provisioning profile do not match.
Environment
- ChatGPT macOS: 26.908.40834 (build 8881)
- macOS: 26.5.2 (25F84)
- Architecture: arm64
- MDM enrollment: No
- DEP enrollment: No
- FileVault: On
- SIP: Enabled
- Gatekeeper assessments: Enabled
- Secure Token: Enabled
Affected helper:
~/.codex/computer-use/Codex Computer Use.app
Bundle identifier: com.openai.sky.CUAService
Team identifier: 2DC432GLL2
Signing authority: Developer ID Application: OpenAI OpCo, LLC (2DC432GLL2)
Reproduction
- Open ChatGPT for macOS.
- Go to Settings → Connections → Remote.
- Select Control this Mac.
- Select Connect a device to this Mac.
- Click Get started.
- ChatGPT reports
Couldn't check security requirements. Try again.
Findings
The CUA service launches from:
~/.codex/computer-use/Codex Computer Use.app/Contents/MacOS/SkyComputerUseService
codesign --verify --deep --strict succeeds with valid on disk and satisfies its Designated Requirement.
However, the app's signed entitlements contain:
com.apple.security.application-groups =
2DC432GLL2.com.openai.sky.CUAService
while its embedded provisioning profile authorizes:
com.apple.security.application-groups =
group.com.openai.sky.CUAService
2DC432GLL2.*
macOS trustd repeatedly reports:
Entitlement com.apple.security.application-groups=(
"2DC432GLL2.com.openai.codex.notifications",
"2DC432GLL2.com.openai.sky.CUAService"
) is ignored because of invalid application signature or incorrect provisioning profile
The application-group identifier requested by the signed executable therefore appears not to match the explicitly provisioned application group.
Downstream failure
After the entitlement rejection, ChatGPT logs:
RemoteHostedPIPContent CUAService bootstrap failed:
Error Domain=NSOSStatusErrorDomain Code=-1712
LaunchServices sees the running CUA application at ~/.codex/computer-use/Codex Computer Use.app, with CFBundleIdentifier = com.openai.sky.CUAService and CFBundleExecutable = SkyComputerUseService.
Troubleshooting already performed
- Tested another network / mobile hotspot
- Verified FileVault, SIP, Gatekeeper and Secure Token
- Verified nested CUA app signatures with
codesign - Checked quarantine attributes
- Re-registered bundled CUA components with LaunchServices
- Restarted LaunchServices
- Launched the bundled Computer Use helper/installer directly
- Confirmed
SkyComputerUseServiceactually launches
The problem persists.
Suspected cause
This appears to be a signing/provisioning issue in the distributed Codex Computer Use bundle.
Specifically:
- Signed entitlement:
2DC432GLL2.com.openai.sky.CUAService - Provisioning profile:
group.com.openai.sky.CUAService
macOS consequently rejects/ignores the application-group entitlement, after which CUA bootstrap times out.
Could you confirm whether the CUAService entitlement or provisioning profile in the current macOS build is incorrect?
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
Start with ~/.codex/computer-use/Codex Computer Use.app and reproduce the Control this Mac flow. Inspect the signed entitlements and embedded provisioning profile for com.openai.sky.CUAService, using the codesign findings in the report as a baseline. Done means the application-group values agree and the CUA service bootstraps without the security-requirements or timeout error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos
- Domain
- desktop, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100