Follow Discord
Sweep 22 Sep 2026 · 17:19Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.265 ·

CRI/gateway loopback config validator gains an escape-hatch env var

Gateway loopback check now also covers cri.issuer and cri.policy.webhook.url, not just cri.jwks_url

TierUnder the hoodhow much it should matter to you
Useful1my rating, 1 to 5
Signal1worth watching, 1 to 5
AreaElsewherewhat it touches
KindInternal Changesin v2.1.265,
Under the hood

Gateway loopback check now also covers cri.issuer and cri.policy.webhook.url, not just cri.jwks_url

What

The deployment-time check that rejects loopback addresses (like localhost) in gateway configuration still requires the CLAUDE_GATEWAY_ALLOW_LOOPBACK environment variable to be set before it will allow one through. This check now also applies to cri.issuer and cri.policy.webhook.url, in addition to cri.jwks_url.

Why

This widens the same safety net that was already in place for cri.jwks_url to two more configuration fields, so pointing any of these three settings at a loopback address without the escape-hatch variable set will still be treated as a fatal misconfiguration.

Read from
Names in the bundleCLAUDE_GATEWAY_ALLOW_LOOPBACK
Since it was published

The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.

Confirmed since Anthropic's documentation has since written up CLAUDE_GATEWAY_ALLOW_LOOPBACK, on Claude Code changelog. * Improved the Claude apps gateway's loopback error messages to name `CLAUDE_GATEWAY_ALLOW_LOOPBACK` changelog see the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up CLAUDE_GATEWAY_ALLOW_LOOPBACK, on Claude Code changelog.

See this entry in the whole of v2.1.265 →

Feedback