How Claude Code's Weekly Usage Limit Works and How to Avoid Hitting It
Claude Code enforces two overlapping usage limits: a rolling 5-hour window that resets after a short wait, and a harder weekly cap that can lock users out for days regardless of how long they wait. Both limits draw from a shared pool that covers Claude Code, claude.ai chat, and Cowork simultaneously, meaning activity outside the coding tool still depletes the same budget. Usage drains faster than expected because Claude Code sends the full conversation history with every request, making long sessions, cache misses after breaks, and compaction operations particularly costly. Background agent tasks and parallel teammates can consume roughly seven times the tokens of a normal session, silently exhausting the weekly allowance. Users can monitor both limits, reset times, and per-feature usage attribution in real time by running the built-in /usage command or visiting the Usage section in claude.ai settings.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in