METAGROK
GROK BOT / why-grok-bot-rows-show-under-cursor-models-usage

Why Grok Bot rows show under Cursor Models usage

why-grok-bot-rows-show-under-cursor-models-usage

On Cursor Included Usage / Spending, rows labeled grok-bot-default, grok-bot-automation, and grok-bot-cua used to appear under Cursor Models and Other Models and look like they ate 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
Computer-use Bot work (grok-bot-cua) 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.

Display fix (Sep 11, 2026)

Staff Colin on forum 170771 #22 (Sep 11, 2026): the Spending-page display bug is fixed. grok-bot-default / grok-bot-automation / grok-bot-cua (and models Grok Bot calls as part of its work) no longer appear in the Cursor Models and Other Models breakdowns.

Metering was separate the whole time — only the breakdown put Bot rows in the wrong lists. Earlier confusion (Bot row % moving while Bot was idle) came from those rows sharing the bar with real Cursor usage. After the fix, refresh Spending; if a Bot row still shows after a day, reply on 170771.

What Bot does to Cursor Models quota

Bot chats, automations, and CUA 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

  • Treating old screenshots (Bot rows under Cursor Models) as proof Bot drained monthly Cursor Models — header % was always Cursor-app usage; Bot weekly is separate.
  • 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.