Cursor is the workshop. Grok Bot is the named staff. SuperGrok Heavy’s four-at-once trick is a smarter one-reply, not twelve teammates with photos.
This is the desk SOP for what Grok Bot actually added. The money map sits next door at four lunch tickets. The job shape — skill, schedule, QA, working files — still lives at persistent agents. Grok Bot’s names for those two rungs are skill (how) and routine (when). Same ladder as Claude scheduled tasks and Cursor Automations: skill is how, routine is when. If you already live in Cursor and never open grok.com, you are not missing the Grok model. You are skipping the chat booth. Keep skipping it.
Three different Groks (do not stack them)
People say “Grok” and mean four products. Only one of them is Grok Bot.
| Thing | What it is | How old |
|---|---|---|
| grok.com chat | One Grok you type at. SuperGrok / SuperGrok Heavy is the lunch ticket. Custom Agents were the old named personas (a few slots, a short prompt). That is a chatbot with costumes. | Years. Not Grok Bot. |
| Heavy “four agents” | One reply, several reasoning traces racing, then one answer. It can feel like a mixture of experts. You still talk to one Grok. Nobody has a photo. Nobody keeps a job overnight. Cursor can also spawn sub-agents inside one coding session. Same family of trick: extra brains for this answer, not a roster. | Grok 4 Heavy era. Not Grok Bot. |
| Cursor + Grok 4.6 | The workshop / harness. Files on your disk, git, fleet, skill markdown, effort picker, other models if you mean to spend them. This is the Codex cousin. Building lives here. | The harness you already use. |
| Grok Bot | Named teammates with avatars. You message them like staff. They share one always-on cloud computer (browser, filesystem, terminal). They can sign into apps, talk to each other, and keep going when your laptop is closed. Official cap: 50 Bots + group chats combined. | Announced 11 Aug 2026. This is the new product. |
You are looking at this the right way
If Cursor and Grok Bot can both read email, use tools, and drive a browser, why does Grok Bot exist? Because the staffing model is new. The Grok brain is not.
Cursor is where you build: repos, WordPress, the content factory, skill files, the overnight queue. It is Codex with a Grok (or Claude, or GPT) brain dropped into a harness you own. You were right not to go to grok.com for that. A chatbot is not a harness.
Grok Bot is where you staff: a roster of named people (Avery-shaped, ops-shaped, inbox-shaped) who keep a job, a photo, a thread, and a computer when you are not in the room. Cursor can feel like that for one long Agent session. Grok Bot is built to feel like that for twelve people at once, from your phone, after you close the laptop.
A Cursor sub-agent and a Heavy four-trace reply are extra arms for this turn. A Grok Bot teammate is extra staff for the role.
That split is not theory on this Mac. I have twelve named Grok Bot desks under one coordinator (public roster: how I use Grok Bot). IT Support already did real work: the theninetriangles.com login reset on 16 Aug, from the shared computer, while the public site stayed up. I wrote what the sidebar icons mean because I kept treating the colored shapes as a department code. They are faces. The skill is the method. The routine is the clock.
18 Aug, early afternoon, cursor.com/dashboard/spending on this Ultra seat: Cursor Models 11%, Other Models 0%, Grok Bot weekly 100% (resets 19 Aug), on-demand $358.49 / $380. The 7:00am Cursor email said Other Models were at 100% and I should switch to Grok 4.6. This editor already is Grok 4.6. The 100% bar is Grok Bot. That is why the glossary exists, and why we did not turn on new routines today. Receipts: /skills-and-routines/.
What is truly incremental (and what is not)
| Grok Bot added this | You already had this in Cursor |
|---|---|
| Named persistent teammates with a job, avatar, and memory that is supposed to compound across days. Cap: 50 Bots + group chats. | A strong Agent session, rules, and skills. Persistence lives in your files, which is actually the better source of truth. |
| One shared cloud computer for every Bot: browser, filesystem, terminal, logins. Work can finish in the real app, including sites with no API. Laptop closed is not a stop. | Tools on this Mac, MCP, browser, git. Cursor Cloud Agents exist, but they are still a coding harness, not a twelve-person office. |
| Bot-to-bot routing. They can DM each other or sit in a group chat so you are not the paste-middleman. | You (or one parent agent) still dispatch the sub-agents. Fine for a build. Tiring as a company org chart. |
| Skill, then routine. Teach a task (when available) records a skill draft — visible computer steps, up to ten minutes, no microphone. A routine is separate: one Bot, a schedule or a narrow event, Test run first. Official: skills and routines. Map: /skills-and-routines/. | You write the skill markdown, then a Cursor Automation or a Cowork scheduled task. Slower to start. Survives a vendor. Same two rungs. |
| Message like iMessage from desktop or phone, pick up the same person later. | Cursor is the IDE. You open a project. That is the point. |
Where the work should live
| Work | Put it here | Why |
|---|---|---|
| Code, fleet, articles on disk, skill files, overnight queue, git | Cursor (Grok 4.6 on Cursor Models) | The files are the company. Codex-shaped work belongs in a repo harness. |
| Named always-on roles: inbox, CRM, “watch this thread,” websites with no API, phone handoff | Grok Bot | That is the product: a roster on a computer that keeps running. |
| Honest score, real voice, a call that can hurt someone | Thin Claude slice | Still the judgment cafeteria. Keep it short. |
| Article 17 of 45 overnight | Local writer on the Mac | No vendor ticket. |
| Just chatting with Grok | Skip grok.com | You already said you need the harness. Believe yourself. |
Skills and routines (do not glue them)
xAI published the same order we already taught for Claude: do the job once, save the method as a skill, only then automate. A Grok Bot skill is reusable how (Settings → Plugins, type /, enable per Bot). A routine is when one Bot runs it. Cap 50 routines per Bot. Background routines can run with the laptop closed. A test run is real work. Teach-a-task is not a clock.
Claude still says scheduled task. Cursor still says Automation. The glossary and the three paste blocks live at /skills-and-routines/. Do not invent a fourth language, and do not put production jobs on grok.com Build’s 7-day /loop.
Put the canon in markdown (skills, Dennis OS, the vault). Do not let twelve Bot profile bios become the only copy of how we work. A Bot can run a skill. The skill still lives in a file the next vendor can read. That is one shared brain.
The lunch ticket (so you do not pay twice)
Grok Bot is not a fifth cafeteria with its own $300 door. Official access, 18 Aug 2026:
- Cursor Ultra ($200/mo) includes Grok Bot. If you already pay Ultra, you are in. Pro and Pro+ do not include it.
- Cursor Teams Premium ($120/seat) includes it. Standard seats do not.
- SuperGrok Heavy ($300/mo) includes it. Linking Heavy can create Cursor Ultra at $0 while Heavy stays active. The usage bars still do not mix: Cursor Models ≠ Grok Bot weekly ≠ grok.com Extra Credits.
- Already on Ultra: linking Heavy does not add extra Ultra. You already have Grok Bot.
If you never open grok.com, the cheap individual path is Cursor Ultra, not SuperGrok Heavy. Pay Heavy when you want grok.com’s top weekly buffet, or when you already have Heavy and should link instead of also paying $200. Paying Heavy and Ultra without linking is two bills for one workshop.
What the extra $100 buys (Heavy vs Ultra)
You were right: $300 SuperGrok Heavy can include Cursor Ultra and Grok Bot if you link it. The extra $100 versus paying Ultra $200 is not a bigger Cursor, and it is not a bigger named-Bot product. It is grok.com’s top cafeteria.
| Pay this | You get | You do not get |
|---|---|---|
| $200 Cursor Ultra | The workshop (Grok 4.6 on Cursor Models, $400 Other Models). Grok Bot. Effort picker including xhigh. Cloud Agents. This is what the team needs to build and to staff named Bots. | grok.com Heavy: the largest Chat / Imagine / Voice / Build weekly pool, 1080p Imagine video, peak-time priority, early grok.com features, and the hard-problem / multi-hypothesis mode xAI launched as Grok 4 Heavy. |
| $300 SuperGrok Heavy (link for Ultra at $0) | Everything in Ultra + Grok Bot, plus grok.com’s top buffet. Official Heavy copy: highest usage at the fastest speed, solve extremely hard problems, most powerful intelligence, dedicated support and early access. | A second Ultra. Linking does not stack extra Cursor. Grok Bot still has no model picker — paying Heavy does not make your named Bots run the four-agent ensemble. |
The “teams of four agents” you remembered is Grok 4 Heavy on grok.com (July 2025): several reasoning traces racing, then one answer. That lives in the grok.com chat booth. Cursor Grok 4.6 xhigh is more thinking time in the workshop. Grok Bot named teammates are a roster. Three different knobs. The $100 buys the grok.com knob.
What the team should pay: if they only want Cursor + Grok Bot, they pay $200 Ultra (or a $120 Teams Premium seat). They should not buy Heavy. Team accounts cannot use the Heavy-unlocks-Ultra personal promo anyway. Keep Heavy only if someone actually uses grok.com Imagine / Voice / Build / the hard-problem mode enough to care about that buffet.
Cursor does not publish that Heavy gives a larger Grok Bot weekly allowance than Ultra. Do not buy Heavy hoping for “more Grok Bot.” Watch the Grok Bot meter either way.
Grok Bot usage resets weekly (Cursor help). That weekly Bot meter is still not the teal Cursor Models bar. A $300 extra-credit day is the grocery box after a buffet, same as usage-buckets already said — just do not call grok.com chat “Grok Bot” when you mean the new roster.
Where this sits
A skill is a document. An agent is a role. A job is a schedule. Grok Bot calls those last two a named Bot and a routine. Cursor is the workshop that still owns the files.
The System · Skill vs agent · Persistent agents · Skills and routines · Four lunch tickets · Overnight worker
THE DELIVERABLE
Use Cursor to build. Use Grok Bot to staff. Do not buy a smarter one-reply and call it a team.
Lunch tickets Persistent agentsStanding SOP, 18 Aug 2026. Sources: Introducing Grok Bot (11 Aug 2026), Grok Bot overview, skills and routines, create and manage Bots (50 cap), Grok Bot has no model picker, Cursor Grok Bot plans, Heavy unlocks Ultra, x.ai/pricing, x.ai/bot, Grok 4 Heavy (9 Jul 2025). Glossary: skills and routines. Receipt: how we mapped the usage buckets.

