{"version":"2.1.267","anchor":"new-env-var-forwarded-for-memory-context-system-reminders","canonical_anchor":"memory-context-prefetch-built-but-gated-off-by-tengu-misty-a","heading":"Memory-context prefetch added, gated off by default","tier":"soon","area":"Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/new-env-var-forwarded-for-memory-context-system-reminders","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### Memory-context prefetch added, gated off by default\n\nA new background 'memory context' prefetch path exists but stays off unless enabled by feature gate or a new env var\n\n**Unclear.** Whether this variable is meant for general use or is an internal\/testing override is not stated.\n\n**What**\n\n- A new memory-context prefetch\/fetch path was added that fires performance timers (`memory_context_fetch_ms`, `memory_context_boot_spillover_ms`). It requires either `CLAUDE_CODE_ENTRYPOINT` being `remote_cowork`\/`remote_cowork_trigger`, or a new `SYSTEM_REMINDER_MEMORY_CONTEXT` environment variable, plus an account\/session check, plus the `tengu_misty_anchor` feature gate.\n\n- `SYSTEM_REMINDER_MEMORY_CONTEXT` was also added to the lists of environment variables that get passed through\/preserved for sessions, and setting it can force-enable the memory-context fetch even when `tengu_misty_anchor` would otherwise be off.\n\n**Why** The feature is built but gated off by default (`tengu_misty_anchor`), so most users won't see any behavior change yet; the env var provides a way to force it on for testing.\n\n- Flag `tengu_misty_anchor`: Off in both readings (read for one account on one subscription tier against v2.1.267; this account: off, anonymous baseline: off, compiled default: off)\n- Area: Memory\n- Names: `SYSTEM_REMINDER_MEMORY_CONTEXT`\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}