AI / GenAI·6 min·23 August 2026

Claude Code weekly limits stay 50% higher, now through August 31

I schedule my heavy work right after my weekly limit resets. Not because I think more clearly then, but because that is when I have a full tank for an agent that spends two hours grinding through a repo. I built that rhythm during the months when the limit sat 50% above what my plan actually promises. On Tuesday evening it turned out that rhythm survives a little longer, through August 31.

On August 18, Anthropic announced that the temporary increase to Claude Code’s weekly limit runs through August 31, 2026. That is the fourth extension of the same promotion. The same two sentences carry something the previous three did not. The company hopes to make this permanent, and demand for its models is strong enough that capacity may be tight over the coming weeks. Those two statements do not usually travel together.

What changes, and what does not

Claude Code enforces two limits that run independently, and almost every confusing news post about this topic comes from someone mixing them up.

5-hour windowWeekly limit
What it catchesshort, intense burstssustained heavy use across a week
Resetrolling, starts at your first messagefixed point, every 7 days
In place sincethe beginningAugust 28, 2025
Touched by this promotionnoyes, 50% higher

The promotion only moves that second column. Your 5-hour window is unaffected, and that window was permanently doubled on May 6 anyway, which was a separate decision with a separate reason behind it.

The rest of the fine print, taken from Anthropic’s own help article:

  • Period. May 13, 2026 through August 31, 2026, 11:59 PM PT.
  • Where. Claude Code only, everywhere you use it: CLI, IDE extensions, desktop, and web. Claude on web, desktop, and mobile is unchanged, and so is Claude Cowork, which had its own temporary boost back in June.
  • Who. Pro, Max, and Team, plus legacy seat-based Enterprise users. Not Free, not consumption-based Enterprise seats.
  • What you do. Nothing. If you are on an eligible plan, it is already applied.
  • After. The limit returns to your plan’s standard level. Nothing changes about your plan or your billing.

The numbers you need to weigh this

The weekly limit has existed since August 28, 2025. When Anthropic announced it on July 28, 2025, the justification was that it would affect “less than 5% of subscribers based on current usage.” That figure is a year old and has never been updated. Claude Code usage has not held still over that year, so the honest reading is that nobody outside Anthropic knows what share of users hits the ceiling today.

The weekly budgets published at the time, in hours per week:

PlanSonnet per weekOpus per week
Pro, $2040 to 80 hoursnot included
Max, $100140 to 280 hours15 to 35 hours
Max, $200240 to 480 hours24 to 40 hours

Notice the spread. The gap between 140 and 280 hours is a factor of two, and where you land inside that range depends on how heavy your sessions are. The table also describes Sonnet 4 and Opus 4, the models of August 2025. Today’s models consume differently, so treat these numbers as an order of magnitude rather than a budget you can plan against. The only figure that describes your account comes from running /usage in the CLI.

The number that flatters Anthropic least is the count of extensions. The promotion started on May 13 with a July 13 end date, moved to July 19, then to August 19, and now to August 31. Four extensions of a few weeks each mostly tell you that someone reassesses, period by period, how much can be handed out.

Why a promotion instead of a plan change

To a user, a temporary promotion and a permanent increase look identical. To the provider they are completely different objects.

A permanent increase is a promise. You have to honor it on your worst day, with your busiest customers, on the model that burns the most compute. A promotion only has to hold until the end date you picked yourself. As long as compute supply is uncertain, a promotion is the only honest instrument a provider has.

That lines up with what happened in May. On May 6, Anthropic did permanently double the 5-hour window, and that announcement was explicitly tied to a new capacity deal: access to a data center bringing more than 300 megawatts of new capacity, over 220,000 GPUs, within the month. The weekly limit promotion arrived a week later, temporary. So the permanent part only landed once the power was there. The weekly limit is still waiting for a foundation of its own.

The caveat

The baseline shifts without anyone promising anything. A promotion extended four times starts to feel like the normal level after three months. Your planning quietly settles around a number that is formally temporary, and in my case that has hardened into one fixed morning a week. Anthropic’s help article is explicit that the limit reverts afterward. Reading that as “they will extend it again” means building your work week on an assumption nobody has committed to.

The risk lands on you. “Capacity may be tight” is a polite sentence, but it is also a transfer. You have to keep headroom, you have to have a fallback, and you are the one who finds out mid-session. The side that can actually act on capacity is the side that sees the numbers and does not share them.

Wider limits cost electricity, even when you pay nothing extra. May’s permanent doubling was tied to hundreds of megawatts of new data center capacity. A wider limit gets paid for in energy somewhere, even when your invoice never shows it. That belongs in your calculation, right alongside how much of your work you move into a single vendor’s window and how much it hurts when that window shrinks.

What I do myself

I am not building my pipeline on this extra headroom. The heavy work that has to run every week, the content gates and the scheduled checks, fits inside the standard limit and stays there. I spend the promotional headroom on the experimental side: several agents running in parallel, a large refactor, an afternoon of grinding through one repo. That is exactly the work I can postpone after August 31 without breaking anything.

Beyond that, I am checking before August 31 whether there is anything heavy I would rather do now, and I run /usage at the start of the week instead of at the moment I get stuck. The second habit is dull, but it saves me the irritation of an agent that stalls halfway through.

Frequently asked questions

Do I have to turn anything on to get the higher weekly limit?

No. If you are on Pro, Max, Team, or a legacy seat-based Enterprise seat, the increase is already applied to your account. Run /usage in the CLI to see what actually applies to you right now.

Does this change my 5-hour limit too?

No. This promotion touches the weekly limit only. The 5-hour window was permanently doubled on May 6, 2026, which is a separate change.

Does it apply to Claude on the web, or to Cowork?

No. The increase covers Claude Code only, in every environment where you use it. Claude on web, desktop, and mobile keeps its own limits, and so does Cowork.

What happens on September 1?

Your weekly limit in Claude Code returns to your plan’s standard level. Nothing changes about your plan or your billing, only about how much work fits inside it.

Sources

  • @ClaudeDevs on X, announcing the extension through August 31, August 18, 2026
  • @ClaudeDevs on X, the earlier extension through August 19, July 18, 2026
  • Anthropic Help Center, “Claude Code May–August 2026 weekly limits promotion”, accessed August 19, 2026
  • Anthropic, announcement of the permanent 5-hour limit doubling and the capacity deal behind it, May 6, 2026
  • TechCrunch, “Anthropic unveils new rate limits to curb Claude Code power users”, July 28, 2025
  • Help Net Security, “Claude Code users keep 50% higher limits until July 19”, July 13, 2026

Checked on August 19, 2026. The period, the eligibility, and the fine print come from Anthropic’s own help article, which at that moment carried “May–August 2026” in its title and named August 31 as the end date. One thing does contradict itself: on X, Anthropic says it hopes to make the change permanent, while the help article states flatly that the limit returns to standard after August 31. I follow the primary source, so: temporary until the opposite is written down. The hours-per-week table dates from August 2025 and describes Sonnet 4 and Opus 4; I found no more recent official table, so I could not verify those numbers for today’s models. The “less than 5%” figure has never been updated, so I have treated it as a 2025 snapshot rather than a current measurement.