Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.251 Home All releases ←olderv2.1.250
Claude Code v2.1.251

Custom OAuth endpoints keyed to a single environment variable

Use it now
Useful3 Signal3
Auth Notable not in their notes

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

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

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.251 →