Why Grok Bot rows show under Cursor Models usage

On Cursor Included Usage, rows labeled grok-bot-default and grok-bot-automation can appear under Cursor Models and look like they eat the monthly Composer / Cursor Grok quota. Staff: they do not count against that monthly Cursor Models pool. Thread: forum 171226 (deanrie, Sep 10, 2026). Official Bot metering: Plans and billing.

What is metered where

Activity	Meter
Grok Bot chats (grok-bot-default)	Grok Bot weekly allowance on the Cursor account
Grok Bot automations / routines (grok-bot-automation)	Same Grok Bot weekly allowance
Cursor cloud agents the Bot launches for you	Cursor plan (like any other cloud agent)

Grok Bot usage is metered on the Cursor account. A SuperGrok or X Premium+ link grants Bot weekly on that account; it does not create a second Bot meter on grok.com / X.

Why the UI looks wrong

The per-model breakdown under Cursor Models is not filtering out Grok Bot rows yet (display bug staff are tracking). On the Pro example in that thread:

• Header 23.1% was the real Cursor-app usage.
• Bot rows under it were labelled in the wrong list and inflated how “full” Cursor Models looked in the row list.
• After the filter ships, those rows leave the list and the remaining Cursor model percentages renormalize up to the same header (header stays).

Nothing on the account needs a support fix for the display alone.

What Bot does to Cursor Models quota

Bot chats and automations do not reduce remaining Composer or Cursor Grok model quota. The documented exception is cloud coding agents Grok Bot runs for you — those draw Cursor plan usage like any other cloud agent.

For stretching Bot weekly itself: Pace Grok Bot weekly allowance on Ultra (and Heavy).

Pitfalls

• Read the header percentage for Cursor Models, not the misleading Bot rows under it, until the filter ships.
• Ultra / Heavy Bot weekly and Cursor Models monthly are separate pools.
• On-Demand after Bot weekly hits 100% is separate again: Control Grok Bot On-Demand after weekly usage.