Source Intelligence

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

All of v2.1.224 Home All releases olderv2.1.223 v2.1.225newer

Cross-machine messages ask first when peer isolation is on

Use it now
Useful4 Signal4
Cross-Session Messaging Notable not in their notes

With isolatePeerMachines on, cross-machine messages now stop and ask for your approval.

isolatePeerMachines
What

With the isolatePeerMachines protection enabled, sending a message to a Remote Control session, to a cloud session, or to a name that could not be resolved because the cloud session list was unavailable, now stops and asks for your explicit approval instead of going ahead.

Details
  • The three triggering cases are bridge addresses, resolved cloud sessions, and unresolvable names during a failed session-list lookup.
Evidence

isolatePeerMachines is enabled \u2014 cross-machine message requires explicit approval

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.

See this entry in the whole of v2.1.224 →