You'll notice
Useful2 Signal3
Cloud sessions lacking a trusted-device token are told upfront they can't message a Remote Control peer.
What's wrong with this entry?
Anonymous. No account, no email.
What
If you are in a cloud session with no trusted-device token and your organization requires one, sending a message to a Remote Control peer is refused immediately with an explanation, instead of being attempted and failing.
Details
- The message explains the target "requires a trusted device, which a cloud session never has" and tells you to message it from one of your own machines.
- Applies when the session is remote (
CLAUDE_CODE_REMOTE) and org policy requires a trusted device.
Evidence
not reachable from a cloud session \u2014 that session requires a trusted device, which a cloud session never has; message it from one of your own machines instead
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.