Two environment variables for pointing memory at your own server exist but do nothing.
CLAUDE_CODE_MEMORY_API_BASE_URL and CLAUDE_CODE_MEMORY_API_TOKEN are declared, but the resolver has an empty body.
What's wrong with this entry?
Two environment variable names for pointing memory at your own server, CLAUDE_CODE_MEMORY_API_BASE_URL and CLAUDE_CODE_MEMORY_API_TOKEN, are declared in this build and excluded from the environment restored from saved credentials. Setting them does nothing: the function that resolves the base URL has an empty body that returns nothing, so the override branch is never taken.
- The memory client can switch to
auth: "none"with a bearer header, but only reachable once the resolver returns a URL.
"CLAUDE_CODE_MEMORY_API_TOKEN",
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 base token
-
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