Grok Bot routine create refused: "Automations are not available with your plan" (Start + SuperGrok)

Support Help
,
1

Where does the bug appear (feature/product)?

Grok Bot

Describe the Bug

Hi Dean, as you asked, this is a separate topic for the routine-create issue from thread 171895: Grok Bot update_state memory writes fail fleet-wide: brain docs snapshot was cut short before completing - #18 by deanrie

On 13 Oct 2026 at about 7:28 PM IST, I tried to create a routine from my Grok Bot (a disabled cron test, nothing else). The server refused it with:

Not saved: the server refused this routine (create refused): Automations are not available with your plan.

My account is on the Cursor Start plan (₹649/mo), and I also have SuperGrok. Grok Bot usage shows as a separate SuperGrok meter on my Spending page. Earlier creates in late September failed with no reason given. This is the first time it has named the plan.

Two questions:

  1. Do Grok Bot routines need Cursor Pro, or should SuperGrok (or Start) cover them?
  2. If they’re meant to be included, could the plan check be the bug?

I can get a Request ID from desktop if you need one. Thanks!

Steps to Reproduce

  1. In Grok Bot, ask the bot to create any routine (I tested a disabled cron routine).
  2. The server refuses it: “Not saved: the server refused this routine (create refused): Automations are not available with your plan.”

Expected Behavior

The routine saves, or the plan page states which plan includes Grok Bot routines.

Operating System

MacOS

Version Information

Grok Bot 0.70.2 (Stable track, macOS app)

Does this stop you from using Cursor

No - Cursor works, but with this issue

6

Hey @Amogh_Tyagi, thanks for splitting this out.

To answer your questions: routines currently check your Cursor plan, and the Start plan doesn’t include Automations (scheduled and triggered runs). Your SuperGrok link gives you access to Grok Bot itself, but it isn’t counted for routines, so the server refuses the save. That’s what the new message is telling you.

The failures you saw in late September were very likely the same refusal. The app just didn’t show the reason back then.

We agree this is confusing when Grok Bot itself works on your account, and the plan pages don’t spell it out. I’ve added your report to the issue we’re tracking for this and passed on the docs feedback.

8

Thanks Colin, that clears it up. Good to know the September failures were the same refusal. One follow-up: is there any plan to let SuperGrok cover Grok Bot routines, or at least show “requires Pro” in the app before a create is attempted? Happy to close this otherwise.