{"version":"2.1.315","anchor":"remote-session-cross-session-turn-admission-and-usage-limit","canonical_anchor":"remote-session-cross-session-turn-admission-and-usage-limit","heading":"Bedrock gateway upstreams must share guardrail input tagging","tier":"notice","area":"Bedrock","scope":"org","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315\/e\/remote-session-cross-session-turn-admission-and-usage-limit","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315","markdown":"### Bedrock gateway upstreams must share guardrail input tagging\n\nGateway configs now require the same `guardrail.input_tagging` on every Bedrock upstream, and remote-session messages wait for admission\n\n**What**\n\nA gateway configuration that sends requests to several Amazon Bedrock upstreams now has to set the same `guardrail.input_tagging` on all of them. An upstream is a server the gateway passes requests on to. If the values differ, Claude Code asks you to set the same value on every Bedrock upstream.\n\nIn remote sessions driven through the SDK, which is the toolkit for running Claude Code from other programs, messages delivered by the server now pass an admission step before they become a turn. A turn is one exchange between you and Claude. Claude Code also records whether a message ends its turn.\n\nClaude Code now also tracks two new usage-limit cases: when the text served about a usage limit was altered, and when it was rejected.\n\n**Why**\n\nIf you run a gateway with several Bedrock upstreams, make sure their guardrail input tagging matches, or the configuration will be refused.\n\n- Area: Bedrock\n- Names: `guardrail.input_tagging`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: yes"}