{"version":"2.1.285","anchor":"bedrock-content-type-fixes-and-tc-helper-for-provider-stream","canonical_anchor":"bedrock-content-type-fixes-and-tc-helper-for-provider-stream","heading":"Streaming checks for Anthropic, gateway and AWS providers are shared","tier":"internal","area":"Elsewhere","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/bedrock-content-type-fixes-and-tc-helper-for-provider-stream","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Streaming checks for Anthropic, gateway and AWS providers are shared\n\nClaude Code now handles streamed replies from Anthropic, gateways and Anthropic on AWS through one shared check, and the Bedrock guard is unchanged\n\n**Unclear.** Some requests now also record a timestamp, and what it is used for is not known.\n\n**What**\n\nClaude Code receives Claude's replies as a stream, piece by piece. The checks it runs on those streams for Anthropic's own service, for gateways (a proxy between you and the model provider) and for Anthropic on AWS now go through one shared routine instead of being written out separately in each place.\n\nThe Amazon Bedrock check on a streamed reply's content type and the `CLAUDE_CODE_DISABLE_BEDROCK_CONTENT_TYPE_GUARD` variable that turns it off work as before.\n\n**Why**\n\nThis can change how streamed replies behave for AWS and gateway setups.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}