Cursor Curse Monitor by Lorapok Labs
Get extension

Lorapok Labs · VS Code–based AI IDEs

Open VSX · loading… VS Code · loading… Release v—

Know your Cursor limits before they know you.

Works across major VS Code–wrapper IDEs — live included quota, billing cycle, on-demand spend, and automatic free fallback to Composer 2.5 (Fast off). Install from Open VSX or the Marketplace.

  • Real-time quota & billing cycle
  • Personal budget cap & warnings
  • Private — data stays on your machine

IDE extension

Install from Open VSX Open VSX hosts · v— VS Code Marketplace v—

Browser extension

Firefox Add-ons AMO · v— Chrome extension Direct zip download

Other

Download VSIX GitHub Release · — View on GitHub Source & releases

Open source — help shape the next release: Join the community · Good first issues · Project #4

Extension ID lorapok-labs.cursor-curse-monitor-by-lorapok

Explore the product

Interactive feature map

Select a node on the orbit to see how each capability fits the Lorapok ecosystem — IDE, browser, Mission Control, and roadmap.

Click a satellite to explore

Open source momentum

Live GitHub traffic & CI — synced from Mission Control and npm run site:data

Universal compatibility

Works with every major VS Code–based AI IDE

Install from Open VSX or the VS Code Marketplace — the same extension runs in Cursor, Windsurf, VSCodium, and every VS Code wrapper IDE listed below.

Need another tool from Lorapok Labs? Visit lorapok.tech for more software & experiments.

Full Lorapok ecosystem

IDE extension, browser guard, and Mission Control

One product family — usage in Cursor, credential protection in the browser, and ops in the admin panel.

Live usage inside your AI IDE

One extension for all VS Code wrapper IDEs. Quota meters, billing cycle, budget caps, Composer 2.5 fallback, and local credential scanning — works in Cursor, Windsurf, VSCodium, Void, Gitpod, Trae, Kiro, and every Open VSX / VS Code Marketplace host.

System topology

Architecture — data, deploy, and edge cases

Animated workflow simulations for the full Lorapok stack: local extensions, Mission Control, Production Deployment, and marketplace guards.

Local-first IDE and browser surfaces. Usage and scans stay on your machine except authenticated Cursor API calls.

Canonical source: README architecture · Mission Control

Behind the scenes

How the monorepo ships

Four surfaces, one release train — Mission Control operators, procedure tracking, cred vault secrets, and agent commands that keep the public site honest.

IDE extension VS Code wrappers · Open VSX Browser extension Firefox AMO · Chrome zip Marketing site GitHub Pages · site-data Mission Control Cloudflare Pages · ops

Procedure + Project #4

Non-trivial work lands in procedure/ with a GitHub issue on Project #4. Agents say Update? for status and next for the top queue item — progress stays in procedure files, not chat dumps.

AI agent commands · Task tracking

Cred vault

API tokens and webhooks live in the GPG cred vault — never in git, wrangler.toml, or client bundles. Sync scripts push to Cloudflare and GitHub Actions after rotation.

Architecture wiki · Agent init

Release integrity

Dynamic versioning, marketplace gates, and release checks keep VSIX / AMO / Open VSX / Pages deploys aligned. Mission Control is the opt-in path for marketplace publish.

Deployment · System topology

Contribute

Good-first issues and CONTRIBUTING live on GitHub. Chrysalis (floating Larvae) points newcomers at the public board, footers, and hero/subscribe CTAs.

CONTRIBUTING.md · Good first issues

Deep dive: Engineering history · Public Website wiki · Ecosystem roadmap

Why developers install it

Everything you need to stay inside your quota

Six core capabilities — each with a product screenshot. Tap any image to view full size.

Live dashboard

Sidebar panel and status bar with Auto/API meters, included quota, and auto-refresh — no extra notification tab.

Budget cap

Set a personal USD limit, track on-demand spend, and get warned before you overshoot.

Free fallback

At 100% included usage, auto-switch to Composer 2.5 (Fast off) — the free slow pool.

Privacy-first

Your auth token never leaves your machine. No telemetry, no shared team dashboard.

Safe DB writes

Read-only while Cursor runs; fallback writes only after quit with WAL backups and integrity checks.

Multi-account

Discover multiple installs on one machine, switch accounts in the dashboard, and read today's accepted lines from the active profile.

Complete feature set

Every install includes the full monitoring stack — local-first, no account required beyond your IDE login.

  • Multi-account switching

    System login plus discovered installs — switch in the dashboard or browser extension without mixing quotas.

  • Today & cycle insights

    Local accepted-line stats for today and the billing cycle from the active install's SQLite store.

  • Sidebar dashboard

    Activity bar panel with included quota, Auto/API meters, billing reset, on-demand spend, local insights, and cycle trend.

  • Status bar meter

    Live usage percentage in the editor status bar — plan, Auto/API, or both.

  • Auto refresh

    Polls the Cursor API on a schedule (default 60s) with manual refresh on demand.

  • Personal budget cap

    Set a USD limit in settings and track spend against your included quota.

  • Billing cycle countdown

    See days until reset so you can pace usage through the month.

  • Limit warnings

    Native workbench toasts overlay the open editor at your threshold (default 80%). No extra Notification tab.

  • Composer 2.5 fallback

    Optional auto-switch to Composer 2.5 (Fast off) when usage reaches 100%.

  • Team-aware limits

    Surfaces individual vs team limit type from your Cursor session context.

  • Security scanner

    Local credential detection in files, clipboard, and commits — Manage Processes–style alerts with redacted previews only.

  • Privacy-first

    Auth stays on your machine. No extension telemetry unless you opt in.

  • Safe DB writes

    Read-only while Cursor runs; fallback writes only after quit with WAL backups.

  • All Open VSX editors & VS Code

    Works in Cursor, VSCodium, Windsurf, and Visual Studio Code via Open VSX and the VS Code Marketplace.

  • Local insights

    Today’s accepted lines, active models, and recent session titles from local Cursor storage — never chat bodies.

  • Cycle trend

    Sparkline of included usage over the billing cycle, stored only on this machine.

  • Fully configurable

    Poll interval, status bar source, warnings, budget, and fallback toggles in settings.

Get started in minutes

Install —

Commands below update automatically from CI — always pointed at the latest release.

Recommended · Cursor

Open VSX (Cursor Marketplace)

Search Extensions for:

lorapok-labs.cursor-curse-monitor-by-lorapok
Open on Open VSX
Recommended · VS Code

VS Code Marketplace

Search Extensions for:

LorapokLabs.cursor-curse-monitor-by-lorapok
Open on VS Code Marketplace

GitHub Release VSIX

Download — from the latest release, then run:

cursor --install-extension …
Download VSIX
Browser · Firefox

Firefox Add-ons (AMO)

Install from Mozilla Add-ons — auto-published on each release.

Install on Firefox →
Browser · Chrome

Chrome (direct download)

Not distributed via Chrome Web Store. Download zip, extract, then chrome://extensions → Load unpacked.

Download Chrome zip

Offline / sideload

Install the browser extension without a store

Use these steps when AMO review is pending, Chrome Web Store is unavailable, or you need an air-gapped install from the GitHub Release assets.

Firefox · offline

Load from GitHub Release (.xpi)

  1. Download cursor-curse-monitor.xpi from the latest GitHub Release (or use the direct link below).
  2. Open about:debugging#/runtime/this-firefox in Firefox.
  3. Click Load Temporary Add-on… and select the .xpi file.
  4. Pin the toolbar icon — usage syncs after you sign in on cursor.com/dashboard.

Temporary loads reset when Firefox restarts. For a permanent install, use Firefox Add-ons (AMO) once published.

Download Firefox .xpi Install from AMO →
Chrome · offline

Load unpacked from zip

  1. Download the Chrome zip from the latest GitHub Release.
  2. Unzip to a folder (e.g. ~/Extensions/cursor-curse-monitor).
  3. Open chrome://extensions (or Edge → edge://extensions).
  4. Enable Developer mode, then Load unpacked and select the extracted folder.

Chrome does not distribute this build via the Web Store — sideload only. Re-load after each browser update if Chrome disables unpacked extensions.

Download Chrome zip

For maintainers

Release via Production Deployment

Push to main → auto-patch bump → publishes to Open VSX + VS Code Marketplace → creates GitHub Release. Manual major/minor bumps via GitHub Actions workflow dispatch.

1

Push to main → auto patch bump

→
2

CI builds & publishes to both marketplaces

→
3

GitHub Release + website auto-update

Auto (every push) 
git push origin main  # patch bump is automatic
Manual minor release 
GitHub → Actions → Production Deployment → Run workflow → minor
Manual major release 
GitHub → Actions → Production Deployment → Run workflow → major

Site data last synced:

Trust

Your data stays yours

  • Only your login — usage is read from your Cursor auth token on your machine.
  • No shared dashboard — teammates cannot see your usage through this extension.
  • Team context — you see limits for your account session, not other members.
  • Anonymous website stats — the marketing site counts visits and install-link clicks only (no personal data).
  • No extension telemetry — usage stays on your machine; no third-party trackers in the extension.
Read privacy policy

About · Founder

Mohammad Maizied Hasan Majumder

Founder & Principal Engineer at Lorapok Labs · Senior Software Engineer at Shohoz Ltd

GitHub LinkedIn Telegram Portfolio

Open source under GNU GPL v3 · free to use, study, and modify. See Terms.