You’ve used 75% of your weekly limit: what it means and what to do

The notice “You’ve used 75% of your weekly limit” tends to appear mid-task. It is not a fault and not a block: it is a counter telling you how much of the week’s allowance is left. Here is what it means, how the limits are built, and what to do so the remaining quarter lasts until the reset.

What “You’ve used 75% of your weekly limit” means

It says exactly what it reads: three quarters of this week’s allowance are gone and a quarter remains. Access is not switched off — the warning comes early so the rest can be spread out.

How the Claude weekly limit works

Paid plans run two counters at the same time, and that is the part worth understanding:

• Session limit. Resets every five hours.
• Weekly limit. Resets once a week. This is the one the 75% notice refers to.
• Everything counts together. Usage on claude.ai, in the desktop app and in Claude Code all draws on the same allowance.

So a five-hour session can reset while the weekly counter carries straight on. When people say the limit “runs out faster than it used to”, it is usually the weekly counter they are hitting, not the five-hour one.

When the weekly limit resets

The app itself shows the exact date and time: in Claude it appears in the usage details, in Claude Code through the usage status command. That figure is the one to go by — the week runs from the start of your own period, not from Monday.

Why the limit burns faster than before

The same number of messages can cost wildly different amounts. According to Claude’s own help, consumption depends on:

• Length and complexity of the conversation. In a long chat every new message makes the model re-read everything above it.
• Extended thinking. Valuable on hard problems, expensive on simple ones.
• Effort level. A high level costs more.
• The model chosen. Larger models spend the allowance faster.
• Connected apps, web search and project files. Each connection adds text to every request.
• Automatic context management. When a long chat nears the context limit, Claude summarises the earlier messages to itself — and that counts too.

What to do when 25% is left

• A fresh chat for a fresh task. The strongest single move: a long chat gets dearer with every message, a short one costs the same each time.
• Extended thinking only where it earns its keep. Text edits and simple questions do not need it.
• A lower effort level for routine work. Sorting mail and short answers run fine on low.
• Turn off connections and web search you are not using. If the answer does not depend on today’s news, search only adds bulk.
• Keep project instructions and files short. They are attached to every request, not once.
• Wait for the reset, move up a plan, or switch on usage credits. A new plan takes effect immediately.

Making the allowance last a full week

If the 75% notice lands on Wednesday, the plan is rarely the problem — the shape of the work is: long chats, a heavy model on light tasks and connections left on “just in case” eat a week in three days.

When it is cheaper to hand the work over

The allowance disappears where a person runs routine by hand through a chat window: sorting enquiries, assembling reports, rewriting copy, watching a site. That same work moves into automated scenarios that spend on the job itself and leave your personal limit alone.