{"version":"2.1.238","anchor":"remote-sessions-no-longer-get-automatic-read-access-to-memor","canonical_anchor":"remote-sessions-no-longer-get-automatic-read-access-to-memor","heading":"Remote sessions no longer get automatic read access to memory, tasks and teams","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/remote-sessions-no-longer-get-automatic-read-access-to-memor","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### Remote sessions no longer get automatic read access to memory, tasks and teams\n\nRemote sessions no longer get free read access to memory, tasks and teams files.\n\n**What**\n\nReads of agent memory files, auto memory files, the tasks directory, the teams directory and bundled skill reference files were previously allowed without a permission check. When the request comes from a remote surface, those shortcuts are now skipped and the read goes through the normal permission flow.\n\n**Details**\n\n- Gated on a per-request flag marking the caller as a remote surface; local sessions keep the fast paths.\n\n**Evidence**\n\n`Agent memory files are allowed for reading`\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 4\/5"}