Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.267entry #6

Claude Code v2.1.267 ·

Memory-context prefetch added, gated off by default

A new background 'memory context' prefetch path exists but stays off unless enabled by feature gate or a new env var

Group of 2 Nothing to try yet No documentation found In Development
JSON All of v2.1.267
Nothing to try yetTier: how much it should matter to you
3Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
MemoryArea: what it touches
In DevelopmentKind: in v2.1.267,
What probably matters to youSection of the release

Unclear Whether this variable is meant for general use or is an internal/testing override is not stated.

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 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.
  • 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.

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.

Read from
Names in the bundleSYSTEM_REMINDER_MEMORY_CONTEXT
Feature flag
tengu_misty_anchor Off in both readings

The 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

What has happened since
Flag reading moved The flag server now returns off for tengu_misty_anchor, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns on for tengu_misty_anchor, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns off for tengu_misty_anchor, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns on for tengu_misty_anchor, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns off for tengu_misty_anchor, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns on for tengu_misty_anchor, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns off for tengu_misty_anchor, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns on for tengu_misty_anchor, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.

See this across every release →

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhether this variable is meant for general use or is an internal/testing override is not stated.
The name it cites is new in this buildNew in this build: SYSTEM_REMINDER_MEMORY_CONTEXT

See this entry in the whole of v2.1.267 →

Feedback