Consumer Terms Gate
What happens when an account must accept updated Consumer Terms and Privacy Policy at claude.ai before the API will serve it: instead of retrying forever, the session stops cleanly, says exactly what is wrong, and that account is kept out of the pool so other sessions are unaffected. Covers the four-step fix and why the detection is deliberately narrow.
On this page
What it is
When Anthropic updates its Consumer Terms & Privacy Policy, every account must accept the new terms at claude.ai before the API will serve requests. Until accepted, the API returns a specific 400 error. Omniscio detects this error automatically — instead of retrying in a loop, it stops the session cleanly, tells you exactly what happened, and keeps the gated account out of the session pool so other sessions aren't affected.
You'll see this as a session that transitions to "Needs You" with a message like: "The Anthropic account you@example.com needs to accept updated Terms & Privacy Policy. Open claude.ai, sign in and accept the terms, then click "I've accepted the terms" on the card in your inbox." An inbox card appears with the same guidance, and its second button is that click.
Where to find it
You do not go looking for this — it comes to you. The session that hit the gate turns amber in the sidebar with the word "Needs You" and carries the explanation in its chat, and the same wording also arrives as a card in your inbox. The card carries two buttons: Open claude.ai (where you accept the terms) and I've accepted the terms (which lets that account run again).
How it behaves
How to fix it
- Open claude.ai — the card's Open claude.ai button takes you there
- Sign in with the account shown in the message
- Accept the updated terms when prompted
- Click I've accepted the terms on the card
No settings change is needed, and no restart. Step 4 is what clears the gate: accepting the terms at claude.ai does not tell Omniscio anything on its own, and the account is held out of the pool meanwhile, so the click is the only thing that lets it back in.
If the terms were not actually accepted, nothing is broken — the next turn on that account hits the same 400, the account is gated again, and the same card comes back. One card, never a loop.
If you would rather not click, restarting Omniscio also clears it (the gated state is in-memory only) — but the button is the intended road, and the card says so.
How it works
The Claude CLI wraps API errors as "synthetic placeholder" events — assistant messages with model: "<synthetic>" and zero output tokens. Normally, Omniscio's placeholder-stuck watchdog auto-replays these as empty turns. But the Consumer-Terms 400 can never succeed via replay (it's a server-side gate), so the watchdog would loop until it exhausts retries, then show a misleading generic error.
The fix works in four steps:
- Detection, and the account is gated right there.
isConsumerTermsGate400matches the specific error text ("consumer terms" + "accept them in claude.ai") in the synthetic event. That moment IS "the first Consumer-Terms 400", so the account is added to the in-memory gated set at detection — not later, and not only when the turn happens to have a particular shape. - Terminal sink.
fireAccountNeedsTermskills the CLI, emits a clear system message, and transitions the session toneeds_you/recovery_failed. No auto-replay, no cross-account fallback. The route is decided by the error class, so it fires whatever shape the turn took. - Pool exclusion, on every surface that judges the pool. The load-balancer, the pre-spawn picker, its single-account fast path, the pool-exhaustion classifier and the last-resort account fallbacks all ask one shared predicate, so a gated login is refused everywhere rather than in most places.
- Inbox card, and the way out. One deduped alert per gated account explains what to do, and carries the I've accepted the terms button that clears that one account's mark. Without it the account would be refused by the picker and therefore never able to run the turn that would clear it — a dead end only a restart could open.
The detection is intentionally narrow — only the specific Consumer-Terms text matches, so an ordinary 400 gates nothing. Generic 400 errors fall through to the existing paths (fail-open).
Related
The nearest neighbour in behaviour is aborted response recovery, which uses the same shape — a specific synthetic event detected and routed to a terminal sink rather than replayed. The pool exclusion rides on the account model described on the account pool page, and the other state an account can be parked in, a rate limit, is covered by account relogin.
- Account Terms Gate Contract
- Aborted Response Recovery — similar pattern (synthetic event detection + terminal sink)
Last verified 2026-10-11