Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.232 ·

Cloud sessions are told up front they cannot message a trusted-device peer

Cloud sessions lacking a trusted-device token are told upfront they can't message a Remote Control peer.

You'll notice Improvements
JSON All of v2.1.232
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Remote ControlArea: what it touches
ImprovementsKind: in v2.1.232,
ImprovementsSection of the release
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.

See this entry in the whole of v2.1.232 →

Feedback