← Back to all free guides

How To Never
Hit Your Claude
Limit Again

5 changes that keep you off the Claude weekly cap. Most people hit it because of one habit (long threads) and one choice (the biggest model for everything). Fix those plus 3 more and you’ll basically stop hitting it.

Paid Claude plans have two limits. A five-hour session limit starts with your first message and resets in full five hours later. A weekly limit resets at a fixed day and time assigned to your account. Some plans also have a separate weekly limit for Fable. (How Claude’s limits work)

Everything you do counts toward the same budget: claude.ai, the desktop app and Claude Code. What burns it fastest is long chats, big models on small tasks, high effort and lots of back-and-forth. Here’s how I fix each one.

First, look at your numbers. Go to Settings, then Usage. You’ll see how much of your current session and weekly limit you’ve used, plus when each one resets.

Tip 1: Start New Chats Often

Claude rereads the whole conversation every time it answers, so each new message in a long thread costs more than the one before it. Very long chats also trigger automatic summarizing, and Anthropic says those conversations use more of your limit.

When a thread gets long, start fresh. Run this at the bottom of the old chat first so you don’t lose anything:

The Handoff Prompt
You are closing out this conversation so I can continue it in a fresh chat without losing anything important. Read this entire thread, then write a handoff document with these sections: 1. GOAL: what we're working on and what "done" looks like, in one short paragraph. 2. DECISIONS: every decision we made, each with a one-line reason. Bullets. 3. CURRENT STATE: the latest version of anything we produced (copy it in full if it's under 300 words, otherwise summarize it and tell me where it lives). 4. OPEN QUESTIONS: everything still undecided. 5. MY PREFERENCES: anything I told you about my style, constraints, tools or context that a new chat would need. 6. NEXT STEP: the exact next action, written as the first instruction to the new chat. Rules: - Only include things that actually came up in this chat. Don't fill gaps with guesses. - If something was changed later in the thread, keep only the final version. - Keep it under 600 words and format it so I can paste it into a new chat as the very first message.

Paste the result into a new chat as your first message and keep going. You get the context without paying for the whole history again.

Tip 2: Use Projects For Anything Recurring

Files you add to a Claude Project are cached. When you reuse them while they’re still cached, they count less against your limit than uploading the same files into chat after chat. The cache does expire after a while, so the first message after a long break counts that content in full. (Anthropic’s usage tips)

I keep a Project for every big area of my work, like my brand, my content and each client. The style guide, brand voice file and past work go in once, and every chat inside starts smart. Clear out files you no longer need so Claude isn’t carrying dead weight.

Paste this into the Project’s instructions so Claude uses those files instead of asking you to repeat yourself:

Project Instructions
You are my working partner for [area of work, e.g. "my brand's content" or "Client X"]. ALWAYS USE THE FILES IN THIS PROJECT: - Treat the uploaded files as the source of truth for my voice, audience, offers and past work. - Before you answer, check them for anything relevant. If two files disagree, tell me which one you followed. - Never ask me for information that's already in these files. HOW I LIKE TO WORK: - Keep replies tight. Lead with the answer or the draft, then any notes. - When I give you several tasks at once, handle all of them in one reply. - If a request is unclear, make your best call, flag the assumption in one line and keep going. WHAT TO AVOID: - [Words, phrases or formats you never want] - Restating my question back to me or summarizing what you just did.
  1. Use it once. Paste the Project Instructions into a new chat in Claude or ChatGPT, fill in the [brackets], and send. Then open a chat inside that Project.
  2. Keep it. In Claude, make a Project, click Set project instructions, paste it in and save. Every chat in that Project starts with it. In ChatGPT, do the same with a Project’s instructions.
Tip 3: Match The Model And Effort To The Job

Pick the model and effort level from the menu next to the send button. You can change both at any point in a chat, and the change applies from Claude’s next reply. (Model and effort settings)

01

Haiku 5.5

Quick lookups, formatting, simple rewrites, summaries and sorting. Anything you’d hand an intern for 60 seconds.

02

Sonnet 5.5

Everyday work like drafting, editing, analysis and most coding. This should be your default.

03

Opus 5.5

Hard reasoning, multi-step plans, big strategy calls and the work where quality really matters.

04

Fable 5.1

Anthropic’s model for the most demanding reasoning and long agent runs. Save it for the rare job Opus can’t crack. On some plans it has its own weekly limit or is paid with usage credits.

For a sense of scale, on Anthropic’s API price list Opus 5.5 costs twice what Sonnet 5.5 does, and Fable 5.1 costs more than twice Opus.

Effort matters too. Click the model name, then Effort. Anthropic says Low and Medium stretch your usage further, while higher effort uses more tokens and gets you to your limit faster. I run routine work on Low or Medium and raise it only for hard problems.

Tip 4: Batch Your Questions

Three separate messages mean three replies, and each one carries the whole conversation with it. Anthropic’s own advice is to group related questions into one message and give the background up front.

This template makes it easy:

The Batch Prompt
I'm going to give you several related tasks in one message. Do them all in this single reply. CONTEXT (read first, applies to every task): [Paste the background once: who it's for, the goal, any files or details that matter] TASKS: 1. [First task] 2. [Second task] 3. [Third task] FOR EACH TASK: - Put it under its own numbered heading that matches the list above. - Give me the finished output, not a plan to do it. - If you need information I didn't give you, make a reasonable assumption, label it ASSUMPTION, and keep going instead of stopping to ask. AT THE END: - One short list of anything you assumed or couldn't do, so I can fix it in a single follow-up message.
Tip 5: Plan Around The Five-Hour Session

This is the limit people forget. Your session starts with your first message, so one heavy hour can use it up and lock you out until it resets, even with plenty of weekly room left.

Spread heavy work across the day instead. A morning block, an afternoon block and an evening block each land in their own session. One four-hour marathon burns through a single session.

If you need a long sprint, do the hard thinking on Opus, then switch the same chat to Sonnet and lower effort for the execution work that follows.

The Order To Fix Things

Day one, move your recurring work into Projects. Day two, make Sonnet your default and drop effort on routine tasks. Day three, start using the handoff prompt to keep chats short. Comment LIMIT on the original post and I’ll send you the full setup, including the handoff prompt and a Project starter file.