CLAUDE_GATEWAY_ALLOW_LOOPBACK

A Claude Code environment variable, read out of the shipped bundle. It has been in the build since v2.1.160, including the newest one read.

Releases whose published page names CLAUDE_GATEWAY_ALLOW_LOOPBACK.

1. v2.1.285 29 Sep 2026
   Some requests now name a gateway or API host

   One kind of request now says whether it goes to ccr-gateway or api, depending on the kind of session

   found in this entry's text, named in this entry

2. v2.1.281 23 Sep 2026
   CLAUDE_GATEWAY_ALLOW_LOOPBACK helpers restructured in gateway module

   The code reading CLAUDE_GATEWAY_ALLOW_LOOPBACK was reorganised; the variable still lets the gateway reach loopback addresses

   found in this entry's text, named in this entry

3. v2.1.277 18 Sep 2026
   Gateway egress-boundary mode: outbound traffic can defer address checks to a forward proxy

   A new env var lets a gateway proxy handle outbound address safety checks itself instead of Claude Code

   found in this entry's text

4. v2.1.277 18 Sep 2026
   Gateway self-host config: per-upstream custom headers, and a new loopback guard on telemetry forwarding

   Gateway config adds per-upstream custom headers and blocks loopback telemetry URLs unless explicitly allowed

   found in this entry's text

5. v2.1.265 8 Sep 2026
   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

   found in this entry's text, named in this entry

6. v2.1.243 24 Aug 2026
   Gateway loopback escape hatch is still present

   Pointing the gateway's key-set URL at a loopback address still needs that environment variable set.

   named in this entry, found in this entry's text

7. v2.1.238 20 Aug 2026
   Loopback JWKS overrides now require an explicit test escape hatch

   Pointing the gateway key-set URL at loopback is now blocked unless you set CLAUDE_GATEWAY_ALLOW_LOOPBACK, which is for tests only.

   named in this entry, found in this entry's text

8. v2.1.232 13 Aug 2026
   Environment variables read through one typed table instead of scattered process.env lookups

   Environment variables are now read through one typed table, with the same names and behaviour.

   found in this entry's text

9. v2.1.228 11 Aug 2026
   Self-hosted gateway can admit callers with Anthropic-issued JWTs

   The gateway can authenticate callers with Anthropic-issued JWTs verified against a remote key endpoint.

   found in this entry's text

10. v2.1.228 11 Aug 2026
    Gateway customer-routed inference config, disabled by default

    The self-hosted gateway accepts a strict customer-routed inference config block, off unless you enable it.

    named in this entry, found in this entry's text

The earliest release whose published evidence quoted CLAUDE_GATEWAY_ALLOW_LOOPBACK was v2.1.232, 13 Aug 2026. That is the oldest release this project wrote about it, so it is a floor on the name's age and not the release that introduced it. It is not a presence reading: which builds carried the name is the table below.

One row per release since the first build this name was read out of. Absent means the build was read and the name was not in it, never mined means no bundle for that release was ever archived, and a declared type or a default is only ever what that release's own bundle stated.

Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the environment variable does. All environment variables.