Cursor · Cursor usage menu bar Mac
Cursor monthly usage, against the clock
UsagePool reads Cursor’s existing access token from its local state database, read-only, and requests the same monthly usage data the installed Cursor client uses — then shows the Cursor Models and API pools independently, each against the time left in the month. Usage above 100 percent gets a deliberately cautious warning, because Cursor’s payload cannot distinguish bonus capacity, credits or on-demand billing.
Cursor · Cursor Models Example reading
Usage 13% Window 41% Low
Limits UsagePool can show
- Cursor Models
- The included model pool.
- API Models
- Shown independently, in the popover’s
Cursor · Monthly · API Modelsgrammar.
Unique to Cursor
A month is a long window, which makes Cursor the provider where the marker spends most of its time far to the right and the comparison is easiest to misread by eye.
Cursor is also the one provider whose sign-in cannot be driven from a terminal, so the recovery button opens the Cursor app instead of a shell.
Because the two pools reset on Cursor’s own dates rather than a calendar month boundary, UsagePool follows the start and reset dates the payload reports rather than assuming the first of the month.
02 / 06 · Mechanism
How the reading is taken
UsagePool reads Cursor’s local state database, opened read-only. Here is exactly what happens on each refresh.
UsagePool opens Cursor’s local state database read-only, takes the access token that is already there, and keeps it in memory. It is never written to disk by UsagePool.
That token can be sent to exactly one place: Cursor’s allowlisted HTTPS usage endpoint, requesting the same current monthly usage data the installed Cursor client requests. The ephemeral network session refuses redirects, refuses cookies, refuses caching, and enforces a one-megabyte response limit while streaming.
Cursor Models and API pools appear independently, and their timing follows the start and reset dates Cursor itself reports.
03 / 06 · Stated here, not buried
Usage above 100 percent is reported cautiously
When a Cursor pool reports usage above 100 percent, UsagePool shows a cautious additional-usage warning instead of a confident number. The payload does not identify whether the excess is bonus capacity, credits, or on-demand billing, and inventing that distinction would be exactly the kind of comfortable lie this app exists to avoid.
The same restraint governs the orange ¢ glyph: it tells you additional usage was detected and sends you to the provider card, which says what the data can and cannot distinguish.
04 / 06 · Scope
What is never read or stored
Cursor’s access token is held in memory only, is never written by UsagePool, and can reach exactly one allowlisted endpoint — no other host, no redirect, no cookie jar.
UsagePool does not collect a usage-history archive or send your usage to its licensing service. It retains the settings and latest connection projections needed to show current limits. The privacy page lists this field by field →
05 / 06 · One product
One app, one download, five providers
The same application supports all five providers. Choose one with Free or Single, or use them together with Full for From $4 once.
06 / 06 · Start
Set up and start reading
Cursor installed, opened at least once, and signed in — the local state database only exists after a real sign-in.