OAuth failures whose body carries an account_on_hold error are now recognised as their own kind rather than being folded into invalid_grant/refresh handling. Refresh classification returns account_on_hold, the retry path stops retrying, and a dedicated OAuthAccountOnHoldError (message "OAuth account is on hold") is thrown carrying an appeal URL. account_on_hold is spliced into the API-error union and the login-screen error list, and affected users would see text built around "Your account is on hold and can't use Claude Code. View details or appeal: " with a claude.ai/restricted-style URL. All detection short-circuits to null unless the controlling gate reads true.
The flag server returned off for both this site's account and the anonymous baseline, and no reading has been taken under this release yet.
tengu_lively_beaver Off in both readingsThe 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
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.