forceLoginGatewayUrl
A Claude Code settings key, read out of the shipped bundle. It was in the build from v2.1.162 and was gone by v2.1.284.
Set the gateway URL the login screen connects to
Anthropic's own wording. Read off All settings, captured 2026-10-22.
In the changelogs
11Releases whose published page names forceLoginGatewayUrl.
-
v2.1.296
Setting forceLoginMethod to gateway now leads to the gateway login
With forceLoginMethod set to "gateway" and no forceLoginGatewayUrl, Claude Code now treats gateway login as required
found in this entry's text, named in this entry
-
v2.1.284
Gateway login can accept hosts confirmed by a recognised Claude gateway
Gateway hosts outside the built-in list can now be accepted if a recognised Claude gateway deployment confirms it serves them
found in this entry's text
-
v2.1.284
Gateway address checks now send your login token to a verifier
Rechecking a gateway address now uses a verifier that gets your session token and your organization's pinned login settings
found in this entry's text, named in this entry
-
v2.1.281
CLAUDE_CODE_HOST_GATEWAY_LINEAGE: new env var that marks sessions spawned by a Claude Desktop gatewayNew CLAUDE_CODE_HOST_GATEWAY_LINEAGE variable keeps child processes of a Desktop-hosted gateway session treated as host-managed
found in this entry's text
-
v2.1.281
New managed-policy check for Desktop-hosted gateways
When Claude Desktop runs Claude Code through a gateway, Claude Code now checks that gateway against your organization's policy and explains failures
found in this entry's text, named in this entry
-
v2.1.268
Managed settings can restrict a Cloud gateway sign-in to your org's public IP block
Managed settings can now restrict Cloud gateway sign-in to CIDR blocks matching the org's own public IP
found in this entry's text, named in this entry
-
v2.1.268
New managed-settings key gatewayInternalNetworks joins highest-source-wins auth pins
New managed setting gatewayInternalNetworks joins the group taken only from the top-priority settings source
found in this entry's text
-
v2.1.265
forceLoginGatewayUrl validation loosened from strict URL to non-empty string
forceLoginGatewayUrl now accepts any non-empty string instead of requiring a valid URL
found in this entry's text, named in this entry
-
v2.1.265
Gateway-forced-login detection simplified/changed condition
The check for whether login is forced through a gateway was simplified
found in this entry's text
-
v2.1.247
Managed settings can force login through a gateway
Admins can force gateway login using forceLoginMethod or forceLoginGatewayUrl in managed settings.
named in this entry, found in this entry's text
-
v2.1.242
Managed settings can now merge across sources instead of the top one winning
Admins can set managedSourcesBehavior to merge managed settings sources instead of only the top one.
found in this entry's text
First cited
4The earliest release whose published evidence quoted forceLoginGatewayUrl was v2.1.247, 26 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.
Presence across releases
2Build by build
127One 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 settings key does. All settings keys.