5hr silently warms up Claude Code and Codex before you wake up — so quota resets land right in your productive hours, not while you're idle.
How it works
5hr installs two cron jobs. Before you wake up, it sends a silent message to your AI tool — starting the rolling clock. You inherit the reset.
Cron runs 5hr start claude --warmup. A silent message is sent to Claude Code. The 5-hour rolling window starts. You're still asleep.
Only 2 hours have burned. You have 3 hours left in the window — and the reset is already counting down at 13:00.
Fresh 5-hour window opens right when you're deep in flow. Second warmup fires at 13:05 automatically.
Another full window for the evening session. Two productive windows, zero wasted quota, no manual work.
Commands
Lightweight CLI. No daemon. No cloud. All data stays in ~/.5hr/.
Set your working hours, timezone, provider, and how early to fire the warmup. Takes about a minute.
Installs OS-native scheduled jobs that fire warmups automatically every weekday. Shows exact times before confirming.
View your current config and change any setting interactively. Adjust warmup offset, provider, or hours without touching JSON.
See recommended session windows based on your config and past history. Recommendations refine over time.
Total sessions, average duration, utilization score, estimated wasted quota, and week-over-week trend. All local.
Verifies provider binaries in PATH, config validity, OS scheduler availability, and storage permissions.
Get started
5hr init
— set your hours & provider
5hr schedule
— install cron, done