{"version":"2.1.227","anchor":"self-hosted-memory-endpoint-is-scaffolded-but-cannot-be-swit","canonical_anchor":"self-hosted-memory-endpoint-is-scaffolded-but-cannot-be-swit","heading":"Self-hosted memory endpoint is scaffolded but cannot be switched on","tier":"soon","area":"Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/self-hosted-memory-endpoint-is-scaffolded-but-cannot-be-swit","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Self-hosted memory endpoint is scaffolded but cannot be switched on\n\nTwo environment variables for pointing memory at your own server exist but do nothing.\n\n**What**\n\nTwo 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.\n\n**Details**\n\n- The memory client can switch to `auth: \"none\"` with a bearer header, but only reachable once the resolver returns a URL.\n\n**Evidence**\n\n`\"CLAUDE_CODE_MEMORY_API_TOKEN\",`\n\n- Area: Memory\n- Names: `CLAUDE_CODE_MEMORY_API_BASE_URL`, `CLAUDE_CODE_MEMORY_API_TOKEN`\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}