[FEATURE] Remove or make the Max plan five-hour hard stop configurable

Problem

I pay for Claude Max 20x and routinely run five or more Claude Code sessions in parallel across separate tabs. The current five-hour usage window can stop all of that paid work one or two hours before the window resets, even when the workday still has substantial time remaining. The interruption is predictable enough to plan around, but the fixed boundary is not controllable by the subscriber and makes a multi-session workflow unnecessarily fragile.

Requested change

Please remove the recurring five-hour hard stop for Max plans, or provide a documented user-selectable allocation that preserves weekly/fair-use controls without forcing a mid-day interruption. At minimum, expose a clear per-account usage budget and reset boundary so subscribers can make an informed scheduling choice.

Acceptance criteria

• A normal paid Max workday is not forcibly interrupted solely because a five-hour rolling window ended.
• The remaining capacity, reset boundary, and any weekly/fair-use cap are visible and predictable.
• Usage is attributable per account and across parallel sessions, so one tab cannot silently consume an opaque shared allowance.
• When capacity is genuinely constrained, Claude Code explains the constraint and provides a documented recovery path.

Context and alternatives tried

I have tried spreading work across multiple sessions and switching between two Max accounts. I also use /usage, /clear, /compact, focused file references, and model selection to reduce avoidable context cost. These practices help, but they do not solve a hard stop that arrives during the workday. I use Codex with GPT-5.6 for this reason: in my workflow it does not impose the same recurring five-hour interruption. I am considering consolidating on Codex exclusively if Claude Code keeps making a paid, parallel-session workflow stop before the workday is over.

This is a product-policy request, not a claim that any provider should offer unlimited usage. Related reports about unexpectedly fast depletion, usage transparency, parallel-session accounting, and graceful continuation are useful evidence, but this request is specifically about giving Max subscribers a predictable, configurable window.

Related reports

• #55735 — Max 20x 5-hour session usage accounting disproportionately high with parallel sessions (closed user report)
• #54714 — Max 20x limits appear silently tightened (closed user report)
• #13354 — Continue when the session limit reached (open feature request)
• #67754 — Expose usage-limit reporting and hook points (open feature request)