Memory could sync against your own server with a bearer token, but the selecting check never returns.
A development memory backend using CLAUDE_CODE_MEMORY_API_TOKEN is present but its selection branch is unreachable.
What's wrong with this entry?
Memory sync gained an alternative development backend that skips normal login and takes a bearer token from CLAUDE_CODE_MEMORY_API_TOKEN, with its address from CLAUDE_CODE_MEMORY_API_BASE_URL. The check that selects it calls a function whose body returns nothing, so the branch cannot be reached and normal memory sync is unaffected.
- Both environment variable names were added to the lists that allow them through and scrub them from logs.
- When active it would bypass the usual organisation-memory precondition on its own.
memory-dev/memory-dev
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.248
Memory API endpoint and token environment variables
Both mention token base
-
v2.1.219
Remote Control now explains exactly which endpoint setting blocks it
Both mention base
-
v2.1.238
CLAUDE_CODE_ARTIFACT_SYNC_BASE_URLenv var for artifact syncBoth mention base