Not many people seem to know this, so here it is: the 5-hour usage window in Claude Code does not run on a fixed clock. The counter starts on your first prompt, and resets exactly 5 hours later — no matter how much (or how little) you did in between.
That little detail is worth a surprising amount.
Say you sit down at 9:00, fire off your first real prompt, and grind. Your window now resets at 14:00 — right in the middle of the afternoon, exactly when you do not want to be told to wait. You accidentally anchored your reset to the worst possible time.
The fix is silly and effective: start the window on purpose, early, with something throwaway.
Ask Claude "what's the weather today?" at 6:00 — from your phone, on the way to work — and your windows now fall at:
06:00 (first prompt)
11:00 reset
16:00 reset
21:00 reset
02:00 reset
Now the resets land in the gaps — your commute, lunch, after dinner — instead of mid-task. You can even put a tiny cron job on it so it happens before you wake up. The window is going to start somewhere; you might as well pick where.
This only shifts your 5-hour windows around. The separate weekly limit resets at a fixed time Anthropic assigns to your account (with its own timing for Opus), and priming a session early does nothing to that ceiling. So this is about convenience, not more usage — it stops the short window from resetting at the one moment you need it most.
Small trick, but I reach for it every morning.