Remote Control bridge sessions refuse to start unless your device is enrolled as trusted.
What's wrong with this entry?
Before a Remote Control bridge session starts, Claude Code checks that the device is enrolled as a trusted device. If it is not, the session is skipped, the reason is logged, and the failure is reported as either terminal or an auth problem.
- The unenrolled case is recorded as
trusted_device_unenrolled. - Runs on the bridge session start path.
trusted_device_unenrolled
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.