{"version":"2.1.224","anchor":"cross-machine-messages-ask-first-when-peer-isolation-is-on","canonical_anchor":"cross-machine-messages-ask-first-when-peer-isolation-is-on","heading":"Cross-machine messages ask first when peer isolation is on","tier":"use","area":"Cross-Session Messaging","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/cross-machine-messages-ask-first-when-peer-isolation-is-on","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Cross-machine messages ask first when peer isolation is on\n\nWith isolatePeerMachines on, cross-machine messages now stop and ask for your approval.\n\n**What**\n\nWith 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.\n\n**Details**\n\n- The three triggering cases are bridge addresses, resolved cloud sessions, and unresolvable names during a failed session-list lookup.\n\n**Evidence**\n\n`isolatePeerMachines is enabled \\u2014 cross-machine message requires explicit approval`\n\n- Area: Cross-Session Messaging\n- Names: `isolatePeerMachines`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 4\/5"}