Group of 2 Nothing to try yet
No documentation found
A new background 'memory context' prefetch path exists but stays off unless enabled by feature gate or a new env var
What
- A new memory-context prefetch/fetch path was added that fires performance timers (
memory_context_fetch_ms,memory_context_boot_spillover_ms). It requires eitherCLAUDE_CODE_ENTRYPOINTbeingremote_cowork/remote_cowork_trigger, or a newSYSTEM_REMINDER_MEMORY_CONTEXTenvironment variable, plus an account/session check, plus thetengu_misty_anchorfeature gate. SYSTEM_REMINDER_MEMORY_CONTEXTwas 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 whentengu_misty_anchorwould otherwise be off.
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.
Names in the bundleSYSTEM_REMINDER_MEMORY_CONTEXT
Feature flag
tengu_misty_anchor Off in both readingsThe flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.
This account: off · anonymous baseline: off · compiled default in v2.1.267: off
Read once, for one account on one subscription tier, against v2.1.267. It isn't a statement about your account. What a flag value here can and cannot tell you
One source agreesOne thing we can check says the same as this entry.
The name it cites is new in this build
New in this build: SYSTEM_REMINDER_MEMORY_CONTEXT