Omniscio

OmniscioGuidesAccount on hold

Claude Code: your account is on hold

Last checked against Anthropic's documentation on November 18, 2026. By the Omniscio team. Updated .

What is the exact message?

Your account is on hold and can't use Claude Code. View details or appeal: https://claude.ai/restricted
Your account is on hold and can't sign in to Claude Code. View details or appeal: https://claude.ai/restricted

The first form appears when Claude Code tries to renew your saved login and learns of the hold. The second appears when a sign-in you completed in the browser reports it.

What does it mean?

The Claude account behind your login has been suspended. The hold sits on the account, not on the login, so clearing the login and signing in again with the same account returns the same message.

In a non-interactive run (-p) or an Agent SDK application the structured error code is account_on_hold. Before Claude Code v2.1.235, a held account was reported as Login expired, whose recovery steps cannot clear a hold — so an older build can send you down the wrong road.

Why it appeared

  • The account was suspended. Anthropic's entry says the account behind the login has been suspended; the message itself is how Claude Code learns of it.
  • It is not a usage limit. A hold is a suspension of the account. Reaching a plan or usage limit is a different message with a different fix, covered in the Claude Code usage limits guide.

What can I do about it?

  1. Open the link in the message. https://claude.ai/restricted is where the hold's details are, and where an appeal is filed.
  2. Do not keep signing in with the same account. The hold is on the account, so the same sign-in returns the same message.
  3. If you have another Claude account that is not affected, sign in with it. Run /login and choose the other account.
  4. If you have an API key that is not affected, use it. Set ANTHROPIC_API_KEY before starting Claude Code, and the session authenticates with the key instead of the held account. In an interactive session Claude Code asks once whether to use the key, and remembers your answer.

How do I know it is fixed?

  • The next request in a session signed in with the other account or the API key succeeds.
  • /status shows the account or key you are actually using.
  • After an appeal succeeds, a sign-in with the restored account starts a session instead of returning the message.

Where these answers come from

  • Both message forms, when each appears, the suspension, the account_on_hold code, the earlier Login expired behaviour, and the appeal and alternative-credential steps: Anthropic's error reference, read November 18, 2026.
  • The precedence of ANTHROPIC_API_KEY over a saved login: Anthropic's authentication page, read November 18, 2026.

Common questions

Does signing in again clear an account hold?

No. The hold is on the account rather than on the login, so signing in again with the same account returns the same message. The message's link is the way to view the hold or appeal it.

Where does the message appear?

The first form appears when Claude Code tries to renew your saved login and learns of the hold. The second appears when a sign-in you completed in the browser reports it.

Can I keep working while the hold is resolved?

Yes, if you have another Claude account or an API key that the hold does not affect. Run /login with the other account, or set ANTHROPIC_API_KEY before starting Claude Code.

What does a non-interactive run report?

In -p runs and the Agent SDK the structured error code is account_on_hold. Before Claude Code v2.1.235, a held account was reported as Login expired, whose recovery steps cannot clear a hold.