Do I need to start exactly at the recommended time?

No. It is a planning target so later resets land during work, not a hard deadline. Starting earlier or later shifts the following resets by the same amount. Use Adjust first trigger time to fine-tune, or change work hours and recalculate if your schedule changes.

Do Claude Code and Codex use the same reset rules?

Not necessarily at the provider level—limits, rolling windows, weekly caps, and plan notes can differ. 5hReset uses the same rolling-window planner for every tool profile. Set the window length to match the tool and plan you use, and check the provider’s current rules when they change.

Why is the recommended start time earlier than my workday?

Starting the first window slightly before work can place later resets at more useful times. For example, for a common 09:00–18:00 day with a five-hour window, starting around 06:00 can place refreshes near 11:00 and 16:00. The goal is a better trigger phase—not asking you to work earlier.

How does the 5-hour window refresh work?

Most plans start a rolling usage window on your first request, then refresh about five hours later. 5hReset schedules a lightweight CLI call (a simple hello-style prompt) at the recommended times so that window opens when you want. You do not need to understand cron, launchd, or PowerShell yourself—copy the agent prompt and let your coding agent install and test the scheduled task.

What schedules and usage limits does 5hReset support?

Time-based rolling windows (especially 5-hour) with custom work hours—early/late shifts and non-9-to-5 days included. Adjust the work period to the hours you want covered. It plans reset timing only: it does not increase quota, bypass limits, or optimize weekly/monthly caps. When tools differ, set each tool’s window separately.

5hReset

Plan AI Reset Times Around Your Workday

Find the best time to start your 5-hour AI usage window so resets happen while you're working — not when you're trying to finish.

Best Time to Start

06:00

Trigger early at 06:00 to get 3 full 5-hour quota periods during work,
but triggering at work start only gives you 2.

09:00–18:00

3 useful windows during work

05:45

06:00

06:15

Adjust first trigger time

Work hours09:00 → 18:00

Tool

5-hour rolling window + weekly cap (ChatGPT Plus). Pro plans may skip the 5-hour limit.

Recommended: schedule in ChatGPT Work

ChatGPT Work and Codex share one quota pool, so cloud refreshes in Work also refresh Codex. No local script: open a Work mode session in the browser (not a regular chat), paste the prompt below, and it can create scheduled tasks for each refresh time.

Use ChatGPT Work mode. All times below are in my timezone UTC. On weekdays at 06:00, 11:01, 16:01, send a short message saying hello at each of those times.

Open ChatGPT

Or install a scheduled task on this machine

Schedule format

0 6 * * 1,2,3,4,5 codex exec 'Reply with OK.' >> "$HOME/.5hreset.log" 2>&1 # 5hreset:codex
1 11 * * 1,2,3,4,5 codex exec 'Reply with OK.' >> "$HOME/.5hreset.log" 2>&1 # 5hreset:codex
1 16 * * 1,2,3,4,5 codex exec 'Reply with OK.' >> "$HOME/.5hreset.log" 2>&1 # 5hreset:codex

No need to set up scheduled tasks yourself,

5hReset helps you time the usage you already have. It does not add extra quota.

Make every bit of quota count

A rolling window refreshes from when you first use it—not at midnight. Start at the right time and the same allowance covers more of your workday.

Start at work

Open at 09:00 → first refresh around 14:00. Midday stretch with no new window.

09:00

14:00

18:00

First use

Refresh

Work ends

Trigger early

Open around 06:00 → refreshes near 11:00 and 16:00, while you are still working.

06:00

11:00

16:00

18:00

First use

Refresh

Work ends

Fine-tune freely

Nudge the first trigger so refreshes miss lunch—e.g. 06:15 → 11:15 and 16:15, clear of 12:00–13:00.

06:15

11:15

16:15

18:00

Fine-tuned

Refresh

Work ends

Lunch

Align refreshes to work
Place resets inside your hours so you are not waiting when you need the tools most.
Set it once
Copy a schedule for your agent or OS task runner—no need to remember every morning.
Same allowance
Nothing is added or unlocked. You only choose when the quota you already have starts.

Common questions

Do I need to start exactly at the recommended time?: No. It is a planning target so later resets land during work, not a hard deadline. Starting earlier or later shifts the following resets by the same amount. Use Adjust first trigger time to fine-tune, or change work hours and recalculate if your schedule changes.
Do Claude Code and Codex use the same reset rules?: Not necessarily at the provider level—limits, rolling windows, weekly caps, and plan notes can differ. 5hReset uses the same rolling-window planner for every tool profile. Set the window length to match the tool and plan you use, and check the provider’s current rules when they change.
Why is the recommended start time earlier than my workday?: Starting the first window slightly before work can place later resets at more useful times. For example, for a common 09:00–18:00 day with a five-hour window, starting around 06:00 can place refreshes near 11:00 and 16:00. The goal is a better trigger phase—not asking you to work earlier.
How does the 5-hour window refresh work?: Most plans start a rolling usage window on your first request, then refresh about five hours later. 5hReset schedules a lightweight CLI call (a simple hello-style prompt) at the recommended times so that window opens when you want. You do not need to understand cron, launchd, or PowerShell yourself—copy the agent prompt and let your coding agent install and test the scheduled task.
What schedules and usage limits does 5hReset support?: Time-based rolling windows (especially 5-hour) with custom work hours—early/late shifts and non-9-to-5 days included. Adjust the work period to the hours you want covered. It plans reset timing only: it does not increase quota, bypass limits, or optimize weekly/monthly caps. When tools differ, set each tool’s window separately.