{"version":"2.1.124","anchor":"isolatepeermachines-setting-remote-control-safety","canonical_anchor":"isolatepeermachines-setting-remote-control-safety","heading":"isolatePeerMachines setting (Remote Control safety)","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.124\/e\/isolatepeermachines-setting-remote-control-safety","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.124","markdown":"### `isolatePeerMachines` setting (Remote Control safety)\n\n**What**\n\nA new boolean setting that requires explicit user approval before `SendMessage` can reach a peer Claude Code session running on a different machine via Remote Control.\n\nUsage (in settings.json):\n\n`{ \"isolatePeerMachines\": true }` **Details** - When the latch is engaged for a session it is persisted to the JSONL session log as `isolation-latch` events (sticky type) so resumed sessions inherit the side they were locked to. - Setting description: `Require explicit approval before SendMessage can reach a peer session on another machine via Remote Control`. **Evidence** Setting schema and runtime check (search for `\"isolatePeerMachines\"` and `\"isolation-latch\"`)."}