Follow Discord
Sweep 22 Oct 2026 · 21:04Z Build v2.1.309 528 read Stable v2.1.308 Latest v2.1.309 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.251 ·

Custom OAuth endpoints keyed to a single environment variable

One env var now decides your custom OAuth endpoint, and it passes to spawned commands.

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

A custom OAuth endpoint is now recognised purely from the CLAUDE_CODE_CUSTOM_OAUTH_URL environment variable, with the secondary fallback check removed. The same variable is also registered in the list the subprocess environment builder knows about, so it is carried as a recognised Claude Code variable when Claude Code spawns commands.

Details
  • Setting CLAUDE_CODE_CUSTOM_OAUTH_URL is the only way to be treated as having a custom OAuth endpoint; unset means the standard endpoint is used.
  • The variable is now a known name to the code that assembles environment variables for spawned subprocesses, rather than an unrecognised passthrough.
  • Nothing else in this build shows what a spawned process does with the value once it receives it.
Evidence

CLAUDE_CODE_CUSTOM_OAUTH_URL !== void 0, "CLAUDE_CODE_CUSTOM_OAUTH_URL"

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Read from
Names in the bundleCLAUDE_CODE_CUSTOM_OAUTH_URL

See this entry in the whole of v2.1.251 →

Feedback