How to maximize the 5-hour session window in Claude Code

Your usage window opens on your first request and resets five hours later. Not your first real request. Any request. A one-word “hi” starts the clock exactly like a forty-minute refactor does.

That asymmetry is the whole trick.

The problem. You start the clock by accident, at 9am, because that is when you opened the terminal. It resets at 2pm — five fresh hours handed to you mid-task, two of which you will spend in a meeting.

The fix. Start the clock before you get there.

Setup (one line)

1. Pick a time about two hours before you actually sit down.
2. Schedule something that costs nothing.

0 7 * * 1-5   claude -p "hi" >/dev/null 2>&1

It says hi. It exits. That’s the entire system.

What the day looks like

Time	What happens
07:00	Cron fires, window opens. Nobody is awake.
09:00	You sit down. Two hours already gone — spent on “hi”.
12:00	Window closes, quota resets. Conveniently, lunch.
13:00	Full window again, good until 18:00.

Three hours of your working day consumed an entire cycle. The other two went on breakfast and the commute.

Tip — Keep the scheduled task genuinely trivial. An overnight batch job burns the quota you are trying to protect. The goal is to spend the clock, not the budget.

Why it works

Starting the window is nearly free. Being inside it is what costs.

The clock never asks how large your first request was, only that there was one. So you are not conjuring extra quota — you are dragging the boundary onto hours you were never going to work anyway.

When it breaks

• You are hitting a weekly cap. The 5-hour window usually is not the only ceiling, and no amount of timing helps with the longer one. That wall needs a cheaper model or more capacity.
• Your start time moves. A 7am cron only pays off against a reliable 9am start. Drift two hours and you either waste the head start or the window closes before you arrive.

Before building a routine on any of this: send one message, note the time, and watch when your counter actually clears. Five hours from first request is the model to plan against — but confirm it against your own plan first.