reset

<p align="center"><img src="docs/icon.png" width="128" alt="Reset icon"></p> <h1 align="center">Reset</h1> <p align="center">Know exactly when your AI usage window resets, get pinged on your phone when it does, and see what your usage is actually worth.</p> <p align="center"><a href="https://msfbeast.github.io/reset/"><b>Website</b></a> · <a href="https://github.com/msfbeast/reset/releases/latest"><b>Download</b></a> · <a href="#faq">FAQ</a> · <a href="#troubleshooting">Troubleshooting</a> · <a href="CHANGELOG.md">Changelog</a></p> <p align="center"><a href="https://github.com/msfbeast/reset/actions/workflows/tests.yml"><img src="https://github.com/msfbeast/reset/actions/workflows/tests.yml/badge.svg" alt="Tests"></a></p> <p align="center"><img src="docs/share-card.png" width="720" alt="Reset share card"></p>

Reset is a free, open source macOS app for people who live inside Claude Code (with Codex, Gemini CLI, Antigravity and Cursor support too). It sits in your menu bar, counts down to your next fresh window, and turns your local usage logs into a dashboard, desktop widgets and a card you can post.

Everything it reads stays on your Mac.

What it does

• Your window at a glance. A colored pill in the menu bar: orange "2:46 · 42%" as usual, red when the window is nearly empty or your pace runs out before the reset ("38% · out 10:07": 38% left, empty at 10:07 at this pace), green "ready" when a fresh window is waiting. Exact when live usage is on; estimated from your activity when it isn't, and labelled as such.
• Phone alerts while your Mac sleeps. Reset queues each reset alert on an ntfy server ahead of time, so it arrives on your phone even with the lid closed.
• Limit forecast. At your current pace, will you hit the limit before the reset? Reset warns you once per window, on your Mac and your phone.
• Weekly limit, early. On Pro and Max plans, Reset warns from 80% of the weekly limit (in the menu, the status line and one notification a week), so a used-up week doesn't come as a surprise. To keep an eye on it all the time, Settings → Appearance → Limits shows the weekly limit under the 5-hour window in the menu bar pill ("Both"), or on its own ("Weekly"). For Claude this needs live usage.
• Work and personal accounts. Use a Team account and a personal Pro plan? Each gets its own entry, window and countdown, and the dashboard splits costs, sessions and projects by account, each against its own plan price. The menu's top card, the menu bar and the mascot follow the account you're using. Live usage covers the account Claude Code is signed in to and, if you allow it, the other accounts signed in to the Claude desktop app.
• Notifications you can act on. Clicking one opens the dashboard; reset alerts have a Start now button and sign-in problems a Sign in button. Times follow your 12 or 24-hour clock.
• Auto-start. Optional. When a window runs out, Reset sends a one-word prompt so the next window starts right away instead of when you wake up.
• Dashboard. API-price value of your usage against your plan, cache savings, every 5-hour window of the week, token mix, when you build, cost per session and per project, and what used each session (main thread, subagents, each MCP server). Right-click a session to copy the command that resumes it; with two accounts it says which one the session ran under, and warns when Claude Code is signed in to the other. ⌘1–4 switch the range, ⌘R rescans.
• 8 desktop widgets, including Fuse: your window as a burning fuse, with where today's pace runs out and how much to slow down to make the reset. The others: countdown, gauge, arrival, today's spend, month calendar, week, and a Game Boy. When a fresh window is waiting, the countdown and Fuse widgets show a Start now button that starts it right from your desktop. Plus 8 looks for the menu card, and the other tools and accounts can each get a card too (Settings → Appearance).
• Mascots. Animated desktop pets whose mood and health bar follow your usage: fresh, focused, tired, asleep at the limit, waking at the reset.
• Share card. A 1200 × 675 image of your month for X.
• Claude Code integration. A status line for your terminal and an MCP server, so Claude can check how much window is left (and the weekly limit) and pace itself, including a per-task budget that tells it when to wrap up or switch to a smaller model. One click in Settings sets both up, and both say so when Reset isn't running rather than showing old numbers.
• Stay awake. Keeps the Mac from idle-sleeping (when plugged in, or always) so auto-start and alerts run on time, without a separate app. The display still sleeps.
• One-minute setup. A first-run guide picks your tools, signs Claude Code in, sets up phone alerts with a QR code, and takes your plan price.

<p align="center"><img src="docs/menubar.png" width="720" alt="Menu bar pill: as usual, almost empty, pace runs out first, fresh window waiting, weekly limit"></p> <p align="center"><img src="docs/dashboard.png" width="820" alt="Dashboard"></p> <p align="center"><img src="docs/widgets.png" width="820" alt="Widgets"></p> <p align="center"><img src="docs/looks.png" width="560" alt="Looks"></p>

Install

Download: grab the latest .dmg from Releases, open it and drag Reset to Applications.

Reset isn't notarized yet, so macOS blocks the first launch. Open Reset once, close the warning, then go to System Settings → Privacy & Security and click Open Anyway next to Reset. You only do this once. (Or run xattr -dr com.apple.quarantine /Applications/Reset.app in Terminal.)

The download is ad-hoc signed, so its widgets won't appear. For widgets, build it yourself as below.

Build from source (about two minutes):

You need macOS 14 or later, Xcode 16 or later, and XcodeGen:

brew install xcodegen
git clone https://github.com/msfbeast/reset.git
cd reset
./scripts/build.sh --install

That builds an ad-hoc signed app and copies it to /Applications.

Widgets need a real signature. macOS only lists widgets from apps signed with an Apple Development certificate. If you're signed in to Xcode with any Apple ID (a free one works), pass your team ID:

TEAM=ABCDE12345 ./scripts/build.sh --install

Find your team ID in Xcode under Settings → Accounts, or in Keychain Access on your "Apple Development" certificate.

Setting it up

The first launch opens a short setup guide that covers all of this. You can run it again from Settings → Advanced, or change anything below in Settings, which has four tabs: General (live usage, your tools, alerts), Automation (auto-start, stay awake), Appearance (look, mascots) and Advanced (commands, custom tools, Claude Code integration, diagnostics).

| Feature | How | |---|---| | Exact Claude usage | Settings → General: turn on Live usage from your Claude account. Reset reads the sign-in that the Claude Code CLI stores in your Keychain and asks Anthropic for your current usage every 2 minutes while you're using Claude Code, and every 5 minutes otherwise. If it says the sign-in expired, run claude auth login once. | | Phone alerts | Install the free ntfy app, subscribe to a long random topic name, and enter the same topic under Settings → General → Phone alerts. Anyone who knows the topic can read it, so make it unguessable. | | Auto-start | Settings → Automation: turn on Auto-start for Claude. It runs claude -p "hi" --model haiku (the command is under Advanced) once when a window you were watching runs out, while the Mac is awake. Each run uses a little of your quota. | | Value multiple | Press Add your plan price on the dashboard and enter what you pay per month. | | Stay awake | Settings → Automation → Stay awake: Off, When plugged in, or Always. Blocks idle sleep only; closing the lid still sleeps the Mac unless it's plugged in with an external display. | | Status line | Settings → Advanced → Claude Code integration → Add for me (it backs up settings.json first), or add to ~/.claude/settings.json: "statusLine": {"type": "command", "command": "cat \"$HOME/Library/Application Support/Reset/statusline.txt\""} | | MCP server | Add for me in the same place, or claude mcp add --scope user reset -- /Applications/Reset.app/Contents/MacOS/reset-mcp (with Reset's real location if it isn't in Applications). Tools: get_claude_usage, plus set_budget (task, max window %, optional downshift model) and clear_budget. With a budget set, the advice moves from normal to wrap-up at 80% of the cap to downshift at the cap. The active budget shows under the burn bar on the dashboard, with a Clear button. It's kept in budget.json next to widget.json and never leaves the Mac. |

FAQ

Does Claude checking its own window over MCP use up that window? Barely. Reset's MCP server makes no API call; it reads a file Reset already keeps on your Mac. The only cost is the answer landing in the conversation, about 150 to 250 tokens a check, plus about 350 tokens for the three tools' descriptions in context. That's less than Claude reading one small file.

Can an agent tell when the numbers are old? Yes. get_claude_usage includes usage_as_of and usage_age_minutes (when the usage was last read from Anthropic), and if the live check starts failing, live_check_failing_since_local, the reason, and usage_may_be_stale: true. The advice and any budget then say the reading may be out of date. If Reset itself quits, everything is marked stale.

How exact is the countdown? With live usage on, the reset time and % come straight from your Claude account, refreshed every 2 minutes while you work and every 5 when idle. Without it, Reset estimates from your Claude Code activity and labels the numbers "estimated", so you always know which you're looking at.

Does it track the weekly limit? Yes, on Pro and Max plans with live usage on. The menu shows the weekly %, it warns you from 80% (in the menu, the status line and one notification a week), and once it's used up it shows when it lifts. Claude sees it through the MCP server too.

How do task budgets work? Before a big task, Claude (or you, by asking it) sets a budget over MCP: a task name, the window % to stop at, and optionally a smaller model to fall back to. As the window nears that % Claude is told to wrap up, and past it to move to the fallback model or stop and check in. Reset doesn't switch models itself, and Claude can't change its own: it hands the remaining steps to subagents on that model (which start fresh, with only the brief Claude writes), or asks you to run /model to continue with the whole conversation. The cap is the window's total usage ("stop when the window hits 60%"), not the task's own share. It's guidance Claude follows, not a hard lock.

Does auto-start use up my usage? Almost none. It sends one word to the smallest model (Haiku) with no tools or MCP servers loaded, which is just enough to start the 5-hour clock. It waits for a working network instead of failing offline, and gives up after 4 tries.

Does it work with the lid closed? Phone alerts do: each one is queued on the ntfy server ahead of time, so it arrives while the Mac sleeps. Auto-start needs the Mac awake, so leave it plugged in with Stay awake on; on battery with the lid closed, it starts the window the moment the Mac wakes.

I have two Claude accounts. Each gets its own entry, window, costs and plan price, and you can name them (Settings → General → Claude accounts). Live usage, the forecast, auto-start and budgets follow the account Claude Code is signed in to; the other one is estimated. See Troubleshooting for details.

How does it split costs between two accounts? Claude Code