{"version":"2.1.227","anchor":"two-memory-api-environment-variables-are-hidden-from-command","canonical_anchor":"two-memory-api-environment-variables-are-hidden-from-command","heading":"Two memory-API environment variables are hidden from commands Claude runs","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/two-memory-api-environment-variables-are-hidden-from-command","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Two memory-API environment variables are hidden from commands Claude runs\n\nYour memory API base URL and token are now hidden from every command Claude runs.\n\n**What**\n\n`CLAUDE_CODE_MEMORY_API_BASE_URL` and `CLAUDE_CODE_MEMORY_API_TOKEN` are now stripped from the environment given to every subprocess Claude Code spawns, the same way `CLAUDE_CODE_OAUTH_TOKEN` and `CLAUDE_CODE_ARTIFACTS_API_TOKEN` already were. A bash command or tool cannot read your memory API token.\n\n**Details**\n\n- Both names are new in this build.\n- The code that would use the token sends it as an `Authorization: Bearer` header, but only when an override host is set, and the function that supplies that host currently returns nothing. So the memory-API override is not reachable yet; the scrubbing is the part that is live.\n\n**Evidence**\n\n`CLAUDE_CODE_MEMORY_API_TOKEN`\n\n- Area: Permissions\n- Names: `CLAUDE_CODE_MEMORY_API_BASE_URL`, `CLAUDE_CODE_MEMORY_API_TOKEN`\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 3\/5"}