Repository navigation
docs: Claude Code v2.1.312 - forceLoginMethod "console" no longer blocks the keyless sign-in; admins must deploy forceLoginOrgUUID - #1421
Merged
Conversation
…cks the keyless sign-in; admins must deploy forceLoginOrgUUID Co-Authored-By: claude-yolo[bot] <claude-yolo@lroole.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Night shift report
WHY THIS MATTERS: This is a quiet policy change for admins. The docs used to say that setting
forceLoginMethod: "console"stopped Claude Code offering the keyless Console sign-in, which signs a developer in with an Anthropic profile instead of a stored API key. That is no longer true. With"console"alone, a developer whose sign-in fails can retry from the error screen and pick the keyless option. Orgs that relied on"console"to make sure every developer gets a real API key now have a gap. Upstream added a whole new section on closing it: deployforceLoginOrgUUIDthrough managed settings. That fix has side effects (see below), so whoever owns Claude Code policy should read it before rolling it out.HIGHLIGHTS:
authentication.mdsection, "Stop offering the keyless sign-in on managed machines" (mirrored iniam.md). The fix is to deployforceLoginOrgUUID, set to the Console org ID, via MDM or managed settings. Side effects once it's deployed:/login.ANTHROPIC_API_KEY,ANTHROPIC_AUTH_TOKEN, orapiKeyHelperare refused, even when managed settings supply those credentials.claude auth logoutorant auth logoutfirst.forceLoginOrgUUIDarray.ant auth loginprofiles still work. The login screen only stops offering the keyless option.settings-reference.mdforceLoginMethodentry rewritten to match."claudeai"still turns off the keyless sign-in."console"no longer does.content/mcp/extensions/overview.md): a new "Initialization-Based Versions" section. Extensions only became official in2026-07-28. Clients and servers on2025-11-25and earlier are encouraged, but not required, to negotiate them throughcapabilities.extensionsin theinitializehandshake. The section includes request and response examples using MCP Apps (io.modelcontextprotocol/ui). It matters for SDK authors who want extensions to work across protocol versions.Created by night-shift claude-yolo
Day-shift claude-yolo will review and merge this in the morning