{"version":"2.1.281","anchor":"reading-memory-files-while-memory-is-paused-the-deny-check","canonical_anchor":"reading-memory-files-while-memory-is-paused-the-deny-check","heading":"Reading memory files while memory is paused: the deny check now uses the resolved path","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/reading-memory-files-while-memory-is-paused-the-deny-check","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Reading memory files while memory is paused: the deny check now uses the resolved path\n\nReading memory files while memory is paused is now blocked based on the file's actual resolved location\n\n**What**\n\nWhen memory is paused with `\/pause-memory`, Claude Code refuses to read memory files. That check now looks at the resolved path of the file being read, meaning its full final location, rather than the path as first given.\n\nThe refusal message is unchanged: \"Cannot read memory while it is paused. Run \/pause-memory to resume automemory.\" The recorded reason is \"memory access blocked by \/pause-memory\".\n\n**Why**\n\nChecking the final location makes it harder for a read to get past the pause by naming the same memory file a different way."}