{"version":"2.1.283","anchor":"claude-code-gb-base-url-added-to-the-protected-env-var-set-i","canonical_anchor":"claude-code-gb-base-url-added-to-the-protected-env-var-set-i","heading":"CLAUDE_CODE_GB_BASE_URL gets the same settings checks as the proxy variables","tier":"use","area":"Configuration","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/claude-code-gb-base-url-added-to-the-protected-env-var-set-i","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### `CLAUDE_CODE_GB_BASE_URL` gets the same settings checks as the proxy variables\n\nCLAUDE_CODE_GB_BASE_URL joins the proxy, certificate and bridge variables that Claude Code checks when it cleans a settings file\n\n**Unclear.** It is unclear whether the filter keeps or removes these variables, which settings files it runs on, and whether the variable really sets where feature flags are fetched from.\n\n**What**\n\nThe environment variable `CLAUDE_CODE_GB_BASE_URL` has been added to a fixed list of sensitive variables. The list already held `HTTPS_PROXY`, `NODE_EXTRA_CA_CERTS`, `CLAUDE_BRIDGE_OAUTH_TOKEN` and `CLAUDE_REMOTE_TOOLS_BRIDGE_URL`. The new variable sits next to `CLAUDE_CODE_GB_REFRESH_INTERVAL_MS`.\n\nClaude Code uses this list in two places:\n\n- Cleaning a settings file: it filters the `env` section of the settings against the list, in the same step that handles `managedMcpServers`.\n\n- Inspecting a settings file: it checks whether the file sets any of these variables.\n\n**Why**\n\nWherever Claude Code cleans or inspects a settings file for these variables, `CLAUDE_CODE_GB_BASE_URL` now gets the same treatment as the proxy, certificate and remote bridge settings.\n\n- Area: Configuration\n- Names: `CLAUDE_CODE_GB_BASE_URL`, `CLAUDE_CODE_GB_REFRESH_INTERVAL_MS`\n- Tier: Use it now\n- Useful: 2\/5\n- Signal: 3\/5"}