Yesterday Anthropic reset the 5-hour and weekly rate limits for every Claude user. The announcement tweet has 3.2 million views. I saw it at 1:18am on my phone, with 14% battery, about 5 hours after it happened.
A reset like that is basically free quota. If you were anywhere near your weekly cap, you got a clean slate. I missed most of my evening window because I simply didn't know, and I even have Twitter notifications turned on for @ClaudeDevs. Didn't help.
So, field notes on what I did about it. Two parts: finding out in time, and not burning the window once you have it.
Part 1: my phone now tells me
I didn't want another app. I wanted a push notification that says "limits got reset, go use them". Turns out you can get pretty far with three public feeds and ntfy.sh, which is a free push service that needs no account:
-
https://status.anthropic.com/history.atom(official incidents) -
https://nitter.net/ClaudeDevs/rss(the announcement account, readable as RSS) -
https://github.com/anthropics/claude-code/releases.atom(if you also want releases)
The whole watcher is about 150 lines of Python with no dependencies: fetch the feeds, remember what you've seen in a json file, and for anything new do a POST to your ntfy topic. Sending a push is literally one line:
curl -d "Claude limits got reset, go!" ntfy.sh/your-secret-topic
I run it as a Windows scheduled task every 15 minutes. If the tweet mentions words like "reset" or "rate limit" it sends with high priority so it actually makes noise. First test push I sent myself was the exact tweet I had missed. Felt a bit like getting the notification from a parallel universe where I went to bed informed.
One honest caveat: the nitter instance could die someday (they do that), so the watcher also reports when a source stops answering. The status page feed is the stable one.
Part 2: not wasting the window
A fresh window is only worth something if it lasts. My pattern was always the same: reset day, I go hard for two days, then I'm rationing tokens like it's wartime. So I built two small things for myself, both free and open source:
- usage-guard: a Claude Code plugin that watches your real plan quota from inside the session and tells you to slow down or push, based on your actual pace. Zero deps, local only.
- claude-usage-pacer: a tiny single-file web app that spreads your weekly quota over the days so you know if you're ahead or behind.
From what I've read, weekly limits are getting cut around July 13. If that's true, knowing when your quota comes back (and pacing it) stops being a nice-to-have.
Not sure the 15 minute polling is the right cadence tbh, maybe it's overkill. If you've solved the "never miss a reset" problem some other way, I'd really love to hear how. And if you try either tool, tell me what feels off, that feedback is worth more to me than stars 🙏
Top comments (0)