{"version":"2.1.219","anchor":"memory-recall-skips-the-current-session-s-own-logs","canonical_anchor":"memory-recall-skips-the-current-session-s-own-logs","heading":"Memory recall skips the current session's own logs","tier":"notice","area":"Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219\/e\/memory-recall-skips-the-current-session-s-own-logs","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219","markdown":"### Memory recall skips the current session's own logs\n\nMemory recall no longer feeds a session its own transcript notes back to itself.\n\n**What**\n\nCandidate memory files belonging to the running session are now filtered out, so a session cannot recall its own transcript notes back into itself.\n\n**Details**\n\n- A predicate passed into memory recall rejects any candidate under `logs\/` whose basename is `<id>.md` or starts with `<id>-`, where `<id>` is the first 8 characters of the current session identifier.\n- Built defensively: returns undefined if the session id cannot be read, in which case no filtering is applied.\n\n**Evidence**\n\n`if (!r.startsWith(\"logs\/\")) return !1;`\n\n- Area: Memory\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}