Free, with the source on GitHub

Know if you'll make it to reset.

Fuel Gauge watches your Claude Code, Codex, and Grok Bot limits from the menu bar, and tells you if they'll last until they reset.

brew install --cask coreyhaines31/tap/fuelgauge

macOS 14 Sonoma or later · Apple Silicon and Intel · No account

Or ask your coding agent:

Install Fuel Gauge on my Mac: run `brew install --cask coreyhaines31/tap/fuelgauge`, open Fuel Gauge, then run `fuelgauge install-statusline` and `fuelgauge status`.

The verdict comes first.

Percent used doesn't tell you much on its own. 55% with three hours left is fine at one pace and a problem at another. Fuel Gauge does the math and says which.

A glyph that reads at a glance

The needle shows the fuel left in whichever limit is closest to running out. It turns orange when a limit is on pace to run out before it resets, and red when one is out.

One card per limit

Claude Code's 5-hour and weekly limits, Codex weekly, and Grok Bot weekly. The most urgent is on top, with a chart of your usage so far and where it's headed.

How much you can still use

“Using 28% an hour. You can use up to 15% an hour and still make it.” So you know whether to slow down, and by how much.

Your limits, right under the prompt.

Turn on the status line and Claude Code shows the forecast after every reply. Orange means a limit is on pace to run out early.

  • Turn it on from the app, or with one command.
  • Keeps your existing status line and adds a line under it.
  • Backs up settings.json first. fuelgauge uninstall-statusline takes it out again.
fuelgauge install-statusline

How the forecast works.

No guesswork about your plan. It reads the same numbers your tools show you, and watches how fast they climb.

1

It reads what's already there

A reading every time Claude Code replies, through its status line. Codex's session logs and Grok Bot's local usage cache fill in the rest.

2

It measures your pace

How much usage climbed over the recent stretch: the last hour for 5-hour limits, the last day for weekly ones.

3

It projects to the reset

If that pace holds, do you hit 100% first? You get a verdict and a range, not a fake-precise minute.

It needs about 10 minutes of readings before it forecasts, and says “Learning your pace” until then. It's an estimate from your recent pace, not a promise.

Let your agent check first.

fuelgauge status exits with code 2 when a limit is forecast to run out before it resets. So an agent can check before a big job, and ask you before it burns through what's left.

  • fuelgauge status for the verdict on every limit
  • fuelgauge status --json for the details
  • fuelgauge history for the readings behind it

Add this to your CLAUDE.md or AGENTS.md

Then every agent session checks before the expensive stuff.

Before starting a long or expensive task, run `fuelgauge status`. If it exits with code 2, a Claude Code, Codex, or Grok Bot limit is forecast to run out before it resets: tell me which one and when, and ask before starting, or switch to a cheaper model. `fuelgauge status --json` has the details.

Quiet, and stays on your Mac.

It reads only what Claude Code, Codex, and Grok Bot already save on your Mac.

Local files only

No browser cookies, no keychain, no sign-in. It never asks for your accounts.

No Full Disk Access

It doesn't need it. Everything it reads sits in your home folder.

Zero telemetry

The only network request is the check for updates.

One alert, early

Once per window, when the forecast says you'll run out at least 30 minutes early. Alerts at 50, 80, or 95% used are optional.

Track what you use

Pick which tools it watches in Settings › Tools.

Free

No trial, no subscription. Source on GitHub, signed and notarized by Apple.

Questions

Is it accurate?

It's an estimate from your recent pace, not a promise. Speed up or slow down and the forecast moves with you. That's why it shows a range, like “Between 11:31a and 12:14p at your recent pace,” instead of one exact minute, and why it waits for about 10 minutes of readings before it forecasts at all.

Does it work with Claude Pro and Max?

Yes. It uses the 5-hour and weekly limits Claude Code reports for your plan, so it works on Pro and Max. The status line is where those readings come from, so turn it on.

Which tools does it track?

Claude Code's 5-hour and weekly limits, Codex's weekly limit, and Grok Bot's weekly limit. Choose which ones to watch in Settings › Tools.

Does it send my data anywhere?

No. It reads only what those tools already save on your Mac. No browser cookies, no Full Disk Access, no keychain, no sign-in, and zero telemetry. The only network request is the check for updates.

How is it different from CodexBar?

CodexBar covers far more providers, over 100, and leads with percent used. Fuel Gauge covers three tools and leads with the verdict: will you make it to reset. It adds a Claude Code status line and an exit code agents can check, and it reads only local files. The full comparison.

How do I remove it?

Run fuelgauge uninstall-statusline first, so your Claude Code status line goes back to how it was. Then run brew uninstall --cask fuelgauge. If you installed from the DMG, drag Fuel Gauge from Applications to the Trash instead.

Is it really free?

Yes, at home or at work. No account, no trial, no subscription. The source is on GitHub under the FSL-1.1-MIT license.

Which Macs does it run on?

Any Mac with macOS 14 Sonoma or later, Apple Silicon or Intel.

Make it to reset.

Free. No account, no subscription.

brew install --cask coreyhaines31/tap/fuelgauge

macOS 14 Sonoma or later · Apple Silicon and Intel · Or ask your coding agent