We've just reset weekly limits for all Claude users on paid plans.

We've seen members of this community hitting their weekly usage limits more quickly than they might have expected. This is driven by usage of Opus 4.1, which can cause you to hit the limits much faster than Sonnet 4.5.

To help during this transition, we've reset weekly limits for all paid Claude users.

Our latest model, Sonnet 4.5 is now our best coding model and comes with much higher limits than Opus 4.1. We recommend switching your usage over from Opus, if you want more usage. You will also get even better performance from Sonnet 4.5 by turning on "extended thinking" mode. In Claude Code, just use the tab key to toggle this mode on.

We appreciate that some of you have a strong affinity for our Opus models (we do too!). So we've added the ability to purchase extra usage if you're subscribed to the Max 20x plan. We’ll put together more guidance on choosing between our models in the coming weeks.

We value this community’s feedback. Please keep it coming – we want our models and products to work well for you.

Latest Performance Report: https://www.reddit.com/r/ClaudeAI/comments/1n4o701/claude_performance_report_with_workarounds_august/

Full record of past Megathreads and Reports : https://www.reddit.com/r/ClaudeAI/wiki/megathreads/

Why a Performance Discussion Megathread?

This Megathread should make it easier for everyone to see what others are experiencing at any time by collecting all experiences. Most importantly, this will allow the subreddit to provide you a comprehensive periodic AI-generated summary report of all performance issues and experiences, maximally informative to everybody. See the previous period's performance report here https://www.reddit.com/r/ClaudeAI/comments/1n4o701/claude_performance_report_with_workarounds_august/

It will also free up space on the main feed to make more visible the interesting insights and constructions of those using Claude productively.

What Can I Post on this Megathread?

Use this thread to voice all your experiences (positive and negative) as well as observations regarding the current performance of Claude. This includes any discussion, questions, experiences and speculations of quota, limits, context window size, downtime, price, subscription issues, general gripes, why you are quitting, Anthropic's motives, and comparative performance with other competitors.

So What are the Rules For Contributing Here?

All the same as for the main feed (especially keep the discussion on the technology)

• Give evidence of your performance issues and experiences wherever relevant. Include prompts and responses, platform you used, time it occurred. In other words, be helpful to others.

• The AI performance analysis will ignore comments that don't appear credible to it or are too vague.

• All other subreddit rules apply.

Do I Have to Post All Performance Issues Here and Not in the Main Feed?

Yes. This helps us track performance issues, workarounds and sentiment and keeps the feed free from event-related post floods.

Currently my main AI tool develop with is cursor. Within the subscription I can use it unlimited, although I get slower responses after a while.

I tried Claude Code a few times with 5 dollars credit each time. After a few minutes the 5 dollar is gone.

I don't mind paying the 100 or even 200 for the max, if I can be sure that I van code full time the whole month. If I use credits, I'd probably end up with a 3000 dollar bill.

What are your experiences as full time developers?

I've been using Claude Code for two months so far and have never hit the limit. But yesterday it stopped working and gave a cooldown for 4 days. If its limit resets every 5 hours, why a cooldown for 4 days? I tried usage-based pricing, and it charged $10 in 10 minutes. Is there something wrong with new update of Claude code?

Hey everyone,

Not sure what’s going on, but starting today, I’m suddenly hitting my usage limits after only a few non coding related prompts (like 3–4). This has never happened before.

I didn’t change my plan, my workflow, or the size of my prompts. I’m using Claude Code normally, and out of nowhere it tells me I’m at my limit and blocks further use.

A couple things I’m trying to figure out:

• Is this happening to anyone else today specifically?

• Did Anthropic quietly change the quota calculations?

• Could it be a bug or rate-limit miscount?

• Is there any workaround people found? Logging out, switching networks, switching country, etc.?

It’s super frustrating because I literally can’t work with only a few prompts before getting locked out.

If anyone has info or experienced the same thing today, please let me know.

Thanks!

This Megathread is a continuation of the discussion of your thoughts, concerns and suggestions about the changes involving the Weekly Usage Limits implemented alongside the recent Claude 4.5 release. Please help us keep all your feedback in one place so we can prepare a report for Anthropic's consideration about readers' suggestions, complaints and feedback. This also helps us to free the feed for other discussion. For discussion about recent Claude performance and bug reports, please use the Weekly Performance Megathread instead.

Please try to be as constructive as possible and include as much evidence as possible. Be sure to include what plan you are on. Feel free to link out to images.

Recent related Anthropic announcement : https://www.reddit.com/r/ClaudeAI/comments/1ntq8tv/introducing_claude_usage_limit_meter/

Original Anthropic announcement here: https://www.reddit.com/r/ClaudeAI/comments/1mbo1sb/updating_rate_limits_for_claude_subscription/

Anthropic's update on usage limits post here : https://www.reddit.com/r/ClaudeAI/comments/1nvnafs/update_on_usage_limits/

Last week's Megathread: https://www.reddit.com/r/ClaudeAI/comments/1nu9wew/usage_limits_discussion_megathread_beginning_sep/

Megathread's response to Anthropic's usage limits update post here:

https://www.reddit.com/r/ClaudeAI/comments/1o1wn34/megathreads_response_to_anthropics_post_update_on/

I’ve seen a lot of mixed reports about hitting weekly usage limits on Claude.
Some people say it happens with Claude Pro (web), others never hit any limit when using Claude Code.

So I’d like to get a clearer picture from actual users here.

I’ll summarize results later for everyone — hopefully we can see if limits depend on version or usage type.

I have Claude Pro ($20/month) and consistently run into the per-session usage limits when using Claude Code (CLI tool). I'll max out my current session and have to wait for the window to reset, even though I often end up using only 20-40% of my overall weekly allowance.

My budget is around $30/month total. Is there a better solution than Pro + occasional overage purchases?

Options I'm considering:

Paying for extra usage when I hit limits (but feels inefficient)

Switching to API pay-as-you-go for Claude Code specifically

Upgrading to a higher tier (but $100/month seems excessive for my usage)

For those who use Claude Code heavily in bursts but inconsistently week-to-week - what's your setup?

I'm thinking of upgrading to the $20/month plan specifically to use Claude Code. Are you guys hitting the limit constantly? Just trying to figure out if it's usable for a full workday or if I'll get capped immediately.

I'm like 3 days in and I'm at weekly capacity, probably like 30 small haiku messages and about an hour of active sonnet for claude code, and this is getting pretty stupid, curious about this

I’m running Claude Code with the Max $200 plan. I used to be able to run a single window for roughly the whole five hours before running out of context. But for the past 2 days, I’ve only gotten about an hour, and then I have to wait 4. My plan hasn’t changed. It’s not an especially large codebase. I’m not doing anything crazy.

Is there some cache that needs to be cleared, or something I should make sure is not in my Claude.md file? Tips/hints/suggestions? At 1 hour out of every 5 this is unusable. :-(

UPDATE: it was a misconfigured hook. When I removed it, everything returned to normal. (Phew!) Lots of useful suggestions in the thread — thanks all!

Now that there all new weekly limits on claude code usage, how are you tracking daily usage or overall preserving the limits to actually help you run through the week ? Reached capacity and now I literally do not know what to do with my life. Claude code gurus - waiting for your insights and tips & tricks.

/cost doesn’t tell me how many tokens I’ve used. But after 4 hours I’m at my limit. My project is not massive, and I never noticed more than a few k tokens on occasion. It would be good to know what the limits are and I might move to max.

As we know, each time we start a chat or claude code, we open a session for 5 hours. As I understand, even if I wrote hi and left the code, came back in 5 hours - write Hi again - its counted 2 session, regardless of the tokens passed\recieved, so hitting 50 sessions a month is pretty easy. How this works realy, and if some one got session limit warning ever?

TL;DR: Built shell scripts that let you instantly switch between your Claude Pro/Max subscription and API keys from AWS, Google Cloud, Azure, and Anthropic. When you hit rate limits mid-task, one command and you're back to work. Bonus: Easy access to Opus 4.5 on any provider without needing Max subscription. GitHub repo

You know the feeling. You're deep in a debugging session, finally making progress, and then:

"Rate limit exceeded. Try again in 4 hours 23 minutes."

Your momentum dies. Your context is gone. You're stuck.

The Pro plan gives you maybe 10-15 good prompts per 5-hour window. Even Max caps around 40. For anyone shipping fast, that's not enough.

The obvious solution: Use API keys and pay per token. But switching between subscription and API mode in Claude Code is painful – manually editing config files, managing multiple providers, remembering different model IDs. Most of us just... wait for the timer to reset.

So I built something to fix this.

What it does

Simple shell scripts that make switching instant:

# Working with Claude Pro, hit rate limit
claude
# "Rate limit exceeded. Try again in 4 hours."

# Immediately continue with AWS (keeps your conversation)
claude-aws --resume

# Or switch to Haiku for speed, Opus 4.5 for complex reasoning
claude-aws --haiku --resume
claude-vertex --opus --resume

# Back to Pro when limits reset
claude --resume

The --resume flag picks up your last conversation exactly where you left off. No lost context.

Supports four providers:

• claude-aws – AWS Bedrock

• claude-vertex – Google Cloud Vertex AI

• claude-azure – Microsoft Foundry on Azure

• claude-apikey – Anthropic API directly

Each command is session-scoped and non-destructive. Your original config is automatically restored when you exit.

Why this matters

1. Maximize your subscription value

Your $20 or $200/mo is incredibly cost-effective when you can actually use it. Rate limits mean you're paying for capacity you can't access. This lets you use your subscription fully, then seamlessly switch to API when you hit limits.

2. Easy Opus 4.5 access (just released today!)

Claude Pro users: You can now easily switch to Opus 4.5 on any provider when you need its power, without needing a Max subscription ($200/mo). For example, just claude-aws --opus or claude-vertex --opus.

3. Use your cloud credits

If you have AWS, Google Cloud, or Azure credits, these work with Claude Code but setting it up is complex. This makes it simple – add credentials once, switch with one command.

Quick setup

git clone https://github.com/andisearch/claude-switcher.git
cd claude-switcher
./setup.sh

Then edit ~/.claude-switcher/secrets.sh:

# AWS
export AWS_PROFILE="my-profile"
export AWS_REGION="us-west-2"

# Google Cloud
export ANTHROPIC_VERTEX_PROJECT_ID="my-project"
export CLOUD_ML_REGION="global"

# Anthropic API
export ANTHROPIC_API_KEY="sk-ant-..."

# Azure
export ANTHROPIC_FOUNDRY_API_KEY="my-key"
export ANTHROPIC_FOUNDRY_RESOURCE="my-resource"

That's it. Now you can switch between any provider with one command.

Utilities included

• claude-status – Shows current auth mode and configuration

• claude-sessions – Lists all active sessions with provider, model, uptime

My workflow

• Start with claude (Pro subscription)

• Hit limit → claude-aws --resume (AWS credits)

• Need faster responses → claude-aws --haiku --resume

• Complex architecture → claude-vertex --opus --resume

• Limits reset → back to claude --resume

This has saved me hundreds in API costs while keeping productive. More importantly, it removed the friction that killed my momentum.

GitHub: github.com/andisearch/claude-switcher

Built this for myself at Andi (we're building an AI search engine) because we needed it to keep shipping. Figured it might help others too.

If it's useful, a star would be appreciated. Questions or issues, happy to help in comments.