Burned through 5 hours and forgot to reset?
The time after a missed reset still has value.
keep5 claims that value for you — turning what looks like idle time into time already served on your next lockout.
Get keep5
git clone https://github.com/imsodasu/keep5
curl -fsSL https://keep5.sh/install.sh | sh
soon
a missed reset, two ways
Reopens on time
The moment a reset comes due, keep5 fires — so the next window starts then, not whenever you happen back.
No extra quota, no tricks
It grants nothing you weren’t owed. It only stops the hours you were away from waiting to begin.
Runs on your machine
One Python file, one ordinary API call, no servers of ours. Nothing measured, sent, or stored.
How much valued time does keep5 reclaim?
FAQ
Does keep5 give me more quota, or make it faster?
No. It hands you no extra quota. When a reset comes due while you’re away, it just lets the window start on time — so the hours you were gone spend themselves counting down, not waiting to begin. Work straight through and it does nothing.
Would losing the five-hour limit free me? Does this apply to the weekly limit?
Usage also meters by the week, and the same dead reset forms against it — keep5 knocks at whichever reset is next. Dropping the five-hour cap wouldn’t free you: Codex dropped it on 2026-07-12, and its users still hit the weekly wall — sooner, if anything, since a limit nobody feels is a limit nobody paces against.
Is anything of mine collected?
keep5 runs on your own machine and makes one ordinary call to Anthropic’s API — the same endpoint your client already uses — reading only the rate-limit headers it sends back. No servers of ours, no telemetry, nothing stored. (The simulator above runs entirely in your browser.)
Which systems does it run on?
macOS and Linux. You only need it in one place, since it reopens the window for your account, not a device — so put that one copy on a machine that stays awake: a machine that sleeps misses the reset it was waiting for.
codex removed 5h limit on 2026-7-12