Skip to content
← Back to release · 2.1.295
New features / v2.1.295

Force gateway login with no managed settings

CHANGELOG · original

Added support for forceLoginMethod: "gateway" and forceLoginGatewayUrl in your own user settings on machines with no managed settings, so /login opens on that Claude apps gateway
Open official changelog ↗

Documentation

Documentation excerpt

forceLoginGatewayUrl

Set the gateway URL the /login Cloud gateway screen connects to, so people reach your cloud gateway without typing its address. The screen has no URL field: with this key set, it shows your gateway URL and connects when the person presses Enter; without it, it tells them to contact their IT administrator.

In managed settings, either this key or forceLoginMethod: "gateway" makes the machine gateway-only, except for sessions that select a cloud provider with CLAUDE_CODE_USE_*. /login then opens on the Cloud gateway screen with no login-method picker. See Administrator policy requires a Cloud gateway sign-in for what happens to a leftover first-party login or API key. Set both keys so the screen connects instead of showing an error.

  • Scope: User or managed. Read from a managed source on the machine: managed-settings.json, the macOS plist or Windows HKLM registry, or a policy helper. On a machine with none of those, Claude Code v2.1.295 or later also reads it from user settings. Claude Code ignores it in HKCU and server-managed settings.
  • Type: string, a full URL including the scheme
  • Default: unset, so the Cloud gateway screen shows an error telling people to contact their IT administrator
{
  "forceLoginGatewayUrl": "https://claude-gateway.example.com"
}

If the value isn't a valid URL, the sign-in screen reports it, and the rest of the managed settings file still applies. See Set the gateway URL.

Documentation snapshot · 2026-11-20

Change details