cursor-cli-usage
Cursor account usage and quota monitor. It follows the same dependency-free
interface as the other /code/*usage tools.
The tool targets the Cursor CLI harness, but reports account-wide Cursor quota. It does not estimate usage from local CLI sessions.
Example output
Cursor usage
Status: live
Plan: 6.1% used
Resets: 1787506237000
Statusline:
cursor:q:6.1%used reset:12d20h
Install
uv tool install cursor-cli-usage
For local development:
uv tool install .
Commands
| Command | Description |
|---|---|
cursor-cli-usage |
Show current account usage |
cursor-cli-usage status |
Same as above |
cursor-cli-usage json |
Print normalized JSON |
cursor-cli-usage statusline |
Print compact cached output |
cursor-cli-usage refresh |
Refresh the cache and print status |
cursor-cli-usage daemon [-i SECS] |
Keep the cache fresh |
cursor-cli-usage install |
Print installation instructions |
Authentication and data
For every live request, the tool first asks the installed Cursor CLI for its
current authentication state with agent status --format json. If the CLI is
unavailable, it falls back to cursorAuth/accessToken in Cursor IDE's local
state.vscdb. On Linux, the fallback follows XDG_CONFIG_HOME when it is set.
It sends only the current access token to Cursor's dashboard usage service. It
never refreshes, rotates, or modifies Cursor-owned credentials.
The normalized JSON includes:
provider,source,retrieved_at, andstatus- billing-cycle start and end
- plan and spend-limit usage
- models assigned to Cursor's automatic usage bucket
status is live, cached, stale, or unavailable. Errors and caches do
not include the access token or Cursor account identity.
The tool writes only its own non-secret cache at
~/.cursor/usage-limits.json. JSON results report whether they are live,
cached, stale, or unavailable.
Environment overrides:
CURSOR_USAGE_AGENT: alternate Cursor CLI executableCURSOR_USAGE_STATE_DB: alternate Cursorstate.vscdbpathCURSOR_USAGE_FILE: alternate cache path
The usage endpoint is undocumented and may change when Cursor changes its dashboard implementation.
Options
usage: cursor-cli-usage [-h] [-i INTERVAL] [--max-age MAX_AGE] [--refresh]
{status,json,daemon,statusline,refresh,install}
--max-age SECS: maximum cache age used bystatusline--refresh: bypass the cache forstatusline-i SECS: daemon refresh interval
Development
uv --no-config lock --check
uv --no-config run --locked python -m unittest discover -s tests
uv --no-config build --no-sources
Metadata
Release files for cursor-cli-usage 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| cursor_cli_usage-0.1.1.tar.gz | 7.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cursor_cli_usage-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 14.4 kB
Release files / cursor_cli_usage-0.1.1.tar.gz
| Download URL | cursor_cli_usage-0.1.1.tar.gz |
|---|---|
| Size | 7.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
186ec74579e0a53c6fe0d6bb7f09cac4ceeca96bb76b96cab98a332f7fc0a65f
|
|
BLAKE2b-256 checksum How to use checksums |
d7a27bbc54592b6e496689b1239c8b8dcb6016cdaaebd4db53c98f5ad46efb7e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.12.5 {"installer":{"name":"uv","version":"0.12.5","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / cursor_cli_usage-0.1.1-py3-none-any.whl
| Download URL | cursor_cli_usage-0.1.1-py3-none-any.whl |
|---|---|
| Size | 6.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
790e980a1ce99e7516ab268775350a0e0d4d613a9b3c167e65ced165ec5662a5
|
|
BLAKE2b-256 checksum How to use checksums |
6dd73206360ac88f1b98ad673f800affe989f16363a63f7ace6bf87af8c52f46
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.12.5 {"installer":{"name":"uv","version":"0.12.5","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|