Follow Discord
Sweep 08 Oct 2026 · 18:53Z Build v2.1.295 516 read Stable v2.1.286 Latest v2.1.295 Next v2.1.295 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.265entry #132

Claude Code v2.1.265 ·

Gateway-forced login detection and validation simplified

Gateway login logic was simplified: looser URL validation and a more direct check for when login is forced through the gateway

Group of 4 You'll notice Internal Changes
JSON All of v2.1.265
You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
AuthArea: what it touches
Internal ChangesKind: in v2.1.265,
ImprovementsSection of the release

What

  • The forceLoginGatewayUrl CLI option now accepts any non-empty string rather than requiring a syntactically valid URL.
  • The check for whether login is gateway-forced was simplified to: the login method is "gateway", or a gateway URL is set — replacing a more convoluted prior condition.
  • The forced-login-method resolution for the login flow now short-circuits to "gateway" whenever the session is already in gateway auth mode, rather than only special-casing an explicit managed-setting value.
  • The gateway auth backend's API key check now short-circuits to reporting the key as "missing" first when in gateway mode without the expected check passing, instead of falling through to the normal API-key-helper/environment-variable lookup.

Why These changes make gateway-forced login detection more consistent and predictable across the CLI, reducing edge cases where login mode or API key status could be determined by a stricter or more roundabout check than intended.

Read from
Names in the bundleforceLoginMethod
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.

Added since A small documentation edit on Configure server-managed settings touched a line naming forceLoginMethod after this was published. * **Gateway sign-in keys**: Claude Code never reads [`forceLoginGatewayUrl`](/docs/en/settings-reference#forcelogingatewayurl), [`gatewayInternalNetworks`](/docs/en/settings-reference#gatewayinternalnetworks), or the `"gateway"` value of [… server-managed-settings see the edit
Confirmed since Anthropic's documentation has since written up forceLoginMethod, on Claude apps gateway configuration. Claude Code honors [`forceLoginGatewayUrl`](/docs/en/settings-reference#forcelogingatewayurl), [`gatewayInternalNetworks`](/docs/en/settings-reference#gatewayinternalnetworks), and the `"gateway"` value of [`forceLoginMethod`](/docs/en/set… claude-apps-gateway-config see the edit
How sure we are
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up forceLoginMethod, on Claude apps gateway configuration.
Anthropic's release notes agreeChanged machines with forceLoginGatewayUrl in managed settings to be Claude apps gateway sessions from startup, like forceLoginMethod…

See this entry in the whole of v2.1.265 →

Feedback