Skip to content

Know how much Claude you have left.

Rate limits land mid-thought. Tokes sits in your menu bar showing how much of your Claude plan and GitHub Copilot allowance is left — before the wall, not after.

The Tokes popover, showing the Claude session and weekly limits, each with a usage chart, a percentage and a reset countdown.
The Tokes menu bar strip, magnified: the session bar red at 88 percent, two Claude bars below their limits, a divider, and the GitHub Copilot bar in green, with 88% beside it.
  • MIT licensed — source on GitHub
  • App Privacy: “Data Not Collected”
  • No account. No telemetry. No server.
  • 4.6 MB, native on Apple silicon & Intel
  • macOS 14+

Know before you hit the wall.

Three slim bars — session, weekly, per-model — sit in your menu bar and shift green, orange, red as you spend. No window to open.

The history the vendors don’t keep.

The usage APIs report only the current instant. Tokes samples locally on every poll and keeps eight days, so you can actually see the trend.

Nothing leaves your Mac.

No account, no analytics, no middleman server. A token goes to the service that issued it — nothing goes anywhere else, including to us.

Your plan’s state, in peripheral vision.

Session (5 hr), Weekly (7 day), and your plan’s per-model weekly cap, each a bar that fills as you spend and colors by how close you are. Add the optional percentage readout, or keep the icon alone — it’s off by default. At 100% the number turns red: you’re blocked. While polls fail it turns orange: the numbers may be stale. Tokes tells you which is which instead of guessing.

The menu bar strip shown twice, magnified: once with every limit in the green range, and once with one bar red and close to its cap.

Hover for the detail. Click to pin it.

Every limit with its own chart, a reset countdown, and — with GitHub Copilot on — your credits against the allowance you set. “Updated 42 sec ago” means the oldest number on screen, so freshness is never overstated. If a provider fails, the last known numbers stay put behind an honest banner instead of blanking.

A detail of the popover: the GitHub Copilot section with its dashed usage chart, credits used against the chosen allowance, and the footer line saying how long ago the numbers were updated.

Claude and GitHub Copilot, one menu bar item.

A divider in the strip, grouped sections in the popover, a dashed line on Copilot’s charts — two services you can tell apart at arm’s length. The Claude buckets are your account plan’s limits, the same ones claude.ai and the desktop apps draw down. The Copilot meter is measured against an allowance you choose, because GitHub doesn’t expose your plan to anyone — Tokes doesn’t pretend otherwise.

The popover with its limits grouped under separate Claude and GitHub Copilot headings, the Copilot chart drawn with a dashed line.
The menu bar strip, magnified: three Claude bars, a short vertical divider, then the GitHub Copilot bar, with 62% beside them.

One read-only permission. And a path you drive yourself.

GitHub Copilot connects with a real sign-in — Tokes’ own GitHub App asks for exactly one fine-grained permission, Account → Plan: read. It cannot see your code, repos, or issues. Claude works the other way around, on purpose: Anthropic doesn’t sanction third-party credential access, so you export your own sign-in with one Terminal command and hand Tokes the file. It never touches another app’s credential store. An optional Claude Code hook keeps the file fresh on every session start — and if you don’t open Claude Code for a while, Claude data goes stale and Tokes says so plainly rather than papering over it.

{
  "hooks" : {
    "SessionStart" : [
      {
        "hooks" : [
          {
            "command" : "umask 077; creds=$(security find-generic-password -s \"Claude Code-credentials\" -w 2>/dev/null) && printf '%s\n' \"$creds\" > ~/.claude/tokes-credentials.json; true",
            "type" : "command"
          }
        ],
        "matcher" : "*"
      }
    ]
  }
}

Free. And you can read the code that reads your usage.

Tokes is MIT-licensed and developed in the open. No account, no in-app purchases, no telemetry — and the Mac App Store build is compiled from the same public source as everything else, with nothing added. If you’d rather build it yourself, the repo is right there.

Questions

Is Tokes affiliated with Anthropic or GitHub?

No. Tokes is an independent project, not affiliated with, endorsed by, or sponsored by Anthropic or GitHub. “Claude” and “GitHub Copilot” are their owners’ trademarks, used here only to describe what Tokes monitors. Tokes requires your own active Claude subscription and/or GitHub Copilot seat — it doesn’t provide, resell, or include either service.

Can it see my code, prompts, or conversations?

No. Tokes transmits exactly one thing: a bearer token, in an Authorization header, to the service that issued it. It contacts Anthropic’s usage endpoint and GitHub’s billing and sign-in endpoints — that is the complete list, and the source is public if you’d like to check.

Why does connecting Claude take an export step?

GitHub sanctions third-party access to your own usage data; Anthropic currently doesn’t. So the GitHub side is one click, and on the Claude side you stay the actor: one Terminal command exports your own sign-in, and Tokes imports the file you picked. Settings walks you through both.

Does Tokes know my Copilot plan?

No — GitHub doesn’t expose entitlement to anyone. You pick your allowance (Copilot Pro, Pro+, Max, or a custom number) and Tokes measures against it.

I get Copilot through my organization.

Org-provided seats have no per-user billing data — that’s GitHub’s boundary, not a Tokes setting. Tokes tells you so directly instead of showing a meaningless 0%.

Does it count claude.ai usage too?

Yes, necessarily: the buckets Tokes reads are your account plan’s limits, shared by claude.ai, the desktop apps, and Claude Code alike.

What does it run on, and how does it update?

macOS 14 (Sonoma) or later, native on Apple silicon and Intel. Updates come through the App Store — there’s no background updater phoning home.

Why is my chart empty on day one?

The vendors’ APIs have no history at all, so Tokes can only chart what it has seen. You’ll get “Collecting history…” until a few samples exist, then trends — up to eight days.

The wall shouldn’t be a surprise.

Get Tokes (opens in a new tab)
  • Tokes is an independent project, not affiliated with, endorsed by, or sponsored by Anthropic or GitHub. Claude and GitHub Copilot are trademarks of their respective owners. Requires your own Claude subscription and/or GitHub Copilot seat.