Follow Discord
Sweep 29 Sep 2026 · 18:10Z Build v2.1.285 506 read Stable v2.1.280 Latest v2.1.285 Next v2.1.285 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.285 ·

Admins can restrict sign-in providers with a new allowedProviders setting

A new allowedProviders managed setting can block claude auth login and setup-token when the policy disallows Anthropic's own sign-in

Use it now New Features
JSON All of v2.1.285
Use it nowTier: how much it should matter to you
4Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Managed SettingsArea: what it touches
New FeaturesKind: in v2.1.285,
What probably matters to youSection of the release
What

Managed settings are settings an administrator puts in place on a machine. They gain an allowedProviders key. When it does not permit the first-party provider, meaning signing in directly with Anthropic, these commands refuse to run:

  • claude auth login
  • setup-token, which creates a long-lived Claude.ai subscription token

If the value of allowedProviders is invalid, the settings check reports it and asks you to fix it.

Why

Administrators get control over which sign-in providers can be used on a machine. If sign-in is refused, this policy may be why.

Read from
Names in the bundleallowedProviders
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agreeAdded allowedProviders managed setting to limit which API providers a machine may use (Anthropic API, a custom endpoint, Bedrock, Mantle…

See this entry in the whole of v2.1.285 →

Feedback