Claude Code Session Limit vs Weekly Limit: What's the Difference?

Mar 25, 2026

I was in the middle of a work project when I hit a limit. “Session limit reached.” I was confused—I had plenty of my weekly allowance left. Then a few days later, I hit my weekly limit with plenty of session capacity. What was going on?

The Problem: Two Separate Limits

Claude Code has two independent limit types, and hitting one doesn’t mean you’ve hit the other:

Session limits - reset when you start a new conversation session
Weekly limits - accumulate across all sessions and reset on a fixed weekly schedule

I learned this the hard way when I tried to add API credits to bypass what I thought was a session limit:

“I added FIVE dollars and it was gone like instantly finishing the task.”

That’s because API credits and subscription limits are completely separate billing systems. I had confused session limits with weekly limits.

How Session Limits Work

Session limits are token limits per conversation session. They reset when you start a new session.

When You Hit Session Limits

You’ll typically hit session limits when:

Running long conversations with extensive context
Performing large file reads or multiple file operations
Keeping a single session active for extended periods

The interface shows a token count for your current session. When you see “Session limit reached,” it means that specific conversation has consumed its allocated resources.

How to Handle Session Limits

When you hit a session limit, you have options:

Option 1: Start fresh session
  -> Summary: Begin new conversation
  -> Pro: Clean slate, full capacity
  -> Con: Lose context from previous session

Option 2: Use /compact command
  -> Summary: Reduce context size
  -> Pro: Continue in same session
  -> Con: Some detail may be compressed

Option 3: Summarize and continue
  -> Summary: Manually summarize key points
  -> Pro: Preserve important context
  -> Con: Requires manual effort

I’ve found that starting fresh sessions for new tasks prevents me from hitting session limits unexpectedly. The key is recognizing when a task is truly done versus when you should continue in the same session.

How Weekly Limits Work

Weekly limits are your total token allocation per week. They accumulate across all sessions and reset on a fixed schedule (which varies by account).

Plan-Specific Allocations

Different plans have different weekly caps:

Plan	Weekly Allocation
Pro	Lower weekly cap
Max 5x	Higher weekly cap
Max 20x	Highest weekly cap

The interface shows a percentage of weekly usage. When you see “Weekly limit reached,” you’ve consumed your total weekly allowance across all your sessions.

When You Hit Weekly Limits

You’ll typically hit weekly limits when:

Using Claude Code heavily throughout the day
Running multiple parallel sessions
Working with large codebases extensively

One Reddit user reported:

“I burned through 1/3 of weekly limit in like a day”

This is easy to do if you’re not monitoring your usage. I’ve learned to check my weekly percentage early in the week, especially when I have critical work scheduled later.

Why Both Limits Exist

At first, the dual-limit system seemed confusing. But it actually makes sense for resource allocation:

Session limits prevent runaway costs from single conversations. Without them, one long session could consume excessive resources.

Weekly limits balance usage across all users. They ensure fair resource distribution on a fixed schedule.

This combination allows Anthropic to offer flexible usage patterns while maintaining system stability.

Common Mistakes

I’ve made (and seen others make) these mistakes:

Mistake 1: Confusing Session and Weekly Limits

“I hit Session limit and I was shook when last week with same usage did hit anything.”

The user was comparing session limits (which they hit) to weekly limits (which they hadn’t hit last week). These are completely different metrics.

Mistake 2: Not Tracking Which Limit You’re Hitting

When the limit message appears, check which type it is:

Session limit: Token count shown
Weekly limit: Percentage shown

Knowing which limit you’ve hit determines your next action.

Mistake 3: Adding API Credits for Subscription Limits

API credits and subscription limits are separate. Adding money to your API account won’t increase your subscription’s weekly allowance.

Comparison Table

| Feature              | Session Limit          | Weekly Limit              |
|----------------------|------------------------|---------------------------|
| Reset timing         | Per session            | Weekly schedule           |
| Accumulation         | Single session         | All sessions              |
| Interface display    | Token count            | Percentage                |
| Bypass method        | Start new session      | Wait for reset            |
| API equivalent       | Per-request limit      | Monthly billing           |

What to Do When You Hit Each Limit

If Hitting Session Limits

Break work into smaller sessions - Start fresh for each distinct task
Use /compact regularly - Reduce context size before hitting limits
Close inactive sessions - Don’t keep sessions open unnecessarily
Summarize context before continuing - If you need to continue, capture key points first

If Hitting Weekly Limits

Monitor usage early in the week - Check your percentage daily
Reserve capacity for critical work - Plan heavy usage for important tasks
Consider upgrading plan - If you consistently hit limits, a higher tier may be more cost-effective
Evaluate API vs subscription cost - For heavy usage, API pricing might be more economical

One user on Max 5x reported:

“I use this all day at work everyday… Going to get through 40% of cap this week… I just use straight Opus, I don’t even use Sonnet.”

They’re managing their weekly usage effectively by tracking their percentage and understanding their usage patterns.

Lessons Learned

After hitting both types of limits multiple times, here’s what I’ve learned:

Check the limit type first - Session and weekly limits require different responses
Plan weekly usage - Critical work should be scheduled when you have weekly capacity
Start fresh sessions strategically - Don’t force everything into one long conversation
Understand your plan’s allocation - Know your weekly cap and monitor your usage

The key insight is that session limits are about conversation length, while weekly limits are about total consumption. Once I understood this distinction, managing my Claude Code usage became much more predictable.

Final Words + More Resources

My intention with this article was to help others share my knowledge and experience. If you want to contact me, you can contact by email: Email me

Here are also the most important links from this article along with some further resources that will help you in this scope:

Oh, and if you found these resources useful, don’t forget to support me by starring the repo on GitHub!