Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.243 Home All releases ←olderv2.1.242 v2.1.245newer→
Claude Code v2.1.243

Gateway loopback escape hatch is still present

Use it now
Useful2 Signal2
Elsewhere not in their notes

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

CLAUDE_GATEWAY_ALLOW_LOOPBACK
What

An earlier reading of this build suggested the check behind CLAUDE_GATEWAY_ALLOW_LOOPBACK had been removed. It has not: the check and its error text are unchanged, so pointing the gateway's key-set URL at a loopback address still requires that environment variable to be set.

Details
  • The code moved position in the bundle rather than being deleted.
  • Without the variable, a loopback target is rejected with the message naming cri.jwks_url.
Evidence

cri.jwks_url targets loopback but CLAUDE_GATEWAY_ALLOW_LOOPBACK is not set

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.243 →