{"version":"2.1.248","anchor":"prompt-for-remote-machine-tools-now-names-the-other-machine-","canonical_anchor":"prompt-for-remote-machine-tools-now-names-the-other-machine-","heading":"Prompt for remote-machine tools now names the other machine's permission rules","tier":"notice","area":"Remote Tools","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/prompt-for-remote-machine-tools-now-names-the-other-machine-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Prompt for remote-machine tools now names the other machine's permission rules\n\nClaude is now told remote-machine tool calls run under that machine's own permission rules.\n\n**What**\n\nThe system prompt describing tools that act on an attached machine now says those calls run under that machine's own permission rules, rather than describing the target as files in its project folder. This changes what the model is told about where edits land and which approval prompts apply.\n\n**Details**\n\n- The surrounding preamble, saying that machine's own Claude Code decides what may run there and may ask the user first, is unchanged. Only the per-tool sentences moved.\n\n**Evidence**\n\n`on the user's current files there, under that machine's own permission rules`\n\n- Area: Remote Tools\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 4\/5"}