Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.235 Home All releases ←olderv2.1.234 v2.1.236newer→
Claude Code v2.1.235

Full "account on hold" sign-in path built but switched off

Not switched on
Useful2 Signal5
Auth Notable

A complete sign-in flow for accounts on hold, with appeal links, sits in the build switched off.

An end-to-end on-hold login, retry and token-refresh path is built but its detector returns nothing unless a server flag reads true, fallback false.

Feature flag
tengu_lively_beaver Off in both readings

The flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.

This account: off · anonymous baseline: off · compiled default in v2.1.235: not a boolean we can read

Read once, for one account on one subscription tier, against v2.1.235. It isn't a statement about your account. What a flag value here can and cannot tell you

What

An end-to-end path for accounts placed on hold is present and unreachable in this build. It covers the login flow, the setup-token flow, API request retries and token refresh, with a login screen reading "Your account is on hold and can't use Claude Code. View details or appeal: " and a browser page reading "Your account is on hold. You can close this window." Every entry point goes through one detector that returns nothing unless the tengu_lively_beaver flag reads true; it is read with fallback false, so without a server value none of it runs.

Details
  • The local OAuth callback listener gained handling for ?error= redirects, which it previously ignored in favour of code only, serving a plain-text page. That branch also requires the gate.
  • The appeal URL is validated hard: https only, no port, userinfo or fragment, host must be claude.ai or anthropic.com or a subdomain. Anything else falls back to https://claude.ai/restricted.
  • Related events exist but stay unfired: api_request_account_on_hold, tengu_oauth_refresh_token_account_on_hold, and a tengu_oauth_error carrying account_on_hold: true.
  • The gate also decides whether "account_on_hold" is injected into the API error-kind list and the StopFailure hook matcher values, so with the gate off the hook matcher does not advertise it at all.
Evidence

Your account is on hold and can't use Claude Code. View details or appeal: , Your account is on hold. You can close this window., tengu_lively_beaver

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.235 →