When Cursor Start blocks Grok Bot routines

Scheduled and event routines live under each Bot’s conversation details. Official skill/routine docs: Skills and routines. Linking SuperGrok or X Premium+ grants Bot usage without changing your Cursor plan — Plans and billing.

The Start exception

Staff on forum 171173 (Colin, Sep 9, 2026): if Bot access comes from a linked SuperGrok / X Premium+ grant while the Cursor subscription is Start, routines are the one Bot feature that still checks the Cursor plan. Start does not include them, so the server refuses to schedule runs. Resetting the Bot or the Agent Computer does not fix it.

Chat, skills, connectors, and other Bot work can keep working on the linked grant. Only the schedule / event sync is refused.

Confirm this is your case

1. Bot plan screen shows access from a linked SuperGrok, SuperGrok Plus, SuperGrok Heavy, or X Premium+ account.
2. Cursor account is on Start (or another plan that does not include Bot routines).
3. Routines stay silent across Windows, Mac, and iOS after resets.
4. Routine checklist items in Fix a Grok Bot routine that did not run already look correct (enabled, time zone, owning Bot, plugins).

Fix

1. Upgrade the Cursor plan to Pro or higher on the same account that owns Grok Bot.
2. Leave the SuperGrok / X Premium+ link alone unless you intend to change billing elsewhere.
3. Open the Bot → View conversation details → Routines and confirm schedules show a next run.
4. Use Test run with safe inputs after the plan syncs.

Staff said routines should start syncing with no other Bot changes once Cursor is Pro+.

Pitfalls

• Buying X Premium+ or SuperGrok for “Grok Bot included” does not unlock routines while Cursor stays on Start.
• Hiding a Bot from the sidebar does not pause routines; Start refusal is a server-side schedule block.
• On-Demand and weekly Bot meters are separate topics — Control Grok Bot On-Demand after weekly usage.