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.96 Home All releases ←olderv2.1.94 v2.1.97newer→
Claude Code v2.1.96

Bedrock bearer token authentication streamlined

What

Bearer token authentication for AWS Bedrock has been refactored to use the SDK's native apiKey parameter instead of manually setting skipAuth: true and injecting an Authorization header.

Details
  • Previously, when using AWS_BEARER_TOKEN_BEDROCK, Claude Code would set skipAuth: !0 and manually add Authorization: Bearer <token> to the request headers. This has been simplified to pass the token directly as apiKey, which is the SDK's standard mechanism.
  • When CLAUDE_CODE_SKIP_BEDROCK_AUTH is enabled, the code now properly extracts and preserves any existing Authorization header from defaultHeaders configuration. Previously, custom authorization headers in defaultHeaders could be ignored in certain code paths.
  • The skipAuth flag is now only set when CLAUDE_CODE_SKIP_BEDROCK_AUTH is enabled and no bearer token is available (previously it was set whenever either the skip flag or a bearer token was present).
Evidence

Bedrock client construction refactored across three code paths (search for apiKey: Y.token, apiKey: process.env.AWS_BEARER_TOKEN_BEDROCK, and the new pq_ helper that extracts authorization headers)

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

See this entry in the whole of v2.1.96 →