Follow Discord
Sweep 25 Sep 2026 · 19:33Z Build v2.1.283 504 read Stable v2.1.274 Latest v2.1.283 Next v2.1.283 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.283 ·

Compliance-restricted accounts no longer get a misleading sign-in failure

Access refusals caused by compliance or zero-data-retention restrictions are now treated as "unavailable" rather than as unauthorised

You'll notice Bug Fixes
JSON All of v2.1.283
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
Bug FixesKind: in v2.1.283,
Bug FixesSection of the release
What

Sometimes a remote service refuses a request with a 403, meaning access denied. If the refusal says the resource is restricted for compliance or zero data retention, Claude Code now treats the feature as unavailable because of a compliance restriction. Zero data retention is an arrangement where Anthropic does not keep your data. Before, it treated these refusals as a failed login. Other 403 refusals are still treated as unauthorised. This handling sits alongside directory sync.

Why

If your organisation is compliance-restricted, you should now see a restriction message rather than an authentication failure that points you in the wrong direction.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtExactly which remote feature this applies to is not known.

See this entry in the whole of v2.1.283 →

Feedback