Skip to content

developer-tools

1 post with the tag “developer-tools”

Anthropic Calls It a Permanent 25% Raise. Your Claude Code Meter Drops 17% on September 14

Anthropic’s Claude Code announcement reads like a win. Starting September 14, weekly limits go up 25% for Pro, Max, Team, and seat-based Enterprise plans. Permanently. Set that headline next to the meter in your terminal and the story inverts: what you get drops about 17% against today (BleepingComputer).

Both numbers are true. Only one of them lands on your usage bar.

Claude Code’s weekly allowance has been running on a temporary 50% boost. Anthropic’s developer account announced the change on X on August 29: “Starting September 14, we’re permanently raising standard weekly limits in Claude Code by 25% for Pro, Max, Team, and seat-based Enterprise plans. Until then, the current 50% increase will be in place.” (Anthropic on X)

Limit stateValue (baseline = 100)
Original weekly baseline100
Today, with the temporary boost150
From September 14, permanent125
Change vs. pre-promo baseline+25%
Change vs. today’s meter-17%

If your plan’s original weekly allowance was 100 units, you get 150 today. On September 14, that becomes 125. You end with a quarter more than the old baseline and a sixth less than what you are burning right now (BleepingComputer).

The framing did not survive contact with users. Readers attached context notes to the announcement, and community members called out the post for leading with the gain while leaving out the net reduction. Anthropic employees conceded the messaging could have led with the change (X). The company then deleted the original thread and published a clarification that states the number outright: “Compared to today, this works out to a 17% reduction in weekly limits on Claude Code.” It added that it is working on changes that give users “more visibility and control” over usage (Windows Report).

Theo of t3.gg posted a public reply coaching Anthropic on announcement writing: lead with the delta from the meter users see today, not the baseline nobody remembers (X).

The temporary 50% boost was never built to last. It was scheduled to end August 31, and Anthropic extended it twice, most recently to September 14 (explainx.ai). A promotion inflates a baseline. When it ends, the meter drops even though the underlying limit never moved. For anyone who budgeted against 150, the switch to 125 reads as a cut, because against their working number it is one.

The frustration runs deeper than one post. Through July and August, users reported weekly allowances draining faster than expected. One report from August 15 describes a two-hour session consuming an entire five-hour window plus 17% of a weekly limit. A user on the $200-per-month Max 20x plan said a fresh subscription hit its weekly cap after roughly two and a half hours (Uprise RI). A federal lawsuit over how Anthropic marketed its Max plan multipliers sits in the background (explainx.ai).

Anthropic’s position is that usage varies by conversation length, model choice, tool usage, and effort level, so no weekly allowance translates into a fixed number of prompts (BleepingComputer). That is honest arithmetic. It also means the only number you can trust is the one in your own terminal.

The debate is still live. On Hacker News this weekend, the defense of Anthropic is simple: the boosted amount was always temporary, and the app said so every time it opened (Hacker News). The complaint is just as simple: “25% more” and “17% less” describe the same event, and the announcement picked the flattering one (Hacker News).

  1. Re-baseline your budgets at 125. If you plan agent capacity against today’s 150, every week after September 14 goes over. Update the runbooks and the cost sheets now.
  2. Spend promo capacity on real work this week. Long refactors and bulk migrations burn weekly allowance fastest. Run them before September 13.
  3. Check /usage, not the docs. Anthropic says allowances do not map to a fixed prompt count. Your meter is the only live number.
  4. Read every limit announcement against the current meter. Percentages need a reference point. Ask which one the sender is using. If the announcement anchors on the baseline and your meter anchors on a promo, expect the smaller number to win.

Anthropic frames the change as sustainability: “Thanks for hanging with us while we figured out what we can sustainably serve going forward” (Anthropic via Hacker News). Subsidized 150% capacity was never going to last, and operators know subsidized capacity when they see it.

The order of operations still matters. State the cut first, then the raise. Teams plan against the meter in front of them. An announcement that anchors on the baseline and buries the delta spends trust to save a headline. Developers noticed in hours. Your users will too.