Skip to content
Mastering Claude

Home / Never running out of tokens

Never running out of tokens5 minFondation
Clock face with its hand making one full turn, with the dimension line "one day" belowUp and running in a day1 day
Path 1, module 2 of 6, lesson 2 of 3

What to do when the limit is reached

Once the limit is reached, sending new messages is impossible until something unblocks it: waiting for the counter to reset, changing plan, or buying usage credits. Only waiting is free, and the only useful preparation is knowing in advance who to turn to within your organisation.

A Claude account limits what you can consume over a period. As recorded on 2 September 2026, the documentation describes two counters, and neither is daily: a five hour session window, and a weekly limit. The previous lesson had you open the page that displays them. Once this ceiling is reached, sending new messages becomes impossible until an event unblocks it.

Three ways out, and only one is yours

As recorded on 2 September 2026, Anthropic's documentation describes three ways to get going again: wait for the counter to reset, change plan, or buy extra usage credits. The last two cost money, and on an organisation account they do not depend on you: activating credits happens at the organisation level, by whoever is in charge of it. On a subscription taken out personally, the same purchase is made from your own account settings. So the only free way out is waiting.

What has been added since late September

The /rate-limit-options command has appeared, since late September 2026, in /help and in Claude Code's command menu for claude.ai subscribers, which gives an entry point when a limit notice shows. On Pro and Max, Claude Code also warns when resuming an inactive conversation would use a noticeable share of the five hour limit: opening a fresh conversation then avoids that cost. Since 7 October 2026, the Max and Team plans also include monthly API credits, meant for the apps and agents you run on the Claude Platform. The announcement does not present them as a way to lift the conversation limit, and you must link a Claude Console organization in the billing settings to receive them.

The only reliable action, before you need it

What stays true whatever the type of account is that a block always arrives at the wrong moment, right in the middle of a piece of work. The only useful preparation does not depend on any still uncertain technical detail: knowing in advance who to turn to within your organisation in the event of a block. This information is written down once, before you need it, rather than being looked for in an emergency.

Référent à contacter en cas de blocage :
Nom : ...
Moyen de contact : ...
Délai habituel de réponse : ...

Filling in these three lines takes less time than waiting for an answer on the day the block actually happens. The same sheet is also useful for a colleague less comfortable with the tool: sharing it prevents everyone from rediscovering, alone, at the worst moment, the same question with no answer written down anywhere.

Where this fits in the module

The next lesson in this course, the right habits for saving, explains how to space out the moments when this ceiling is reached, which reduces how often this kind of block happens without removing the possibility.

Figure 1

From normal work to being blocked, then to contact

01
Normal work
Token consumption as messages are exchanged.
02
Approaching the quota
Visible in the account settings, on the page that displays usage: five hour window and weekly limit.
03
Quota reached
Sending new messages blocked.
04
Organisation account
Wait for the reset, or extra usage credits activated at the organisation level.
05
Individual account
Wait for the reset, or extra usage credits bought from the account settings.
06
Contacting the referent
The person identified in advance within the organisation.
The path goes from normal work to the block, then to the three documented ways out and to the contact prepared in advance. Addresses at the end of the lesson.
Calibrate it yourself

A person working from an account created by her cooperative's administrator receives a message in the middle of the afternoon informing her that she will be able to write again in several hours. She has to hand in her work that same evening, and looks in her interface for something that would let her resume sooner.

Write in one sentence what this situation establishes, and in one sentence what it does not establish.

What to remember
  • A reached limit blocks the sending of new messages; two counters exist, a five hour window and a weekly limit, no daily counter.
  • Three ways out exist: wait for the reset, change plan, or buy extra usage credits; only waiting costs nothing.
  • On an organisation account, activating credits happens at the organisation level, so not by the person who is blocked.
  • Noting in advance who to contact avoids wasting time looking for this information at the exact moment you can no longer work.
  • Since late September, Claude Code offers /rate-limit-options to claude.ai subscribers and, since October, warns before resuming an inactive conversation that would use a noticeable share of the five hour limit.
Do this now

Write today, to whoever administers your accounts, asking who to contact in the event of a block and within what timeframe. Note the answer in the same place as your other working reference points, before you need it.

What still needs checking

These points depend on an interface or a rule that may have changed since this was written. Check them on your own screen before relying on them.

  • The amount of credits, the top up thresholds and the conditions specific to your plan are read in your account settings, this course quotes no price.
  • The procedure internal to your organisation in the event of a block exists nowhere in writing until you write it with your administrator.
Check the source

Every datable claim in this lesson links here to the public text behind it. A source that does not open proves nothing.