Follow Discord
Sweep 06 Nov 2026 · 01:32Z Build v2.1.319 537 read Stable v2.1.311 Latest v2.1.318 Next v2.1.319 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.319 ·

Gateway settings checks warn about five more misconfigurations

Claude Code's gateway now warns about guardrail headers, GovCloud mixing, base URL variables, pooled priority and model mappings

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

Claude Code's gateway routes requests to model providers such as Amazon Bedrock and Google Cloud's Agent Platform (Vertex). Its check of managed settings, the settings an administrator sets centrally, now warns about:

  • An X-Amzn-Bedrock-GuardrailIdentifier header, which the gateway does not pass on to Bedrock, so it has no effect unless a Bedrock upstream sets guardrail:.
  • admin.pooled_priority_order set while admin.pooled_conflict_rule is not priority_list, in which case it is ignored.
  • A model mapped to upstreams outside the policies that list it.
  • GovCloud upstreams that share developers with non-GovCloud upstreams.
  • ANTHROPIC_BEDROCK_BASE_URL or ANTHROPIC_VERTEX_BASE_URL in the gateway's environment applying to upstreams that have no base_url of their own.

An upstream is one of the provider endpoints the gateway sends requests to.

Why

Gateway operators find out early about settings that quietly do nothing, or that could send traffic across a GovCloud boundary they meant to keep separate.

See this entry in the whole of v2.1.319 →

Feedback