Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.239entry #39

Claude Code v2.1.239 ·

Bedrock streaming responses without a content-type no longer fail

Bedrock streaming replies missing a content-type now work, and a new env var restores the old strict check.

Use it now Notable No documentation found Bug Fixes
JSON All of v2.1.239
Use it nowTier: how much it should matter to you
4Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
BedrockArea: what it touches
Bug FixesKind: in v2.1.239,
What probably matters to youSection of the release
What

A Bedrock streaming response that arrives with no content-type header at all is now treated as application/vnd.amazon.eventstream instead of being rejected. Set CLAUDE_CODE_DISABLE_BEDROCK_CONTENT_TYPE_DEFAULT to turn the defaulting off and get the old strict behaviour.

Details
  • Only applies when the header is absent; a wrong content-type still fails the check.
  • Separately, the default AWS credential chain now builds its STS endpoint through a region helper instead of pasting the region into a hardcoded URL.
Evidence

CLAUDE_CODE_DISABLE_BEDROCK_CONTENT_TYPE_DEFAULT

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

Read from
Names in the bundleCLAUDE_CODE_DISABLE_BEDROCK_CONTENT_TYPE_DEFAULT
How sure we are
One source agreesOne thing we can check says the same as this entry.
The name it cites is new in this buildNew in this build: CLAUDE_CODE_DISABLE_BEDROCK_CONTENT_TYPE_DEFAULT

See this entry in the whole of v2.1.239 →

Feedback