If your team uses Cursor on an enterprise plan, there’s a good chance someone has a browser tab open right now to the Cursor dashboard.
That tab exists because the usage view inside Cursor never worked on our enterprise accounts. The only reliable way to know how much of the month was left was to leave the editor and go look.
We got tired of the tab. So we built Cursor Usage Status, a small extension that puts your usage in the editor’s status bar, where you’re already looking.
For one developer, checking a dashboard now and then is a minor annoyance. For a team, it adds up. Nobody knows they’re close to the limit until they hit it, and whoever is responsible for the budget finds out after the fact.
We kept the dashboard pinned in a tab and checked it between tasks. The number was always there. The problem was that nobody looked at it when it mattered.
The idea was simple: take the same usage data the dashboard shows and put it in the status bar, refreshed in the background every few minutes.
The catch was that none of it was documented. Cursor doesn’t publish a usage API for third-party tools. So the extension works the way the dashboard does. It reads your existing Cursor sign-in from Cursor’s local database and calls the same Cursor-hosted endpoints the dashboard uses. There’s no separate login and nothing to configure.
The first version shipped in April. Enterprise accounts were billed by request quota at the time, so it showed the requests you had left for the model you cared about. On Team and Pro accounts, it showed remaining dollars. Either way, the tab could close.
We knew those endpoints could change without warning. In August, they did.
On August 24, 2026, Cursor replaced request quotas with token-based pricing, billed as dollar spend against a per-user monthly cap. The routes the extension depended on were deleted. There was no quota left to report and no endpoint left to ask.
Letting it go would have meant going back to the browser tab, now watching a dollar figure instead of a request count. So we rebuilt it around the question every developer on a token plan now has: how much have I spent, and will it last the month?
Every refresh pulls three things from Cursor: what you’ve spent this cycle, your per-user monthly limit, and when your billing cycle started. The status bar shows what’s left, like “$60.67 left.”
Hover over it, and the tooltip breaks down spend by model, with input and output token counts for each. When one model is running up the bill and another costs almost nothing, you want to know that before the month ends, not after.
A few other details came out of using it every day:
We were careful not to build something that nags. Notifications only fire when the projection gets worse. If your pace holds or improves, you won’t hear from it. You can dismiss alerts for the rest of the cycle, and they come back on their own when the next one starts. It also won’t guess until there’s enough data to mean something: at least 15% of the cycle elapsed and 5% of the limit spent.
Building against a pricing model that was days old meant running into things nobody had written down.
The first cycle wasn’t a month. The pricing change produced a short billing cycle from August 24 to September 1. Cursor cycles aren’t reliably aligned to the calendar, so the extension uses the end date Cursor reports whenever one is available and only falls back to calculating one month from the cycle start when it isn’t.
The dashboard runs a little behind. While testing, we watched the dashboard header read 70 cents while live spend sat at $0.7673. About ten minutes later the header caught up to 77 cents. The header is driven by a separate counter that’s rounded and updated on a delay. The extension reads the live figure, so it can briefly show a little more than the header. The dashboard’s “Total usage” tile matches what we report.
There was an easier way to get one of the numbers we needed. Cursor has an endpoint that returns the dashboard’s overall spend figure directly. The problem is that its response includes every team member’s name and email address, with no way to filter it down to just you.
We decided the extension would not call it. Nobody installing a status bar widget should pull their coworkers’ personal information onto their machine to see their own spend.
The same thinking shaped the rest of the security design. The extension reads your access token from disk on each refresh and never stores it. The token only travels over HTTPS, and only to the API origin you’ve configured. Error messages stay generic so tokens and file paths don’t end up on screen.
Cursor Usage Status is unofficial. It isn’t affiliated with or endorsed by Cursor, and it depends on endpoints Cursor doesn’t document and can change at any time. We’ve already seen that happen once. If it happens again, the extension may break again, and we’d rather say that up front.
Once AI coding tools bill by the token, usage stops being a quota you might bump into and becomes a budget someone is accountable for. That makes visibility more important, and it matters where developers are working. A number in a browser tab gets checked when someone remembers. A number in the status bar gets seen all day.
Cursor Usage Status is free and MIT licensed. It’s verified on Team accounts, and Business and Enterprise plans resolve the same way. Individual and Pro plans are untested. Cursor doesn’t report a limit for those accounts, so you can set your own in the settings to get a remaining balance and warning colors.
