The memory sync architecture change removes the following:
- The
ANTHROPIC_BEDROCK_MANTLE_API_KEYenvironment variable is no longer recognised. - The old
/api/claude_code/memoryand/api/claude_code/team_memoryendpoints are no longer contacted by the client. If your infrastructure blocks outbound access to the new/v1/code/local/memory/mountsand/v1/code/local/memory/credentialendpoints, org memory will not function. TheCLAUDE_CODE_DISABLE_ORG_MEMORY=1environment variable can disable the feature entirely. - The
tengu_herring_clockfeature flag (which gated the old personal memory sync) has been removed along with the sync implementation it guarded.
Feature flag
tengu_herring_clock 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.210: not a boolean we can read
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.
Read once, for one account on one subscription tier, against v2.1.210. It isn't a statement about your account. What a flag value here can and cannot tell you
Flag reading moved
The flag server now returns off for tengu_herring_clock, 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 nothing at all, having stopped carrying it for tengu_herring_clock, 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.