[adampeterhiggins]

Claude currently continues into paid extra usage after subscription allowances are exhausted. Add Stop at subscription limit in Settings > General (mobile: Settings > Threads > Usage limits) to protect all Claude threads, including delegated work, when leaving the app running unattended. The application setting overrides thread-level Off and immediately rechecks running sessions when enabled. Both application-wide and per-thread settings default to Off.

Protected turns make a fresh, prompt-free usage check before starting. Exhausted allowance or streamed overage signals close the Claude process and its native background work. Unavailable usage also blocks the turn rather than proceeding unchecked. These active-turn stops use the existing Limited status and chat recovery controls: Resume now, Resume at reset, Snooze until reset, and Continue in new tab. Resume now keeps the guard; a user must change provider or disable the application and thread restrictions to permit paid extra usage.

A thread's own option can also be switched from its right-click menu (Stop at subscription limit > On / Off) in the web/desktop sidebar and chat header, and from the long-press menu on mobile. The menu notes when the application setting already covers every thread. On web, the toggle also updates the composer's unsent model pick, so the next message keeps the new value. The thread option applies from the next turn; the application setting is the way to stop a turn already in progress.

The policy is enforced by the server and remains active when clients disconnect. Individual thread model options remain available when the application setting is Off; their normal same-provider-and-model inheritance is unchanged. Other providers are not covered yet. Provider reporting can lag, so this is a spending guard rather than a guaranteed billing cap.

Validation:

• 683 focused tests passed across the Claude adapter, provider registry, settings contracts, cross-environment settings sync, mobile setting scope, and web default restoration (5 browser tests).
• Typechecks passed for server, web, mobile, contracts, and client-runtime. Targeted lint passed with two existing warnings.
• Integrated browser verification used an isolated dev instance and a prompt-free local Claude fixture reporting exhausted usage. The application setting was On while the thread option was Off. The persisted error was usage_limit / subscription_limit_guard, and the actual sidebar showed Limited.
• Verified scheduling and cancelling resume-at-reset, and verified Resume now stops again while the allowance remains exhausted. The fixture was removed afterward; no scheduled test continuation remains. Native mobile was typechecked but not launched.
• Thread menu toggle: menu-builder and shared helper tests (34), plus web, mobile, and client-runtime typechecks. Not yet exercised in a running client.
• Updated the Claude user guide and fork differences.

The screenshots below show actual application state from that guard-triggered turn, using simulated provider allowance data rather than editing UI projections.

Application-wide setting

Guard-triggered stop: Limited sidebar label and normal recovery controls

Resume at reset armed: scheduled continuation and Cancel auto-resume

Model: gpt-6.1-sol (Codex in T3 Code); thread menu toggle by Claude Opus 5.5 (Cursor in T3 Code).