Grok Bot lessons: setup, routines, approvals, costs, mistakes

Get access

Grok Bot is on Cursor's Premium ($30/mo), Super ($100/mo), Ultra ($200/mo) and Teams plans, not Free or Plus (cursor.com/pricing, Oct 28 2026).

Connect apps one at a time

Gmail, Calendar, Drive, X, Vercel etc. Test each with a read-only task before letting it act.

Write standing rules

Paste the agent rules from Scripts: approvals before sending/posting/buying, disclose new scheduled jobs, proof with every "done".

Good at

• Multi-step jobs across your apps: research, build and deploy a site, draft and send email after approval
• Running routines on a schedule
• Working on its own Linux box with files and a browser

Careful with

• Status reports can be wrong; ask for the link or ID
• Routines use credits on every run and can silently stop after a reset; audit weekly
• It can be slow on long multi-step jobs; give the whole spec up front

What burns usage

Long agent runs, browser work, subagents, and scheduled routines. Usage comes from a weekly pool shared with Cursor; top-offs available.

No refunds for mistakes

Usage spent on a wrong or failed run is spent. Prevent it: specs first, stop loops after two failures.

Changing scope mid-job

Every change restarts work and costs usage. Decide the spec, then send it once.

Accepting "done"

Open the URL or screenshot it gives you.

Forgotten routines

Ask for a routine list weekly.

Build request

Bad: "make me a website"

Good: "Build a 5-page static site for my concrete company: Home, Services, Gallery, Quote form (emails me), Contact. Use my logo from Drive. Show me a preview link before publishing."

Why: pages, sources, and an approval point.

Routines are jobs that run on a schedule or when a trigger arrives, like an email. Each run uses credits.

Real record: one user's alert routine had been off since about Oct 25–26, 2026, and it was only found on Oct 28. A box reset had turned it back off. Do this: ask for a list of every routine every week, and require it to tell you before it adds a new one.

Connectors link the bot to apps like Gmail, Calendar, X, Vercel and Google Drive. Each one is another place the bot can act for you.

Do this: connect one at a time, test it with a small task, and remove the ones you don't use.

Posting, emailing, buying and deleting should need your OK. Approvals from other bots don't count.

Real record (Oct 28, 2026): during a flash flood warning, the bot asked which posting method to use instead of just getting the post out. The warning was posted by hand 33 minutes after it was queued. Do this: set standing rules ahead of time for urgent jobs.

The box is a Linux computer that all your agents share. Files and logins stay on it.

Real record (Oct 28, 2026): the platform restored a snapshot at about 11:31 AM PT, rewriting around 7,800 files, and the box rebooted at 2:52 PM PT. Installed packages were wiped and a setting that kept the alerts off was reset. Do this: after any reset, ask it to check that every job is actually running.

You can call the bot and give it orders by voice. Keep orders short, and ask it to repeat back what it will do.

Real record (Oct 28, 2026): on a call, the bot read back the exact queued caption and link. That made it easy to check before posting. Do this: ask for the exact text before anything goes public.

Cursor's official pricing page lists Grok Bot on the Premium ($30/month), Super ($100/month) and Ultra ($200/month) plans, and on Teams. It isn't on Free or Plus. Usage comes from a weekly pool shared across Cursor and Grok. When you run out, you can buy top-offs or wait for the weekly refresh. Source: cursor.com/pricing, checked Oct 28, 2026.

Real record: on Oct 28, 2026, one Ultra user had used 100% of the weekly limit, and it resets Thursday at 1:06 PM PT. Credits spent on mistakes are not refunded.