ThinkFacility

Blog

Claude Code's /limit-reset, and what it actually resets

A command that turns your five-hour session limit back on, once in a while, and tells you when you can do it again.

4 September 2026 · Claude Code usage limits

If you use Claude Code on a subscription, you have met the five-hour session limit. You are partway through something, the session stops, and you wait. A command called /limit-reset now ends that wait, and it appeared without an announcement.

Here is what it does, what it leaves alone, and where it fits alongside the two other things Claude Code has added for the same problem.

What it does

Running /limit-reset clears your current session limit immediately. The command describes itself as resetting your session limit now, and on success it prints a single line in three parts:

Session limit reset · next reset available Sep 5, 6pm · your weekly limit still applies

Every part of that line matters.

Session limit reset means the five-hour window you had exhausted is available again. You can carry on in the same session.

Next reset available is the important half. The command is rationed, and it tells you when you may run it again. On the account tested for this post, that was the following evening. Community reports from earlier in the week described it as a once-a-week allowance. Treat the date the command prints as the truth for your account, because it is the only number that reflects your own plan and history.

Your weekly limit still applies is the sentence to read twice. There are two limits, and this command only touches one of them.

What it does not do

It does not reset your weekly limit. If you have burned through the week, /limit-reset will not help, and the message says so on every successful run.

It does not add credit, change your plan, or give you a larger allowance overall. Consider what it does to be rescheduling, not topping up. You get the rest of your five-hour window sooner, and the weekly ceiling is unmoved.

Three failure messages exist, and they tell you which wall you have hit:

It is not in the documentation

As of today, /limit-reset does not appear in the published command reference, and it is not in the documentation index either. It is in the shipped binary and it works. That gap explains why the first widespread notice of it came from someone typing a slash and reading the list, not from release notes.

Two practical consequences. First, do not expect a documented policy on how often you can run it, because there is not one to find. Second, the behaviour could change without a note, so the date the command prints is worth more than anything written about it, including this post.

The three tools for the same problem, and which to use

Claude Code has picked up three separate answers to hitting a limit over the past month, and they are easy to confuse.

Auto-continue when the limit resets

This one waits for you. When a usage limit stops your session, Claude Code resumes automatically once the limit resets, instead of leaving the work abandoned until you come back. It arrived in the middle of August and is on by default. You turn it off in /config, under the setting for continuing automatically at a usage limit.

Use it for the overnight case. The run stops at one in the morning, resumes when the window rolls over, and you read the result at breakfast.

Lower-priority mode

Offered when you reach your session limit, this keeps you working immediately at reduced priority. Your weekly limit still applies, and replies may pause while the request waits for spare capacity. Running the command again stops it. Once ended, it is offered again after your weekly limit resets.

Use it when you want to keep going right now and do not mind that responses arrive when they arrive.

/limit-reset

Use it when you need full speed immediately and you are willing to spend a rationed allowance to get it. It is the strongest of the three and the one you have least of.

The sensible order is to let auto-continue handle anything that can wait, take lower priority when you want to keep typing, and save /limit-reset for the moment you actually cannot afford to stop.

What people are saying

The reaction in community threads has been consistent, and it is not mainly about this command.

The command itself was met with surprise more than celebration. The first widely read thread about it, at the start of September, was someone reporting that they had found it and describing it as a weekly session reset. The tone was that this was a quiet, welcome addition that nobody had been told about.

The stronger feeling attaches to auto-continue, which landed a few weeks earlier. Several threads described it as the thing people had actually been asking for, with more than one person noting that they no longer set an alarm in the small hours to restart a stalled run. A recurring sentiment was that this was overdue and had come after sustained complaint.

Underneath all of it, the five-hour window remains the thing people are frustrated by. Threads about hitting it appear steadily, including from people who feel their usage disappears faster than they can account for. There was also a burst of posts at the start of September noticing that limits appeared to reset for everyone around the launch of a new model, which is a different event from this command and worth not confusing with it.

Perspectives here are paraphrased from public discussion threads rather than quoted, and no individual is named.

The short version