# LLM.txt - Claude Code Weekly Limits After September 14: What Actually Changed ## Article Metadata - **Title**: Claude Code Weekly Limits After September 14: What Actually Changed - **URL**: https://www.llmrumors.com/news/claude-code-weekly-limits-september-2026 - **Publication Date**: September 22, 2026 - **Reading Time**: 5 min read - **Tags**: Claude Code, Anthropic, AI Agents, Developer Tools, Usage Limits, AI Subscriptions, AI Pricing, Software Development - **Slug**: claude-code-weekly-limits-september-2026 ## Summary Anthropic ended a 50% Claude Code weekly-limit promotion and kept a permanent 25% uplift. The practical change is smaller than a '25% cut' headline suggests. ## Key Topics - Claude Code - Anthropic - AI Agents - Developer Tools - Usage Limits - AI Subscriptions - AI Pricing - Software Development ## Content Structure This article from LLM Rumors covers: - Financial analysis and cost breakdown - Comprehensive source documentation and references ## Full Content Preview TL;DR: Anthropic's May 13 to September 13 Claude Code promotion lifted eligible weekly limits by 50%; from September 14 the permanent uplift is 25% above the pre-promotion baseline.[1] On a baseline index of 100, the allowance moved 100 → 150 → 125. That is a 16⅔% reduction from the temporary peak, not a 25% cut; five-hour limits and non-Code products were not part of this change.[1] The real story isn't a vanished benefit. It is Anthropic converting half of a temporary expansion into a standing one, then leaving users to distinguish a weekly Claude Code allowance from every other counter they see. A useful incident report has to identify which counter stopped work before anyone can explain why it happened. Eligible plans were Pro, Max, Team and legacy seat-based Enterprise; Free and consumption-based Enterprise seats were excluded.[1] A visible percentage alone does not establish a universal quota, a token conversion, or a policy change beyond Anthropic's published terms. The published percentages describe a weekly Claude Code policy, not a universal token quota. Check the active account and the window named in /usage before comparing two incidents. Cover image: generated editorial artwork of an antique mechanical balance holding three stacks of blank paper tokens, with a crimson measuring arm. It is a metaphor for allowance measurement, not a numeric diagram, Anthropic infrastructure or measured usage. The Arithmetic: A Smaller Rollback Than the Headline This table is an editorial index, not tokens or messages. Set the original weekly Code allowance to 100. The promotion added 50%, producing 150. The permanent policy adds 25% to the original baseline, producing 125. | Period | Weekly allowance index | Change from baseline | Change from promotional peak | | --- | ---: | ---: | ---: | | Before May 13 | 100 | 0% | -33⅓% | | May 13–September 13 promotion | 150 | +50% | 0% | | From September 14 | 125 | +25% | -16⅔% | The calculation is (150 - 125) / 150 = 1/6, or 16⅔%. Calling the change a 25% cut confuses the permanent amount, measured against the original 100, with the decline from 150. Calling it a return to normal misses the retained 25 points. Both errors make capacity planning worse. Anthropic did not publish a universal weekly token allotment in the notice. Workload length, model choice, effort and features affect usage, according to the broader limits guide.[2] Reading an Incident: Name the Clock First A short-window reset and a weekly stop are different incidents. Record the actual message before choosing an explanation. Start with the named window, reset time and signed-in account. Claude Code's /usage command is Anthropic's documented place to inspect plan limits and current rate-limit status.[6] | Question | Evidence to inspect | What it can establish | | --- | --- | --- | | Which window generated the notice? | Reset label and time | Whether it is a short or weekly capacity event | | Is capacity shared? | Product and account context | Claude and Claude Code can draw from the same plan usage | | Is this subscription use? | Authentication route | A subscription and an API key bill differently | Avoid inventing a personal quota from a progress bar. Anthropic's public material explains the rules and inputs to usage; it does not provide a stable conversion from an index point to a specific number of tokens, prompts or agent turns for every account. Shared Capacity: Code Is Not a Separate Island For Pro and Max, Anthropic says activity in Claude and Claude Code counts against shared usage limits, including supported IDE use.[3] Its general limits guide also names Claude web, Code and Desktop as surfaces drawing on the same usage limit.[2] Billing Route: Subscription, ... [Content continues - full article available at source URL] ## Citation Format **APA Style**: LLM Rumors. (2026). Claude Code Weekly Limits After September 14: What Actually Changed. Retrieved from https://www.llmrumors.com/news/claude-code-weekly-limits-september-2026 **Chicago Style**: LLM Rumors. "Claude Code Weekly Limits After September 14: What Actually Changed." Accessed September 22, 2026. https://www.llmrumors.com/news/claude-code-weekly-limits-september-2026. ## Machine-Readable Tags #LLMRumors #AI #Technology #ClaudeCode #Anthropic #AIAgents #DeveloperTools #UsageLimits #AISubscriptions #AIPricing #SoftwareDevelopment ## Content Analysis - **Word Count**: ~1,038 - **Article Type**: News Analysis - **Source Reliability**: High (Original Reporting) - **Technical Depth**: High - **Target Audience**: AI Professionals, Researchers, Industry Observers ## Related Context This article is part of LLM Rumors' coverage of AI industry developments, focusing on data practices, legal implications, and technological advances in large language models. --- Generated automatically for LLM consumption Last updated: 2026-09-22T13:51:07.403Z Source: LLM Rumors (https://www.llmrumors.com/news/claude-code-weekly-limits-september-2026)