v0.2.0 — current-cycle limit reporting

The default summary now shows how much of your plan's included usage you've consumed this billing cycle — and how much is left before you hit the limit — split into the same two buckets as the Cursor dashboard:

• Composer / Auto — composer-2.5, composer-2.5-fast, Auto
• Other models — explicitly selected / API models

==============================================================================
CURSOR CYCLE LIMITS  |  resets 2026-08-04
==============================================================================
Composer / Auto [###########...................]   36.7% used,   63.3% left
Other models    [####..........................]   12.4% used,   87.6% left
Included usage  $146.80 of $400.00 used  ($253.20 left)

Also new: cursor-usage --limits-json dumps the raw cycle-limits payload for scripting.

Details: data comes from POST /api/dashboard/get-current-period-usage (the endpoint the web dashboard itself uses), with GET /api/usage-summary as a fallback; server-computed percentages are shown verbatim. The section is skipped silently on accounts where these endpoints are unavailable — existing output and flags are unchanged. Still zero dependencies, Python 3.8+.

v0.1.0 — first release

First public release of cursor-usage — a cross-platform CLI that shows your Cursor usage, spend, and per-event logs from the terminal, using the session your Cursor app already has (no API key needed).

Install

pip install cursor-usage

Highlights

• 📊 Per-model token + compute-value summary for the current billing month
• 📅 --by-day breakdown
• 🧾 --csv per-event export
• 🌍 macOS / Linux / Windows · 🔋 zero required dependencies
• 🔒 Local & private — talks only to cursor.com, no telemetry

See the README and how it was built.

PyPI: https://pypi.org/project/cursor-usage/0.1.0/