Last prompt

The weekly limit is at 98 percent. There is room for one more prompt, so the crew thinks it over, and sends “fix it”.

Two limits, not one

Claude Pro and Max plans give Claude Code a five-hour session limit and a weekly limit. The five-hour one clears within hours. The weekly one resets once a week, so at 98 percent on a Tuesday, the rest of the week is what you have left.

In Claude Code, /usage shows your plan's usage limits, with the session's cost and activity stats. /cost and /stats open the same view.

Keep the numbers in view

A custom status line gets both limits from Claude Code as rate_limits.five_hour.used_percentage and rate_limits.seven_day.used_percentage, with the time each resets. They arrive for Pro and Max plans, after the session's first answer.

AgentValley draws them for you. Its status line puts bars for context, the five-hour limit and the weekly limit under the prompt, and Plan limits in the notch panel shows both with the time left until each resets. Plan limits stays off until you turn it on.

A prompt worth the last two percent

Fix it leaves Claude to work out what it is. Looking for it takes turns, and turns spend the limit you meant for the fix. Claude Code's own best practices ask for the symptom, the likely place, and what fixed looks like, plus a check Claude can run, such as a test or a build:

After a session timeout, login fails with "token expired". The refresh is in @src/auth/session.ts. Fix it so the token refreshes, then run npm test -- auth to check.

The @ in front of a path hands Claude that file, so it reads it before answering instead of searching for it. One small fix with a test that proves it is a better last prompt than a refactor that stops halfway when the limit runs out.