"Rate Limit Reached" on Claude Cowork?

You're paying $100 to $200 a month. You're still getting cut off mid-task. Here's why Cowork eats your quota faster than you think, and what to do about it.

Quick answer: Claude Cowork hits rate limits faster than regular chat because each Cowork task spawns sub-agents, tool calls, and file operations that all consume quota. A single complex Cowork session can use as much quota as dozens of chat messages. The fast path forward: read the exact error string to see which limit you hit (session, weekly, or a single model's bucket), confirm it's not the ghost rate limit bug, and enable Extra Usage pay-as-you-go if you need to keep working past your cap. Note that Claude Code weekly limits dropped 17% from their boosted summer level on 14 September 2026, and five-hour limits went up on 22 September.

If you've hit the "rate limit reached" wall on Claude Cowork, you probably know the feeling: 40 minutes into a real task, the workspace stops, the error appears, and a 4-hour countdown starts. You're paying for a premium tool. The usage page doesn't add up. Here's what's actually happening — and what's changed since the worst stretch in early 2026.

Not a rate limit? If Cowork on Windows stopped running local tasks after the September 8, 2026 Windows update, that was a Windows bug Microsoft fixed on September 14. See the fix.

Update: Claude Code weekly limits dropped 17% on 14 September 2026

This change is easy to misread because of how it was announced.

As of 14 September 2026, Anthropic made Claude Code weekly limits permanently 25% above the old standard. That sounds like more headroom. It isn't, not for anyone who used Claude Code over the summer.

The reason is what it replaced. The temporary 50% weekly boost that ran from May, and that was extended repeatedly (mid-July, then 19 July, then 19 August, then 31 August), expired on 13 September: the day before the permanent increase landed.

Anthropic itself described the result as "a 17% reduction in weekly limits on Claude Code" compared with the boosted level. So the direction depends entirely on where you measure from:

If you used Claude Code at any point in the four months before, you were working against the 150 line. On 14 September you dropped to 125. That is a 17% cut to the capacity you had.

What it means for Cowork: Cowork draws on the same plan usage limits as the rest of Claude, but Anthropic framed this change as a Claude Code weekly-limit change. It did not announce a 17% cut to every Claude or Cowork weekly limit, so don't read it as one. If you use Claude Code and Cowork on the same plan, plan around the lower Claude Code number.

Anthropic's original announcement led with the +25% and did not mention the net reduction. After community pushback the thread was deleted and replaced with a clarification that states the decrease plainly.

Two things to keep separate:

• The 14 September change was about weekly limits. Five-hour limits were raised separately on 22 September (see the update box above).
• Extra Usage (usage credits) still works. If a weekly cap starts biting mid-task, pay-as-you-go overflow is the release valve (see below).

The other half: OpenAI tightened up first

If you keep a second subscription as your fallback, that door narrowed a few weeks earlier. On 25 August 2026 OpenAI reinstated the 5-hour usage limit on Codex and ChatGPT Work for ChatGPT Plus subscribers, ending a six-week unlimited stretch that began on 13 July. OpenAI's stated reasoning was smoothing server load and stopping casual users from burning a whole week's quota in one sitting.

The 5-hour restriction remains disabled on the Pro $100 and Pro $200 tiers — so the escape hatch exists, it just costs considerably more.

The practical upshot: within three weeks, both of the obvious subscription options got tighter for the people paying the mid-tier price. Planning around one provider's limits by keeping a second subscription is a weaker hedge in September 2026 than it was in July. We ran the numbers on both changes, and on the API-key alternatives that don't reset weekly, in what to do when Claude Code and ChatGPT both rate-limit you.

Earlier changes still in effect

• May 6, 2026: A permanent doubling of the 5-hour rate limits on Claude Code (and by extension Cowork) for Pro, Max, Team, and seat-based Enterprise plans. The peak-hours throttle that used to cut Pro/Max during business hours was removed at the same time. This is still in place.
• Extra Usage (Anthropic's pay-as-you-go overflow at standard API rates) is generally available for Pro, Max 5x, and Max 20x. When you hit your plan cap, you don't have to stop — see the "Extra Usage" section below.
• Cowork went GA in April 2026 (it was a research preview when this post first ran).

The ghost rate limit bug below still happens. The pricing-vs-actual-burn gap still exists. But "you just hit the wall and there's nothing you can do for four hours" is no longer the full story.

"Rate limit exceeded. Limits will reset soon"

How long until it resets? It depends on which limit you hit. A five-hour session limit resets in full five hours after the first message of that session, not five hours after you were blocked: start at 2pm, get blocked at 4pm, and you are back at 7pm. A weekly limit resets at a fixed day and time assigned to your account, and that slot stays the same no matter when you subscribed or started using Claude that week. Your exact times are in Settings > Usage, under Current session and Weekly limits. With usage credits turned on, work continues on credits instead of stopping. (Verified Ultra accounts have no five-hour limit, only weekly ones.) Source: Anthropic's help article How do usage and length limits work?

First, what the Claude rate limit is, in plain terms. Every paid Claude plan comes with a usage allowance. It refills on a rolling five-hour session window, and there is a weekly limit on top. When you use up either one, Claude stops responding until the reset time it shows you, unless you have usage credits turned on. Cowork tasks count against the same allowance as chat, just much faster. This page covers Cowork. For limits in regular Claude chat and Claude Code, see our Claude rate limit reached guide. If you call the API with your own key, that has its own separate limits.

If you saw the exact message in the heading above, note that it isn't one of the messages Anthropic currently documents. It doesn't appear in Anthropic's help article on Claude error messages or in the Claude Code errors reference. It may come from an older version of an app or from a third-party app. These are the official messages in claude.ai, and what to do about each:

And in Claude Code:

Why Cowork Burns Through Your Quota So Fast

The first thing you need to understand about Claude Cowork rate limits is that Cowork tasks are not the same as chat messages.

When you send Claude a message in regular chat, that's one message. Simple. Predictable.

When you ask Cowork to organize your Downloads folder, extract data from 15 PDFs, and compile a spreadsheet, that's not one task. Under the hood, Claude is spinning up sub-agents, making multiple tool calls, reading and writing files, and coordinating parallel workstreams. Every single one of those operations consumes tokens from your quota.

Anthropic's own help center says it plainly: "Working on tasks with Cowork consumes more of your usage allocation than chatting with Claude." But they don't tell you how much more.

A single intensive Cowork session doing complex file operations can use as much quota as dozens of regular chat messages. The "225+ messages" on Max 5x translates to as few as 10 to 20 substantial Cowork operations before you hit the wall.

That's the gap between what the pricing page implies and what actually happens in practice.

The Rolling Window Trick, Explained

Here's the second thing that catches people off guard.

Claude doesn't use daily limits. It uses rolling 5-hour windows plus weekly caps. The 5-hour window resets 5 hours after you start using it (not at midnight). On Max plans, you also have two weekly limits running on top — one across all models, one specific to Sonnet.

Sounds flexible. In practice, it creates a dynamic where you can burn through your entire 5-hour allowance in a focused 45-minute work session and then sit idle for 4 hours waiting for the reset — and if you're already deep into a weekly cap, even the 5-hour reset doesn't fully unlock your throughput.

The 5-hour gap still kills momentum mid-task, but at least the May 2026 doubling of the 5-hour limits gives you more runway before that gap appears. On Claude Code, the weekly cap sitting on top of it is the part that tightened on 14 September, and five-hour limits went up again on 22 September. For exactly when each Claude limit resets (session, weekly, and API), see rate limit reached on Claude. Some power users in developer forums still report hitting walls on Max 20x at $200/month during crunch periods, which tells you token consumption on intensive Cowork sessions is high.

Read the exact error string: it tells you which limit you hit

"Rate limit reached" is the phrase everyone searches, but it is rarely the literal text on screen. Claude Code and Cowork name the specific bucket you exhausted, and each one has a different fix. These are the strings in Anthropic's official error reference:

Note the pattern in the last two: a model-specific limit is not the same as being out of quota. This is the single most common misread. If the message names a model, you are not locked out of Cowork — you are locked out of that model, and switching models in Settings gets you moving again immediately.

Anthropic's Fable models have their own bucket layered on top, and it behaves differently by plan:

• Max plans and premium seats: Fable 5 and Fable 5.1 are included, and you can spend up to 50% of your weekly usage limits on Fable models at no extra cost. Past that, you continue on usage credits or switch models.
• Pro plans and standard Team/Enterprise seats: Fable models are not included in your plan limits at all. They run on usage credits from the first token.

That split catches people out, because the Fable bucket can empty while your overall weekly meter still shows headroom. Issue #91623 documents exactly this: a Max 20x plan drained from 0% to 88% of its weekly limit in about 22 hours after sessions pinned to the fable alias silently moved from Fable 5 to Fable 5.1, which emitted roughly twice the output tokens per turn (~783 → ~1,596) on an otherwise unchanged workload. The Fable sub-limit was exhausted well before the general weekly cap.

If your burn rate jumps for no reason you can explain, check whether a model alias moved under you before you assume it's a bug in your own usage.

You may also see billing-side messages, which are a different problem entirely and are not rate limits: Usage credits required for 1M context, Credit balance is too low, spend limit reached, and spend limit unavailable. Those mean a payment or spend-cap setting needs attention, not that you need to wait.

The /limit-reset command

Claude Code added a /limit-reset command on 3 September 2026. Reported behaviour: it clears your 5-hour session limit once a week. It does not touch your weekly cap, and everything you do after the reset still counts against that weekly total.

Two caveats worth knowing before you rely on it:

• It shows up in the / menu for most users, but running it can return "A session-limit reset isn't available right now." Anthropic has not published the eligibility rules, and there is no documented way to check which outcome you'll get before you try.
• It is absent from the official error reference, so treat the behaviour above as community-reported rather than a contract.

It is useful for rescuing one blocked afternoon. It is not a way around the weekly cap, which on Claude Code is the limit that tightened on 14 September.

The Ghost Rate Limit Bug Most Guides Skip

But that's not even the real problem.

There's a documented bug where Cowork returns "API Error: Rate limit reached" even when your account is nowhere near its quota. Multiple users have filed issues on GitHub about this exact scenario. (If the failure shows up only on Windows, it may not be a quota issue at all — our guide on Claude Cowork not working on Windows covers the VM and service bugs that surface look-alike errors.)

One user on the Max plan reported getting rate limited on every single Cowork action for four consecutive days, despite having $250 in API credits and zero recent usage showing on their dashboard. Claude Chat worked fine. Claude Code worked fine. Only Cowork was broken.

Another user reported the same bug with only 16% of their quota used. Switching to a different account on the same machine immediately fixed it, confirming it was a server-side problem tied to their specific account.

The suspected cause? A corrupted rate limit state on Anthropic's backend. A ghost flag that incorrectly marks your account as rate limited when it shouldn't be.

Both users had to request manual server-side resets from Anthropic support to fix it. There's no self-service option. No "clear my rate limit cache" button. You file an issue and wait.

What Anthropic's Pricing Page Doesn't Make Obvious

Let's lay out the actual numbers so you can make your own judgment.

Anthropic warns Pro users will burn through Cowork limits fast and explicitly recommends upgrading for heavy use. Even Max 20x users at $200/month report hitting walls during intensive work sessions, because Cowork token consumption scales with task complexity rather than message count.

Extra Usage is the pay-as-you-go overflow that kicks in after you exceed your plan limits. It bills at standard API rates with optional spending caps and usage alerts. Running complex Cowork tasks in overflow can easily add $50 to $100 on top of your subscription in a busy month — but it does mean you don't have to stop working mid-task. (More on how to enable it below.)

Anthropic also now exposes a real-time usage dashboard at Settings → Usage in Claude. It shows month-to-date consumption broken out by surface (Claude, Claude Code, Cowork) and tracks any Extra Usage spend. It's not a perfect "you're at 80% of your Cowork quota" gauge during a single 5-hour window, but it does close the visibility gap the original version of this post called out — you no longer find out you're capped only when the error appears.

If you're evaluating whether Cowork is the right tool for your workflow, you might want to look at how it compares to OpenClaw for autonomous tasks. The trade-offs are different than you'd expect.

The Real Question: Is Cowork the Right Architecture for Your Work?

Stay with me here. This isn't just a pricing complaint. It's an architecture question.

Cowork now runs on desktop, web (claude.ai), iOS, Android, and Chrome. Cloud sessions continue when your laptop is closed. Desktop sessions still need the app open for local file access. (Until July 7, 2026, Cowork was desktop-only and your computer had to stay awake; if you read that anywhere, it predates the change.)

So the laptop is no longer the question. The question is what Cowork is built around: one person, working on their own files and documents, running Claude only, metered against a subscription allowance. For organizing folders or building a spreadsheet, that model works fine. But if you need an AI agent that handles messages across Slack and WhatsApp and Discord, is shared by a team, and routes cheap work to cheap models so a weekly cap never decides when you're done, Cowork isn't built for that. Our Claude Code vs Cowork comparison lays out exactly which Anthropic tool fits which job, and where both leave a gap.

That's not a criticism. It's a design choice. Cowork is a personal productivity tool, not a multi-channel automation engine.

But if you came to Cowork looking for always-on autonomous agents and you're now hitting rate limits that prevent even simple tasks from finishing, the question isn't "how do I get more quota?" The question is "am I using the right tool?"

This is exactly why we built BetterClaw as a no-code AI agent platform. Your agent runs on our infrastructure, 24/7, on the channels your team already uses. No rate limits from a subscription tier. No ghost bugs locking you out of your own workflows. You bring your own API keys, pay for what you actually use, and the agent keeps running. $49 a month for Pro.

What to Do If You're Stuck Right Now

If you're currently hitting Claude Cowork rate limits, here's a practical action plan.

First, read the error string, then check whether it's a real limit or the ghost bug. If the message names a model ("You've hit your Opus limit"), just switch models — you are not out of quota. If it says session or weekly, open Settings → Usage in Claude. If your dashboard shows low consumption but you're still getting rate-limit errors, you're likely hitting the ghost rate limit bug. File an issue on the Claude Code GitHub repo and contact Anthropic support — the fix requires a server-side reset.

Second, enable Extra Usage so you don't get blocked mid-task. Go to Settings → Usage → Extra usage, attach a payment method, and set a monthly spending cap (or leave it unlimited, capped at $2,000/day). When your plan allocation runs out, Claude switches to standard API-rate billing and keeps working. Available for Pro, Max 5x, and Max 20x. Combine this with usage alerts so you know when you've crossed into pay-as-you-go territory.

If your agent runs on the API, use the API credits included with Max and Team. From 7 October 2026, Max and Team plans include monthly Claude API credits: $100 a month on Max 5x, $200 on Max 20x, and on Team $20 per Standard seat and $100 per Premium seat, pooled and capped at $500. They cover the Claude API, Managed Agents, the Agent SDK and the playground. They do not cover Claude Code, extra usage in the Claude apps, or Bedrock, Vertex and Foundry, and Anthropic says they don't change your usage limits in Claude or Claude Code. Credits don't roll over, you can claim them after 7 days on the plan, and Free, Pro and Enterprise plans aren't eligible. So they won't unblock Cowork, but an agent you've built on the API can keep working while your Cowork limit resets.

Third, batch your work to the 5-hour window. Start intensive Cowork sessions right after a reset to maximize your available capacity. Save simple tasks for regular Claude chat instead of wasting Cowork quota on things that don't need sub-agent coordination.

Fourth, reduce per-task token burn. Anthropic's official "Usage limit best practices" article spells out the levers:

• Use Sonnet or Haiku for routine work; reserve Opus for hard reasoning.
• Toggle off extended thinking on tasks where it doesn't change the output quality.
• Disable unused tools and MCP connectors in the Cowork session — every connected tool adds to the system prompt.
• Store frequently referenced material in project knowledge instead of pasting it into every chat.
• Start fresh chats when switching topics; long sessions carry their entire history forward.

These five changes typically extend a 5-hour window by 30-60% before any other lever moves.

Fifth, consider whether you actually need Cowork's specific capabilities. If your main use case is running OpenClaw best practices style workflows, an always-on managed agent serves you better than a subscription tool with usage caps. And if you're on Pro and hitting limits constantly, the jump to Max 5x at $100/month might help — but if you're already on Max 5x and still hitting walls, throwing another $100 at Max 20x doesn't solve the underlying architecture mismatch. It just delays the same frustration.

The Bigger Picture: Why AI Agent Pricing Is Still Broken

Here's what I think about when I see users paying $200 a month for Cowork and still getting locked out.

The AI agent space hasn't figured out pricing yet. Subscription tiers with vague "message" counts don't map cleanly to agentic workloads. A message in chat and a message in Cowork are wildly different in cost, but they're counted against the same fuzzy quota.

Anthropic has been adjusting the model — limits have moved in both directions over the last few months and Extra Usage now exists as an overflow valve — but the core mismatch between subscription caps and agent workloads remains. Token-based billing with transparent per-request pricing is more honest than caps that hide the true cost. It's less predictable, sure. But at least you know exactly what you're paying for.

Cowork is a impressive product — the sub-agent coordination, file system access, and polished Excel/PowerPoint outputs are real. But every time you stare at a 5-hour countdown instead of finishing your work, or you can't tell whether the error is a real limit or the ghost bug, it chips away at the trust that makes an AI agent useful. Pick the architecture that matches how you actually work, then build something great with it.

If you're building workflows that need to run reliably without surprise rate limits, ghost bugs, or a weekly cap deciding when you're done, give BetterClaw a try. $49/month for Pro, BYOK, managed infrastructure, no subscription-tier caps. The agent runs whether you're awake or asleep.

Frequently Asked Questions

Is "Claude rate limit exceeded. Limits will reset soon. Please try again later." an official message?

No. It isn't one of the messages Anthropic currently documents for claude.ai or Claude Code. It may come from an older version of an app or a third-party app. The official claude.ai messages include "5-hour limit reached - resets time" and "You've reached your weekly limit. It resets day at time." In both cases, wait for the reset time shown or turn on usage credits.

What does "rate limit reached" mean on Claude Cowork?

It means you've exhausted your usage allocation for the current 5-hour rolling window. Cowork tasks consume significantly more quota than regular Claude chat messages because each task involves multiple sub-agent calls, tool use, and file operations. Depending on your plan tier, this could mean as few as 10 to 20 substantial Cowork operations before the limit kicks in.

How does Claude Cowork compare to OpenClaw for running AI agents?

Claude Cowork is Anthropic's agentic workspace for your own files and documents. It runs on desktop, web (claude.ai), iOS, Android, and Chrome; cloud sessions continue when your laptop is closed, while desktop sessions still need the app open for local file access. It runs Claude only and draws on your subscription's usage limits. OpenClaw is an open-source agent framework that runs 24/7 on a server, connects to 15+ messaging platforms, and supports multiple LLM providers. Cowork is better for file and document tasks, while OpenClaw is better for always-on automation and multi-channel workflows.

How do I fix the Claude Cowork rate limit bug when my usage isn't actually high?

If Settings → Usage shows low consumption but Cowork keeps returning rate limit errors, you're hitting the ghost rate limit bug — corrupted backend state on your account. File a fresh issue on the Claude Code GitHub repo and contact Anthropic support directly. Earlier issue #34068 was closed as "not planned," and no public patch has shipped yet, so the fix is still a manual server-side reset by support. Switching to a different account on the same machine can confirm whether the issue is account-specific.

Is Claude Max worth $100 to $200 a month for Cowork usage?

It depends on your workload. Max 5x at $100/month gives roughly 5 times the Pro quota, which translates to about 10 to 20 intensive Cowork sessions per 5-hour window. If you regularly exhaust that, Max 20x at $200/month provides more headroom. But if you need agents running continuously or across messaging platforms, a no-code AI agent platform at $49/month with BYOK API keys may deliver more value per dollar.

Did Claude Cowork rate limits go up or down in September 2026?

Both, and they were different limits. On 14 September 2026 Claude Code weekly limits became a permanent 25% above the old standard, replacing a temporary 50% boost. Anthropic called that a 17% reduction in weekly limits on Claude Code compared with the boosted level. Then on 22 September, with the Opus 5.5 launch, Anthropic raised five-hour usage limits on Pro, Max, Team and seat-based Enterprise plans and added a one-time reset you can save for later. It published no numbers for that increase. Cowork shares your plan's limits, but Anthropic did not describe the 14 September change as a cut to every Cowork limit.

What does the /limit-reset command do in Claude Code?

Added on 3 September 2026, it clears your 5-hour session limit once per week. It does not reset your weekly cap, and usage after the reset still counts toward that weekly total. It can also return "A session-limit reset isn't available right now" — Anthropic has not published eligibility criteria, and the command is not covered in the official error reference.

Why did my quota drain so fast when my workload didn't change?

Check whether a model alias moved under you. Sessions pinned to the fable alias were silently migrated from Fable 5 to Fable 5.1, which produces roughly twice the output tokens per turn — around 1,596 versus 783 — on identical work. Because Fable models draw on their own sub-limit, that bucket can empty while your general weekly meter still shows headroom.

Is Claude Cowork reliable enough for production workflows?

Cowork went GA in April 2026 and is no longer a research preview, but practical limitations remain: local file access still requires the desktop app to be open (cloud sessions on web and mobile don't), the ghost rate limit bug can still lock accounts out unexpectedly, and rate caps can interrupt longer workflows even on Max 20x. For non-critical file and document tasks it works well; for production workflows that need guaranteed uptime, a server-hosted agent with managed infrastructure is the safer bet.