You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
ElsewhereArea: what it touches
ImprovementsKind: in v2.1.284,
ImprovementsSection of the release
What
An organisation can use managed settings (settings an administrator installs on the machine) to require a particular way of signing in, using forceLoginMethod, forceLoginOrgUUID or a cloud gateway requirement. If your session is set up with a different credential, Claude Code now shows a detailed message. It names the credential and where it came from:
a credential supplied by the app hosting Claude Code
--bare, which turns first-party sign-in off, so there is no sign-in at all
The message says which settings file's env block set the credential and suggests specific fixes, such as removing the key from that block or asking your administrator. It also includes a note for administrators: on a third-party desktop session, forceLoginOrgUUID and forceLoginMethod apply to first-party sign-in and should be removed from that machine's managed settings.
Why
If your credentials and your organisation's sign-in policy disagree, you now see which file to change instead of a plain refusal.
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agreeImproved the startup refusal when managed settings require a sign-in (forceLoginMethod or forceLoginOrgUUID) and an API key, token or…
