{"version":"2.1.309","anchor":"memory-file-reads-now-honor-the-sessions-sent-read-rules","canonical_anchor":"memory-file-reads-now-honor-the-sessions-sent-read-rules","heading":"Read rules sent with a session now decide which memory files load","tier":"notice","area":"Memory","scope":"both","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/memory-file-reads-now-honor-the-sessions-sent-read-rules","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Read rules sent with a session now decide which memory files load\n\nLoading CLAUDE.md memory files now follows read rules sent with the request, and loads none if those rules cannot be read\n\n**What**\n\nMemory files such as CLAUDE.md are files of instructions that Claude Code loads into a session. Which memory files are loaded used to depend only on the permissions of the session itself. Claude Code now also applies read rules sent along with the request:\n\n- If those read rules cannot be read, no memory files are loaded, and the result says \"no memory files: the session's read rules could not be read\".\n\n- When Claude Code tracks changed files, it reports \"the repo rules could not be read\" if the repository's rules fail to load.\n\n**Why**\n\nRules about what may be read now also control which CLAUDE.md files reach Claude. If those rules fail to load, Claude Code loads no memory files at all instead of loading them unchecked.\n\n- Area: Memory\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: both\n- Heads-up: yes"}