"5-hour limit reached" in Claude: what it means and what to do

What the message actually means

Paid Claude plans have two clocks running at once:

• The session limit, a five-hour window that starts with your first message and resets five hours later. This is the one you just hit.
• The weekly limit, which covers all models and resets on a fixed day and time assigned to your account.

Hitting the session limit doesn't touch your weekly allowance, and waiting out a session does nothing for a weekly limit. If Claude said weekly rather than 5-hour, see how the limits differ, because that wait is measured in days.

Claude warns you before it happens, too. Anthropic's apps show "Approaching 5-hour limit." as you get close, and many Claude Code users report a 90% warning first.

Find your exact reset time

1. The limit message itself names the time, for example "resets 3:45pm".
2. Open Settings → Usage on claude.ai. The current session bar shows a countdown such as "Resets in 3 hr 39 min".
3. In Claude Code, run /usage.

Paste the message into the countdown on our homepage and it will read the time out of it, show a live clock, and email you the moment you're back so you can close the tab.

What to do with the next ten minutes

• Write down where you are. The next session starts fresh; a three-line note about the goal, the decision you'd just made and the next step saves re-explaining everything later.
• Don't paste it all back in. When you return, start a new chat with that short summary instead of continuing the long thread. Continuing costs you the whole conversation again on every reply.
• Do the parts that don't need Claude. Review the last output, run the tests, gather the files you'll need.
• Consider usage credits only if the deadline is real. They bill separately at standard API rates on Pro and Max. See how usage credits work, including the auto-reload setting that can quietly keep charging.

Why you hit it this time

The session limit isn't a message count. It moves with how much work each message costs, so these are the usual culprits:

• A very long conversation. Every reply re-reads the whole thread. The fiftieth message in a long chat can cost many times what the first one did, which is why limits often arrive late in a long session that felt fine all morning.
• Large attachments and images, which are re-read along with the thread.
• Heavy Claude Code work. Big file reads, long tool chains and agents consume a lot, and it comes out of the same pool as your chats.
• A heavier model for light work. Simple questions don't need your most capable model.

Make the next session last longer

• Start fresh chats at task boundaries. Ask for a short summary, open a new chat, paste it in.
• In Claude Code, use /compact and /clear when you switch tasks, and keep CLAUDE.md short.
• Check the meter before a big task. Starting something large with 15% left, or ten minutes before a reset, wastes both.
• Batch small questions into one message rather than ten.

If you're doing all of this and still running out several times a week, the plan may genuinely be too small: the plan calculator turns your own usage percentages into a straight answer.