Editor Usage for Cursor

Editor Usage for Cursor is a deliberately narrow tool, and that narrowness is the point. Cursor's own web dashboard exists, but it's a browser tab you have to go and open. This widget puts the same information in your menu bar, which means you see it whether or not you went looking for it. For anyone who has ever discovered mid-month that they've burned through their included allowance, that ambient visibility is the entire value proposition. The feature depth is genuinely better than a single usage number. Progress bars are rendered per model, so you can see whether Claude or GPT calls are eating your allowance. Warning thresholds are configurable from 0 to 100% and, since V1.0.1, dynamically shift the bar color as you approach them. Refresh intervals run from 1 to 60 minutes. Display can be compact or detailed, and you can toggle request-tracking visibility and the maximum request number next to the menu bar icon. Launch at login keeps it running without intervention. The subscription-tracking side is where the product has matured. You get billing cycle status, days remaining, model-specific breakdowns, and monthly spending totals. V1.3.0 added support for Cursor's newer usage-based pricing model, a detailed breakdown of included subscription usage split into base and bonus, a detailed breakdown of paid usage with hard limits, and a clear view of bonus credits applied to your subscription. That distinction — what's covered by your plan versus what you're actually paying out of pocket — is the thing most people get wrong when they try to reason about AI spend from memory. The analytics layer covers input versus output token analysis, per-model cost tracking, and cache optimization metrics. Historical month navigation lets you page back through prior cycles to see whether your usage is trending up. V1.1.1 brought Business Team support, including the ability to see other members of a team, so a shared plan isn't a black box. The weaknesses are structural rather than fixable. It requires macOS 14.6 or later, so Windows and Linux developers are excluded entirely. It requires an active Cursor AI account, so it's useless to you if you haven't adopted Cursor. It tracks Cursor only — no OpenAI, no Anthropic, no Gemini direct spend. If your AI costs are spread across three providers, a single-provider widget gives you a false sense of completeness. And it's a companion to Cursor's API rather than a standalone monitor, so its numbers are only as current as Cursor's own endpoints. Where it fits: solo developers on a Mac who use Cursor as their primary editor and want to stop being surprised at the end of a billing cycle. Small teams on a shared Cursor plan who want per-member visibility without building anything. Power users who routinely approach their included allowance and want a threshold warning before they cross into paid usage. Where it doesn't: multi-provider shops, anyone not on macOS, anyone not on Cursor, and anyone who wants a mobile or