{"version":"2.1.229","anchor":"pinned-memory-files-are-listed-as-their-own-source","canonical_anchor":"pinned-memory-files-are-listed-as-their-own-source","heading":"Pinned memory files are listed as their own source","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/pinned-memory-files-are-listed-as-their-own-source","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### Pinned memory files are listed as their own source\n\nMemory file listings now label pinned files separately from auto-recalled and files you read.\n\n**What**\n\nWhen Claude Code tells you where the files in a session's memory came from, pinned files now appear as \"pinned, loaded automatically\", separate from files recalled automatically and files you opened with the Read tool. If the same file arrives from more than one source, the pinned label wins.\n\n**Details**\n\n- Third attribution source alongside automatic recall and Read tool opens\n- Pinned entries take precedence over the same path reported by another source\n\n**Evidence**\n\n`pinned, loaded automatically`\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}