Unclear The finding does not say whether the new state object or timing values change behaviour.
What
CLAUDE_GATEWAY_ALLOW_LOOPBACK still lets the gateway reach loopback addresses, which are addresses pointing back to the same computer. The code that reads it and applies the loopback checks moved into new shared helpers, with a state object that starts disabled and some timing values.
Why
The variable's meaning is the same, so settings that already use it need no change.
Names in the bundleCLAUDE_GATEWAY_ALLOW_LOOPBACK
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 apps gateway configuration.
| `issuer` | Yes | OIDC discovery base. Must serve discovery at `/.well-known/openid-configuration`. Use HTTPS in production; the gateway accepts an `http://` issuer. A loopback issuer such as `http://localhost:8081` is rejected by the [SS…claude-apps-gateway-config see the edit
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
The finding does not say whether the new state object or timing values change behaviour.
Anthropic's documentation agrees
Anthropic's documentation has since written up CLAUDE_GATEWAY_ALLOW_LOOPBACK, on Claude apps gateway configuration.