{"version":"2.1.287","anchor":"cross-machine-send-permission-can-be-asked-unconditionally","canonical_anchor":"cross-machine-send-permission-can-be-asked-unconditionally","heading":"Sending a message to a session on another machine can always require approval","tier":"notice","area":"Session Messaging","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/cross-machine-send-permission-can-be-asked-unconditionally","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Sending a message to a session on another machine can always require approval\n\nClaude Code can now ask for your approval before a message goes to another machine, even when `isolatePeerMachines` is off\n\n**Unclear.** It is not clear which part of Claude Code turns on the always-ask option, or when.\n\n**What**\n\nWhen Claude sends a message to one of your sessions on another machine, Claude Code checks whether it should ask you first. Until now it asked only when `isolatePeerMachines` was turned on.\n\nThat check now has an option that makes it ask every time, whatever `isolatePeerMachines` is set to. When the option is used and the send is not approved, the message says that sending needs your approval and that nothing was sent. It does not mention `isolatePeerMachines`.\n\n**Why**\n\nIn some cases a message to another machine can now need your approval even if you have not turned on `isolatePeerMachines`.\n\n- Area: Session Messaging\n- Names: `isolatePeerMachines`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}