Grok BotGuide

Lesson 7

Grok Bot usage, On-Demand, and cost pitfalls

Grok Bot has no separate SKU. You buy Cursor or SuperGrok / X, and Bot appears as a bundled feature with weekly-resetting usage. Numbers and eligibility change; this page covers mechanics and pitfalls. Dated price/eligibility contrast: pricing snapshot.

How usage works (official)

Cursor Help Plans and billing: paid access includes weekly-resetting usage; when it runs out, if the account has on-demand enabled, overage can go to shared on-demand spend. Metering is on the Cursor account, not on Grok or X. Linking SuperGrok / X Premium+ is a usage grant for that same Cursor account — it does not open a second meter on the Grok side and does not change your Cursor plan. Linking is permanent.

Trial is usage credits, not a fixed number of days (plus a 7-day window). Credits debit by agent steps and tokens, not by how many messages you send. A large task can exhaust them at once. Spent trial credits are not restored. macOS and iOS share one bucket.

Staff later corrected several easy-to-spread points (forum; see troubleshooting sources):

  • On Pro, Grok Bot has its own weekly pool, separate from Cursor plan usage; spillover still enters shared On-Demand.
  • Spend order: Grok Bot weekly pool → promo/referral credits → paid On-Demand. No in-app warning.
  • Setting the On-Demand cap to $0 blocks paid spillover but does not stop credits from being drained.
  • Pro’s $20 Other Models allowance is not the Grok Bot weekly pool.
  • Cursor Cloud Agents launched by Grok Bot consume Cursor plan usage; Grok Bot chat is a different allowance.

Eligibility (official pages on 2026-09-20)

Cursor Help and the xAI FAQ now both include every paid individual Cursor plan (including Pro) and Cursor Teams. You can also link personal SuperGrok / Plus / Heavy / X Premium+. Lite and SuperGrok Team/Enterprise still cannot link. Remaining wording still differs on whether Cursor and SuperGrok grants stack. Open the originals on the pricing snapshot; this site does not invent USD figures.

Pitfalls already showing up repeatedly in the community

  • Weekly usage can burn in a day. An xAI engineer has publicly acknowledged that complaint direction. Chatty Chief-of-Staff threads and sorting a decade of inbox are user hypotheses, not our measurements. Mitigations: keep routines in working hours; use connectors instead of pure browsing for heavy work; keep Chief-of-Staff chats short; do not bulk-sort history on day one. KC’s public note that many multi-bot setups go quiet after 10–14 days is a warning to put memory in /workspace, not a number we repeated — see after week one.
  • Auto-review is best-effort. Require Approval outranks Always Allow; do not write wide rules like “allow everything in the browser.” Personal Auto-review rules live on the current desktop and sync to its Grok Bot computer — check again after switching desktops.
  • Bots are not a security boundary. See shared computer.
  • Cloud computers sleep and can auto-update when idle. Dead background processes are not a failure mode by themselves.

Common misconceptions

  • Assuming linking SuperGrok Heavy still bundles Cursor Ultra. Staff announced that promo ended on 2026-08-21; linking is only a usage grant. Older Help pages lagged — third-party pricing surveys cite dated wording; we do not treat them as a price list.
  • Leaving On-Demand uncapped after the weekly pool is gone.
  • Treating skills inside a Bot template as already installed.

Operator checklist (after the first good week)

  • One pinned door. Specialist Bots do not also sit in the same mega-chat.
  • Routines fire in working hours unless the job is truly overnight (Krista Letz’s prospecting pattern — still stop at drafts).
  • On-Demand cap is a number you chose, not the default leftover.
  • Auto-review: Require Approval outranks Always Allow. Re-check after you switch desktops.
  • Cloud Agents launched by a Bot spend the Cursor plan pool, not the Bot weekly pool.

Next: the operator path, then what others shipped — use cases — or not responding if bots go silent while the computer still opens.

Guides