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

Wider pattern for spotting sensitive HTTP headers

You'll notice
Useful3 Signal2
Privacy

More HTTP headers are recognised as sensitive, including cloud provider auth headers.

What

A pattern was added that recognises headers containing auth, key, token, cookie, secret or credential, plus cloud provider prefixes including Google, AWS, Azure and Cloudflare Access ones, for treating those headers as sensitive.

Details
  • Where it is applied is not visible from the pattern itself.
Evidence

x-goog-|l5d-|bypass|guardrail|amz|x-ms-|azureml

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 →