{"version":"2.1.219","anchor":"pinned-memories-are-injected-into-the-session","canonical_anchor":"pinned-memories-are-injected-into-the-session","heading":"Pinned memories are injected into the session","tier":"soon","area":"Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219\/e\/pinned-memories-are-injected-into-the-session","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219","markdown":"### Pinned memories are injected into the session\n\nAdding `pinned: true` to a memory file's frontmatter would apply it to every session automatically.\n\n**What**\n\nMemory files whose frontmatter carries `pinned: true` are injected so they apply to every session rather than only when retrieved.\n\n**Details**\n\n- Pinned files are scanned, sorted by mtime, capped in count, and truncated when oversized\n- Frontmatter documentation now describes the `pinned` field\n- New one-shot telemetry event `tengu_memdir_pinned_injected` reports pinned_file_count, pinned_injected_count, pinned_injected_chars, truncated and malformed counts\n- New scan-failure paths log \"memory_scan_readdir_failed\" and \"pin_scan_failed\"\n- Gated on `tengu_stone_shell` with fallback false, and suppressed entirely when CLAUDE_COWORK_MEMORY_INDEX_CONTENT is set\n\n**Evidence**\n\n`tengu_memdir_pinned_injected`\n\n- Flag `tengu_stone_shell`: Off in both readings (read for one account on one subscription tier against v2.1.219; this account: off, anonymous baseline: off, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Memory\n- Names: `pinned: true`, `CLAUDE_COWORK_MEMORY_INDEX_CONTENT`\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}