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.228 Home All releases ←olderv2.1.227 v2.1.229newer→
Claude Code v2.1.228

Vertex clients no longer send a stale Authorization header

You'll notice
Useful3 Signal2
Vertex

On Vertex, stale Authorization headers no longer clash with Google's own credentials.

What

When Claude Code talks to Anthropic models on Google Vertex, the HTTP client now blanks out Authorization (and X-Api-Key, unless a check passes) so Google's own auth client is the only thing supplying credentials. If auth resolution is skipped, your own Authorization value is passed through instead.

Details
  • The blanking happens through default headers set at client construction time, so it applies to every request that client makes.
  • Where credential resolution is bypassed, the caller-supplied value travels as a separate wireAuthorization field rather than being dropped.
  • The client's internal auth promise now has a no-op catch, so a failed credential fetch no longer surfaces as an unhandled promise rejection.
Evidence

wireAuthorization

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.228 →