{"version":"2.1.277","anchor":"agent-memory-files-refuse-to-load-from-symlinksspecial-file","canonical_anchor":"agent-memory-files-refuse-to-load-from-symlinksspecial-file","heading":"Agent memory can be marked read-only and now refuses to load from symlinks","tier":"notice","area":"Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/agent-memory-files-refuse-to-load-from-symlinksspecial-file","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### Agent memory can be marked read-only and now refuses to load from symlinks\n\nPersistent agent memory can be set read-only for a session, and memory files are no longer read through symlinks or special files\n\n**What**\n\n- The persistent memory system-prompt builder gained a `readOnly` option; when set, the prompt tells the model \"This memory is read-only this session \u2014 you cannot save new memories to it\" and omits the save\/organize instructions and the memory type list entirely.\n\n- Reading an agent's memory file now checks that the entry point is a regular file, not a symlink or other special file, before reading it. If that check fails, the memory content is treated as empty and the session is told the memory is read-only for that turn, with instructions not to create or write files in its folder.\n\n**Why**\n\nThis prevents memory files from being read through a symlink, which could otherwise be used to trick Claude into reading unintended files, and gives Claude Code a clear way to tell the model when it should not attempt to write new memories.\n\n- Area: Memory\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}