{"version":"2.1.304","anchor":"managed-memory-files-are-marked-unverified","canonical_anchor":"managed-memory-files-are-marked-unverified","heading":"Some managed memory files are now marked unverified and shown to Claude as quotes","tier":"notice","area":"Memory","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/managed-memory-files-are-marked-unverified","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Some managed memory files are now marked unverified and shown to Claude as quotes\n\nCertain managed memory files are flagged unverified, passed to Claude as quoted text, and re-sent when that flag changes\n\n**Unclear.** It is not clear which locations trigger the flag or what Claude Code does differently with an unverified file.\n\n**What**\n\nMemory files are instruction files, such as CLAUDE.md, that Claude Code loads into the conversation. Managed ones are set by an administrator. This release adds an `unverified` flag:\n\n- When a managed memory file's path passes a certain check, the file is marked `unverified`, and so is every file it includes. What the check looks for was not identified.\n\n- A memory file marked `unverified` is now given to Claude with every line starting with `> `, as quoted text. Before, all memory content was given as plain text.\n\n- When Claude Code checks whether loaded files changed, it now compares the `unverified` flag as well as content and type.\n\n**Why**\n\nClaude can now tell some memory content apart as quoted material rather than plain instructions, and a change in that marking is picked up.\n\n- Area: Memory\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: both\n- Heads-up: no"}