Claude peak hours: do limits really run out faster?

Yes, for some plans and products. In March 2026 Anthropic said Claude's 5-hour session limits on Free, Pro and Max drain faster on weekdays from 5 to 11am Pacific time, while weekly limits stay the same. On 6 May 2026 it removed that reduction for Claude Code on Pro and Max. So in Claude Code on those plans, peak hours no longer cut your limit.

What Anthropic said in March 2026#

The change was not a blog post or a help-centre page. It came from Thariq Shihipar of Anthropic's technical team, in a post on X, as The Register reported on 26 March:

"To manage growing demand for Claude we're adjusting our five hour session limits for free/Pro/Max subs during peak hours. Your weekly limits remain unchanged."

The key points, from that report and PCWorld's the next day:

• When: weekdays, 5 to 11am Pacific time.
• What: the 5-hour session limit drains faster in that window. You can reach it in less than five hours of the same work.
• Who: Free, Pro and Max subscriptions.
• Not changed: weekly limits. Anthropic described it as changing how usage spreads across the week.
• How many: Anthropic estimated that about 7% of users would hit session limits they wouldn't have hit before, mostly on Pro.
• Advice: move token-heavy background jobs to off-peak hours.

What changed for Claude Code on 6 May#

Six weeks later, Anthropic's own post, Higher usage limits for Claude and a compute deal with SpaceX, made two changes to Claude Code:

"First, we're doubling Claude Code's five-hour rate limits for Pro, Max, Team, and seat-based Enterprise plans."

"Second, we're removing the peak hours limit reduction on Claude Code for Pro and Max accounts."

Both took effect that day. Every other limit change this year, with dates, is in our list of Claude usage limit changes in 2026. If your 5-hour window in Claude Code felt shorter during weekday peak hours in April, that's why. If it still does now, peak hours aren't the cause; look at your context size and how many agents share the account instead. Our guide to Claude's 5-hour limit covers how the window works.

Who is still affected#

As of 22 October 2026, this is what the two statements cover. We found no later statement from Anthropic either way, so where they say nothing, we say so:

Two things to keep in mind. On Pro and Max, Anthropic's help page says the limits "are shared across Claude and Claude Code", so heavy chat use in the morning still counts toward the same window your Claude Code uses. And Anthropic doesn't publish exact limit sizes, so no one outside can measure "how much faster" in tokens.

Peak hours in your time zone#

The window is fixed in Pacific time. Here it is elsewhere, on weekdays:

The "clock-change weeks" are when the US and Europe change clocks on different Sundays. In 2026 that was 8 to 28 March and 25 to 31 October. In those weeks, peak hours start an hour earlier for Europe. That's also why a "1 to 7pm GMT" figure in some March reports was an hour off: on 26 March, peak hours were noon to 6pm in London.

What you can do about it#

1. Use Claude Code for heavy work on Pro or Max. That's where the reduction is gone.
2. Move long, unattended jobs out of the window, if you're on a plan or product the reduction may still cover. That's Anthropic's own advice.
3. Check where you stand before a big job. /usage in Claude Code shows your 5-hour and weekly use and when each resets. Our guide on checking Claude Code usage walks through it.
4. Mind when your window starts. Claude's 5-hour window starts with your first message, not on the hour. A window you start at 4am Pacific runs through most of the peak.

How Shuriken helps: session limits#

Shuriken can't change how fast a window drains during peak hours. What it changes is when your windows start.

Claude's 5-hour window starts the first time an account is used. With session limits on (they are by default), Shuriken keeps every one of your subscriptions' 5-hour windows running: when one isn't, the computer it's signed in on sends it one tiny request in the background, once per window. Your chats don't move to do it. So when one account runs low, another has been counting down since its last reset and is often close to a fresh window. When an account does reach your switch point, hot swapping, Shuriken moving your chats to another of your accounts or sources when one nears its limit, carries the chat on.

More on the idea in the 5-hour clock starts when you do, and the details on the session limits page. Use only accounts you own and are entitled to use: providers' terms may not allow sharing a subscription sign-in.

If you'd like your accounts' windows to start on their own schedule, download Shuriken.