# Know what is left of your AI plans before you hit the wall.

Canonical page: https://vitalsmac.com/features/ai-usage-limits

Claude, Codex, Copilot, Cursor and the rest each cut you off at a different point: a 5-hour session, a week, a month. Vitals shows how much is left of each, when it resets and whether you will make it there, for every account on this Mac, in the window and the menu bar.

## Plans: Every plan you pay for, on one tab.

Claude, Codex, GitHub Copilot, Cursor, Antigravity, Grok, Ollama and OpenCode each get a ring in their maker's colour with what is left inside it, for every account signed in on this Mac, so you stop checking eight dashboards.

- Claude, Codex, GitHub Copilot, Cursor, Antigravity, Grok, Ollama and OpenCode
- A ring per plan, in its maker's colour
- Every account on this Mac, each Claude Code profile included
- Asked the way the tool itself asks, with nothing else sent

## Limits: The session, the week, the month and the model, with their resets.

One plan can cut you off in four different ways. Vitals shows each window on its own, the 5-hour session, the week, the month and a model's own limit, with how much is left and exactly when it comes back.

- The 5-hour session
- The week and the month
- A model's own limit, such as Opus this week
- When each one resets, down to the minute

## Pace: Will you make it to the reset?

Vitals compares what you have used with how far through the window you are, and tells you plainly: on pace with 10% to spare, or runs out in four days at this rate. For Claude Code and Codex it counts the tokens too.

- On pace, or running out first, in words
- The tokens Claude Code and Codex used today and this week
- Where they went, and which models took them
- Counted from the logs the tools keep on your Mac

## Menu bar: A glance instead of a command.

Put any plan in the menu bar, a number after its maker's mark, with the 5-hour session beside it if you want it. Turn it on in Settings → Integrations; it stays off until you do.

- A number per provider, after its mark
- The 5-hour session beside it, if you want it
- The dropdown's Agents tab has plans, tokens and sessions
- Off until you turn it on in Settings → Integrations

## Why it matters: ai usage limits on a Mac

Every AI plan is a set of windows. Claude has a 5-hour session and a week, Codex its own, GitHub Copilot counts premium requests by the month, Cursor has a billing cycle, and a model can have a limit of its own on top. Each tool shows its own number somewhere, in a command, a settings page or a web dashboard, and none of them shows the others.

So you find out at the worst moment: mid-task, with the agent stopped and a message telling you to come back in two hours. Or you stop early, sure the week must be nearly gone, with a day of it left.

Vitals asks each maker the way the tool itself does, with the sign-in already on your Mac, and puts every plan on one tab: a ring with what is left, when it resets, and whether you are on pace or will run out first. For Claude Code and Codex it counts the tokens too, from the logs they keep. Any plan can be a menu bar item, so the answer is a glance, not a command.

## How to use it

1. **Turn it on.** Settings → Integrations → Show Usage Limits of Your AI Plans. Vitals uses the sign-in each tool keeps on your Mac and keeps no copy of it. For Claude Code inside the Claude app, macOS asks once whether Vitals may read it.
2. **Read the rings.** On the Agents tab, one ring per plan in its maker's colour: the week, the 5-hour session and a model's own limit, each with what is left, when it resets and whether you are on pace. Every account signed in on this Mac gets its own, each Claude Code profile included.
3. **Put it in the menu bar.** Settings → Layout → Menu Bar: a number per provider after its mark, with the 5-hour session beside it if you want it. The dropdown's Agents tab has the plans, the tokens and the sessions.
4. **Count the tokens.** For Claude Code and Codex, the tab shows the tokens used today and this week, where they went and which models took them.

## Compared with Activity Monitor

| | Activity Monitor | Vitals |
| --- | --- | --- |
| Where you look | Each tool's own command or dashboard | One tab, for eight makers |
| Which limits | The one that just stopped you | The session, the week, the month and a model's own, each with its reset |
| On pace | You work it out | On pace, or will run out first, in words |
| Tokens | The tool's own cost command | Today and this week, by model, from the logs |
| Menu bar | None | A number per provider |

## Questions

### How do I turn it on?

Settings → Integrations → Show Usage Limits of Your AI Plans. The Agents tab then shows every plan this Mac is signed in to.

### Does Vitals need my password or an API key?

No. It uses the sign-in each tool already keeps on your Mac, the same way the tool does, and sends nothing else. There is nothing to paste in.

### Which plans does it read?

Claude, Codex, GitHub Copilot, Cursor, Antigravity, Grok, Ollama and OpenCode, for every account signed in on this Mac. It also counts the tokens Claude Code and Codex used today and this week.

### Can I see it without opening the window?

Yes. Any plan can be its own menu bar item, and the dropdown shows them all.

### Does it work with more than one account?

Yes. Every account signed in on this Mac gets its own rings, each Claude Code profile included.

### Does Vitals keep a copy of my sign-in?

No. It reads the sign-in the tool already keeps on your Mac, asks the maker with it the way the tool does, and keeps nothing. Nothing else is sent.

### What if I am not signed in to one of the tools?

A tool you are not signed in to is simply left out. Sign in with the tool and it appears.

### Can it warn me before I run out?

The ring tells you whether you are on pace or will run out first, and a plan in the menu bar is always in view, so you see it coming instead of hitting it mid-task.

## Read on

- [How to check your Claude Code and Codex usage limits on a Mac](https://vitalsmac.com/claude-code-codex-usage-limits-mac)
- [Claude Code using too much memory or CPU on a Mac? How to find it, and get it back](https://vitalsmac.com/claude-code-memory-usage-mac)
- [Codex using high CPU or memory on a Mac? How to find the cause](https://vitalsmac.com/codex-high-cpu-mac)
- [Vitals vs Activity Monitor](https://vitalsmac.com/vs/activity-monitor)

## More of Vitals

Every feature is at [vitalsmac.com/features](https://vitalsmac.com/features). Vitals is one payment, with every update for life: [pricing](https://vitalsmac.com/pricing).