[macOS][Remote Control] Paired Mac host never registers AppServerManager; CUAService bootstrap times out (-1712)

What version of the Codex App are you using?

Not captured for this report.

What subscription do you have?

Not relevant to the observed client-side routing failure.

What platform is your computer?

Two separate Macs running ChatGPT/Codex Desktop.

What issue are you seeing?

Mac-to-Mac Remote Control can show a paired host as connected on both sides, while the controlling Mac cannot route any task message to that host. Every target task remains unavailable, and sending even a harmless message to an unrelated remote task fails immediately with:

No AppServerManager registered for hostId: remote-control:<redacted>

The failure is reproducible across multiple remote tasks. This is not an SSH remote-project setup.

On the controlling Mac, a fresh desktop launch produced the following sanitized sequence:

RemoteHostedPIPContent started private endpoint host
RemoteHostedPIPContent connected to CUAService
... approximately 31 seconds later ...
CUAService bootstrap failed: Error Domain=NSOSStatusErrorDomain Code=-1712

The CUAService bootstrap failure is observed alongside the missing AppServerManager registration; this report does not claim that it is the cause.

What steps can reproduce the bug?

1. Start ChatGPT/Codex Desktop on two Macs.
2. Pair the Macs through Settings > Connections > Control other devices and verify both UIs report the connection as connected.
3. From the controlling Mac, send any harmless message to any remote Codex task.
4. Observe that the task is unavailable and the send fails immediately with No AppServerManager registered for hostId: remote-control:<redacted>.

What is the expected behavior?

Once the host is paired and shown as connected, the controlling desktop app should register an AppServerManager for that remote-control host and route task messages successfully.

What troubleshooting have you tried?

• Restarted the controlling Mac.
• Fully quit and relaunched ChatGPT/Codex on both Macs.
• Logged out and back in on the controlling Mac.
• Removed and re-enrolled the remote Mac.
• Recreated the controlling app's local global state.
• Reset and freshly granted Accessibility, Screen Recording, and AppleEvents permissions for the desktop app and Computer Use service.
• Removed and reinstalled the bundled Computer Use component.

None changed the behavior. The two machines have distinct installation identities; those values are intentionally not included.

Related issues checked

• #27231 covers broader Mac-to-Mac Remote Control connection failures.
• #38095 includes a CUAService bootstrap -1712 symptom, but its Remote Control setup cannot be enabled. Here pairing succeeds and both UIs show connected, yet the controller lacks the AppServerManager registration required to send task messages.

Additional information

No host or environment identifiers, account names, filesystem paths, installation IDs, tokens, task titles, project details, or complete logs are included. I can provide additional sanitized diagnostics if useful.

No source files or tests are identified. Reproduce the two-Mac pairing flow, then trace RemoteHostedPIPContent, CUAService bootstrap, and AppServerManager registration around the missing hostId. Done means a paired host registers an AppServerManager and remote task messages route successfully without the reported error.