Agent HUD · Guides · Supported clients
Cursor usage and quota on Mac
Cursor reports usage for the whole account, not for one machine, which changes what Agent HUD can say about it.
At a glance
| Quota | Usage summary rows, billing cycle |
|---|---|
| Account | Signed-in user, email label |
| Running · completion | No · stop hook |
| Credentials read | Session token, read only |
What you see
Rows for overall usage, models, third-party models, personal, team and extra usage, with your billing cycle as the period and your membership as the plan.
How the account is named
The signed-in user behind Cursor's own session token, labelled with the email Cursor has cached.
Running turns and completions
Running turns are not detected, and completions arrive through the stop hook. Usage events group into account-wide sessions that are never marked running and are not attributed to this Mac.
What Agent HUD reads
Only Cursor's session token and cached email from its own storage — nothing else local. Nothing is refreshed or written back; an expired token is a sign-in notice until Cursor renews it itself.
Common questions
- Why do my Cursor sessions never show as running?
- Cursor's usage events are reported for the account after the fact rather than as work happens, so there is nothing live to follow. Completions still arrive through the stop hook.
- Why do I see usage I did not generate on this Mac?
- Because Cursor reports it per account. Events seen from another machine merge rather than double, so the totals stay right, but they describe the account rather than this computer.
Last updated: 2026-09-20 · The behaviour described here is documented in full, with the code it comes from, in Agent HUD Open. providers.md