Follow Discord
Sweep 25 Sep 2026 · 19:33Z Build v2.1.283 504 read Stable v2.1.274 Latest v2.1.283 Next v2.1.283 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.283entry #60

Claude Code v2.1.283 ·

CLAUDE_CODE_GB_BASE_URL gets the same settings checks as the proxy variables

CLAUDE_CODE_GB_BASE_URL joins the proxy, certificate and bridge variables that Claude Code checks when it cleans a settings file

Use it now No documentation found Improvements
JSON All of v2.1.283
Use it nowTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
ConfigurationArea: what it touches
ImprovementsKind: in v2.1.283,
What probably matters to youSection of the release
What

The 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.

Claude Code uses this list in two places:

  • Cleaning a settings file: it filters the env section of the settings against the list, in the same step that handles managedMcpServers.
  • Inspecting a settings file: it checks whether the file sets any of these variables.
Why

Wherever 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.

Read from
Names in the bundleCLAUDE_CODE_GB_BASE_URLCLAUDE_CODE_GB_REFRESH_INTERVAL_MS
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is unclear whether the filter keeps or removes these variables, which settings files it runs on, and whether the variable really sets…

See this entry in the whole of v2.1.283 →

Feedback