Claude Desktop v1.21459.0: bootstrap-delivered config suppresses deployment-mode chooser (Claude.ai login no longer offered)

Open 💬 0 comments Opened Jul 15, 2026 by josefwsieber

Summary

In Claude Desktop v1.21459.0 (Windows), when managed configuration is delivered via a bootstrap URL, the login screen shows only the organization / gateway (bootstrap OIDC) sign-in. The Claude.ai (Pro/Max subscription) login option is no longer presented.

Delivering the same managed settings via registry policy (HKLM\SOFTWARE\Policies\ClaudeCode) — i.e. without bootstrapUrl / bootstrapEnabled — behaves correctly: the deployment-mode chooser appears and both login options are offered.

This is a regression. On an earlier build, a bootstrap-configured client still presented the deployment-mode chooser with both options.

Expected behavior

With disableDeploymentModeChooser unset (its default), the deployment-mode chooser should appear and offer both the Claude.ai subscription login and the managed/gateway login — regardless of whether the managed config is delivered by bootstrap URL or by registry policy.

Actual behavior

When a bootstrap URL is configured, the app forces the interactive-auth state to the bootstrap/gateway method and skips the chooser entirely. The Claude.ai login option never renders. Signing out does not restore it — the deployment mode is persisted as 3p and is preserved across logout, so relaunching returns to the gateway-only login.

Trigger

The behavior keys off the presence of bootstrapUrl + bootstrapEnabled. When both are set, the bootstrap layer claims the single interactive-auth slot (bootstrapOwnsInteractiveAuth() returns true) and the chooser is bypassed. When those keys are absent (e.g. registry-delivered config), bootstrap is treated as "unconfigured" and the chooser renders normally.

Notably, disableDeploymentModeChooser, disableClaudeAiSignIn, and forceLoginMethod are all unset — nothing is explicitly disabling subscription login; the bootstrap path suppresses it implicitly.

Impact

Users on a bootstrap/gateway-configured client cannot sign in with their personal Claude subscription, and there is no in-app path back to the chooser.

Notes

  • The published Claude Desktop 3P configuration changelog stops at v1.20186.0 (2026-07-09); v1.21459.0 is newer and this behavior change is not documented there.
  • Suggested fix: bootstrap-delivered config should honor the deployment-mode chooser the same way registry-delivered config does, when disableDeploymentModeChooser is unset.

Environment

  • Claude Desktop v1.21459.0
  • Windows 11
  • Managed (third-party / gateway) deployment

View original on GitHub ↗