English中文日本語
Line drawing: a small monitor-headed character leans in and presses a big round amber button. Close-up in a dark room: a stubby arm reaches toward a round button glowing warm amber on a low pedestal.

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
View source
$ git clone https://github.com/imsodasu/keep5
$ curl -fsSL https://keep5.sh/install.sh | sh soon

Same time away. Different outcomes.

left alone
5h
5h
with keep5
5h
5h
keep5
valued time

Reopens every 5h window

Each time a 5-hour window resets while you’re away, keep5 opens the next one on time — so it starts then, not whenever you wander back. The time you come back late becomes valued waiting time.

Time back, shorter lockout

What it reclaims is valued time — the hours you’d have wasted become time already served on your next lockout, cutting it short. And it spends almost none of your usage: a single request to catch the reset.

Open source, runs on your device

One Python file, run on your own device — macOS or Linux, no account, no sign-up, no servers of ours. One ordinary API call, and nothing is stored.

How much valued time does keep5 reclaim?

left aloneyou wasted valued time
with keep5the waiting already happened
→ lockout
100% of that lockout, gone

FAQ

What does keep5 actually get me?

When a reset comes due while you’re away, that window would be missed. keep5 makes it start on time — so the hours you were away become time already served on your next lockout, turning idle waiting into value.

Does it take my API key, or collect anything?

No, you never hand us your API key, and we collect nothing. You set up a token once, locally — see the install guide. After that everything stays on your machine: one ordinary API call reading only the rate-limit headers, no servers of ours, no telemetry, nothing stored.

Does it burn my quota?

No. Opening a window costs only that one request — you spend quota only when you actually use it. keep5 starts the clock; it doesn’t run it down.

Could this get my account flagged?

Very unlikely. keep5 isn’t hammering the API — it fires one request, only at the reset moment, and nothing else. It unlocks nothing you weren’t entitled to; it just starts your own window on time. In use so far it’s caused no trouble. It’s an unofficial tool, though, so use your own judgment.

Why not just reset it myself?

You can — if you never forget, never sleep through it, never step away at the wrong hour. keep5 is for the times you do.

Is it free, and what does it run on?

Yes, it’s free and open source — one Python file on macOS or Linux. Install it once, on a machine that stays awake (a sleeping machine misses the reset).

Line drawing of the same scene: one character presses a lit button while another sits on the ledge with a phone, its own button switched off on the floor. A dark room late at night. On a concrete ledge one small terminal-faced creature leans over a glowing button, waiting to press it. A little way along the same ledge another one sits with its legs dangling, scrolling a phone, its own controller lying switched off on the floor below.
claude code still on shift codex off the clock
codex removed 5h limit on 2026-7-12