{"version":"2.1.227","anchor":"groundwork-for-a-development-memory-backend-unreachable-in-t","canonical_anchor":"groundwork-for-a-development-memory-backend-unreachable-in-t","heading":"Groundwork for a development memory backend, unreachable in this build","tier":"soon","area":"Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/groundwork-for-a-development-memory-backend-unreachable-in-t","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Groundwork for a development memory backend, unreachable in this build\n\nMemory could sync against your own server with a bearer token, but the selecting check never returns.\n\n**What**\n\nMemory 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.\n\n**Details**\n\n- Both environment variable names were added to the lists that allow them through and scrub them from logs.\n- When active it would bypass the usual organisation-memory precondition on its own.\n\n**Evidence**\n\n`memory-dev\/memory-dev`\n\n- Area: Memory\n- Names: `CLAUDE_CODE_MEMORY_API_TOKEN`, `CLAUDE_CODE_MEMORY_API_BASE_URL`\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}