{"version":"2.1.219","anchor":"pinned-memory-files","canonical_anchor":"pinned-memory-files","heading":"Pinned memory files","tier":"soon","area":"Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219\/e\/pinned-memory-files","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219","markdown":"### Pinned memory files\n\nMemory files marked pinned would be injected into every conversation instead of waiting to be recalled.\n\n**What**\n\nMemory files can mark themselves pinned in frontmatter and are then injected as their own prompt section on every conversation rather than listed with ordinary memory files.\n\n**Details**\n\n- `metadata.pinned` is parsed into a `pinnedState` of true, false or malformed; the most recently modified pinned files are selected up to a cap and read as a new `AutoMemPinned` entry type.\n- Rendered as a dedicated section of `<pinned-memory path=\"\u2026\">` blocks with control characters stripped from the path, and excluded from the ordinary memory-file editor list.\n- Telemetry: `memory_pinned_inject` records injected counts, truncation, malformed pins and cap drops; `tengu_memdir_pinned_injected` records counts plus truncated\/malformed; `tengu_memdir_pin_write` fires on writes to memory files.\n- Lives in the cowork memory path, running only when the surrounding index gate passes and the `CLAUDE_COWORK_MEMORY_INDEX_CONTENT` env var is unset.\n\n**Evidence**\n\n`# Pinned memories (apply to every conversation)`, `AutoMemPinned`\n\n- Area: Memory\n- Names: `pinned`, `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"}