{"version":"2.1.248","anchor":"remote-machine-tool-descriptions-clarify-whose-permissions-a","canonical_anchor":"remote-machine-tool-descriptions-clarify-whose-permissions-a","heading":"Remote-machine tool descriptions clarify whose permissions apply","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/remote-machine-tool-descriptions-clarify-whose-permissions-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Remote-machine tool descriptions clarify whose permissions apply\n\nRemote-machine tools now say they use absolute paths under that machine's permissions.\n\n**What**\n\nThe tools that act on another machine now describe themselves as operating on that machine's files by absolute path, under that machine's own permission rules, rather than on files \"in its project folder\".\n\n**Details**\n\n- The existing caveat is kept: edits made to the session snapshot are not sent back.\n\n**Evidence**\n\n`on that machine's files by their absolute path there, under its own permission rules`\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}