Third-party tool
Grok Bot usage menu bar
What job it does
Show Grok Bot weekly usage in the macOS menu bar so you notice the pool before it silently spills into On-Demand.
Platforms
macOS menu bar. Numbers are informational; the Cursor plans screen remains the source of truth for billing.
Install
Install from diegocp01/grok_bot_usage_menu_bar per its README. Grant only the permissions the app documents. Cross-check readings against Cursor → Grok Bot weekly usage — community meters can lag or mis-map pools (Pro Other Models vs Bot weekly pool).
How it differs from the official app
This is a meter, not a Bot client. It does not send messages, run routines, or recover computers. Pair it with the cost lesson on this site: On-Demand $0 blocks paid spillover but does not stop promo credits from draining, and there is no in-app warning from Grok Bot itself.
Cross-check the Cursor plans screen
Install the menu bar, then open Cursor → Grok Bot weekly usage (or the plans screen the cost lesson names) and confirm the two numbers move together for a day. Community meters can lag, cache a stale session, or map the wrong pool — Pro Other Models is not the Bot weekly bucket. After a password change or account switch, sign out of the official Mac app, quit it, sign in again, then relaunch the meter. The invoice and the official screen win every argument.
What the number is not
This is a meter, not a client. It does not send messages, run routines, Recover a computer, or block On-Demand. Grok Bot itself may give no in-product warning when the weekly pool empties. Setting On-Demand spend to $0 can block paid overflow; it does not stop promo or trial credits from draining. macOS and iOS share one bucket — a phone-heavy day still moves this number.
When to stop trusting it
If the menu bar says you have room and the official screen says 100%, believe the official screen. If two Cursor accounts are signed in across devices, check you are reading the account that actually runs Grok Bot. Review the upstream permissions before install: some meters read session or usage endpoints. Do not paste a usage token into chat. Pair the meter with the cost lesson; do not invent a dollar forecast from the remaining percent.
Risks
Third-party. Reading usage may require access to account/session data depending on implementation — review the repo before installing. Do not treat its number as a guarantee against charges; official plans screens and invoices win.
License and source
License. As declared in the upstream repository README
Open GitHub source Prefer official install Symptom-based fixes
Third-party tools can touch a local session. They do not replace Require Approval, secrets cards, or Recover/Update in the official desktop app.