A command that wasn't in anyone's Claude Code changelog started showing up for some users this week: /limit-reset. A r/ClaudeAI post from u/jevans102 (Sept 2-3, 2026, 255+ upvotes) shows it firing exactly as advertised — after hitting a session usage limit, running the command returned:
❯ /limit-reset
⎿ Session limit reset · next reset available Sep 4 at 2pm · your weekly limit still applies
It's a small addition to Claude Code's 90+ slash commands, and the top-voted moderator summary on the thread called the reaction a "resounding meh" — not because it doesn't work, but because it resets the limit fewer people are actually hitting.
TL;DR
| Question | Answer |
|---|---|
| What does it reset? | Your current 5-hour session usage limit |
| How often? | Once per week |
| Does it touch the weekly cap? | No — weekly limit still applies, and usage after the reset still counts toward it |
| Is it live for everyone? | Unclear — looks like an A/B test as of Sept 2026; several users report not having it |
| What people actually want | A /reset-weekly-equivalent — which does not exist |
What it resets, and what it doesn't
Claude Code enforces two separate usage ceilings on subscription plans: a rolling 5-hour session limit, and a longer weekly limit that Anthropic layers on top (see explainx.ai's Claude usage limits timeline for how that structure evolved through 2026). /limit-reset only clears the first one.
The confirmation text is explicit about the boundary: "your weekly limit still applies." One commenter paraphrased it more bluntly — usage after the reset "continues to count towards your weekly total." So /limit-reset doesn't grant free extra usage; it just lets you spend your existing weekly allowance without waiting out a 5-hour cooldown first.
That distinction matters for anyone deciding whether this changes their workflow. It's a scheduling unlock, not a budget increase.
Why the reaction split the way it did
The thread's top-comment consensus, per the auto-generated mod summary, was that this doesn't fix "the real problem: the weekly usage cap." Representative reactions:
- "Too bad it's a session-only reset. My problem is the weekly limit."
- "I never hit a session limit. I need a weekly reset option. Just once a month would be nice."
- "On Max x20 5h limits aren't the issue. Weekly would be much more appreciated, even if only once a month or something like that."
But a second, smaller group pushed back on that framing entirely — for them, the 5-hour session limit is the actual daily annoyance, and this is a real fix:
- "It's kinda funny to read the summary saying that most people 'never hit their session limit,' and that the real issue is the weekly limit. To me it's always the other way around. I pretty much never get even close to the weekly limit, but the session limit is a pain in my ass."
- "Yep. Reset was this morning at 3AM. Better believe as soon as the reset was announced, I was going full tilt for the rest of the day. I think I used about 75% of a week in a day."
That split is a genuinely useful data point on its own: which limit bites depends heavily on usage pattern — sustained all-day sessions run into the weekly cap first, while bursty evening or weekend work runs into the 5-hour session limit more often. /limit-reset helps the second group and does nothing for the first.
Commands that don't exist (yet)
Multiple commenters tried variations that Anthropic has not shipped: /reset-weekly, /no-limits, /reset-subscription, /reset-opus-5. None of these work — they're jokes riffing on the wishlist, not real commands, and Claude Code's own mod-adjacent commentary in the thread confirmed /reset-weekly and /no-limits "don't work" when people tried them. If you see a screenshot claiming otherwise, treat it as satire, not a leak.
The one legitimate near-neighbor already in Claude Code is /usage-credits (formerly /extra-usage), which lets you configure paid extra usage once you hit a limit — a different mechanism from /limit-reset's free, once-a-week session clear. /usage (aliases /cost, /stats) is read-only and reports limits without changing them.
Is it rolled out to you?
Reports in the thread are inconsistent enough to suggest an A/B test rather than a full rollout as of early September 2026:
- Several Max 5x and Max 20x users reported the command not existing or returning "A session-limit reset isn't available right now."
- Others confirmed it worked exactly as shown in the original post, on unspecified plans.
If /limit-reset doesn't show up when you type / in Claude Code, that's consistent with what other users are reporting — not a sign your installation is broken. Anthropic has not published this in official release notes as of this post; treat it as an in-progress rollout rather than a confirmed universal feature. Check /doctor for your installed Claude Code version, and see explainx.ai's complete slash command reference for how it fits alongside /usage and /usage-credits.
Update — September 3, 2026: If you're hitting session limits often, the other half of the problem is what each turn costs. See what actually costs you tokens in a Claude Code session.
Update — September 3, 2026: Max subscribers are reporting Fable 5.1 consuming limits far faster than Fable 5 — the reports, the structural reason, and what to do about it are in Claude Tag, Fable 5.1, and the Max plan gap.
Related reading
- Claude Code Commands: Complete Slash Command Reference
- Claude Usage Limits 2026 Timeline, Explained
- Anthropic Claude Code Limits: 17% Cut, September 2026
- Fable 5 Usage Credits, July 2026
- Will Fable 5 Rate Limits Reset When It Returns?
- Claude Code Desktop Auto-Continue at Usage Limit
This post is based on user reports from r/ClaudeAI as of Sept 3, 2026. /limit-reset has not been confirmed in official Anthropic release notes at time of publication; behavior, availability, and rollout status may change.