Follow Discord
Sweep 29 Sep 2026 · 18:10Z Build v2.1.285 506 read Stable v2.1.280 Latest v2.1.285 Next v2.1.285 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.285 ·

Bedrock, Mantle and Vertex connections share headers and can send your API key

Bedrock, Mantle and Vertex clients now share one set of headers and add an X-Api-Key header from ANTHROPIC_API_KEY unless one is set

You'll notice Improvements
JSON All of v2.1.285
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Third-Party ProvidersArea: what it touches
ImprovementsKind: in v2.1.285,
ImprovementsSection of the release
What

Claude Code can talk to Claude through third-party providers such as Amazon Bedrock, Mantle and Google Vertex. How it connects to them changed:

  • The Bedrock, Mantle and Vertex connections now add a shared set of headers (extra labels sent with each request).
  • If ANTHROPIC_API_KEY is set, its value is sent as an X-Api-Key header, unless a header of that name is already present. This is useful when a gateway sits between Claude Code and the provider.
  • The checks that test whether Bedrock and Mantle are reachable now report what went wrong, not only yes or no.
  • The special handling for CLAUDE_CODE_SKIP_AWS_CRED_CACHE, which used to skip the cached AWS credentials, has been replaced by one shared way of looking up AWS credentials.
Why

If you use a third-party provider, how Claude Code authenticates may behave differently. This matters most if you have ANTHROPIC_API_KEY set or rely on CLAUDE_CODE_SKIP_AWS_CRED_CACHE.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhether `CLAUDE_CODE_SKIP_AWS_CRED_CACHE` still has any effect, and how the new credential lookup caches credentials, is not clear.

See this entry in the whole of v2.1.285 →

Feedback