Skip to content
RRanked By Task

Guides

The Ultimate Grok Bot Guide

Last updated

Some tool links may earn us a commission, at no cost to you. Rankings are never paid for or changed by that. Disclosure.

Grok Bot is Cursor's app for AI teammates that keep a job. Each Bot is a named teammate with context that compounds, on a persistent cloud computer with a browser, a filesystem, and a terminal. You message it. It works across apps and websites, updates you in the chat, and stops for approval. The desktop app runs on macOS (Apple silicon and Intel), Windows (x64 and Arm64), and Linux (x64 and Arm64). The mobile app runs on iPhone. The computers run in Cursor's cloud.

Access is included with every paid individual Cursor plan and with Cursor Teams. You can also link SuperGrok, SuperGrok Plus, or SuperGrok Heavy, or sign in with a self-serve Grok Business seat. Usage resets weekly. This page does not print a dollar price. Cursor sends that matrix to its Plans and billing page. Grok Bot is not on Best for Vibe Coding. Cursor, the editor, is first there.

A Bot, and the computer it shares

Create a Bot when the work has its own goal, tools, approval boundary, or schedule. Cursor's work guide prefers a named job, such as a weekly account-health review, over a general helper. Choose New chat (the + button) or press Cmd+N, then Create new Bot. In the first message, state the job, the sources, and where it must stop, and ask it to remember that. Then give it a real task with a finish line.

Every Bot on your account uses the same cloud computer. Files, browser sessions, and app logins are shared, so a handoff does not need a second setup. The computer belongs to the account. Anything on it is available to every Bot you run. Between users, isolation is strict: each person's computer is dedicated and hardware-isolated. Each Bot gets its own screen, and one computer-use task runs on that screen at a time. Closing the laptop does not stop a background turn or a routine.

Open the computer preview to watch clicks and typing. The Bot hands you the computer for passwords, passkeys, two-factor codes, CAPTCHAs, and payment or identity checks. It does not type those credentials. A connected app is more reliable than clicking a site. OAuth tokens stay on Cursor's connector backend, and the Bot calls the tool without receiving the token. A team can show an app as "Disabled by team admin." That does not block the website. Blocking the site takes Network Controls, which Cursor says is Enterprise only.

Connectors, the inbox, and routines

Gmail, Notion, Slack, and other apps belong to the account you signed in with. Add one from Connect apps, an in-chat card, or, on the phone, your avatar, then finish the provider login. Every Bot on that account can use it. A teammate's Team Bot asks first. Gmail is one mailbox at a time. Calendar can read what you can see and edit events you can already edit. It cannot change Google Meet host controls or add a Zoom link through Google's add-on. Slack posts as the connected user, only where that user can post.

The Email app is separate. It claims one address at mail.grokbot.com instead of connecting Gmail. Ask the Bot, or create the address in the Email app. Nothing is claimed until you approve. You get one address. You cannot rename or delete it, and Cursor says a claimed name is never issued again. On a Cursor team, agent email stays off until an admin turns on Agent Email. There is no inbox screen. Ask the Bot what arrived.

New mail does not wake a Bot. It acts on mail only through a routine. The routine can read, summarize, and draft. Every send waits as a draft until you press Send, including routine replies. Text inside an email is not permission to send. A routine can watch anyone, specific addresses, or a domain such as *@example.com. By default it runs only when the sender passes standard authentication. It cannot filter on subject.

A routine is when one Bot runs: a schedule, or an event from Slack, GitHub, Linear, Sentry, PagerDuty, email, or a webhook. Schedules use the time zone under Settings, then Bot. A new routine waits for the next time. It does not fire when you create it. On desktop, open the Bot's name, then Details, then Routines, to pause, test, edit, or delete. Test does real work and can change files. A skill is the reusable instructions. Cursor's order is a one-time task, then a method you trust, then a skill, then a routine. Keep sending, purchasing, deleting, publishing, and production changes behind approval.

Teammates, and where this site stops

Bots can run in parallel, message each other, share a group of two to six, and pass a task. A public link copies identity, description, skills, and routines to another account. It does not copy your computer, logins, or history. A Team Bot is one shared Bot the team chats with.

Memory keeps preferences, role context, and summaries. For a stale-prone decision, ask the Bot to reopen the live source. This site does not rank Grok Bot beside Claude Code or GitHub Copilot. See Cursor alternatives. Cursor cloud canvases is a different surface.

Sources

Questions people ask

Does Grok Bot keep working when the laptop is closed?
Yes. Cursor's docs say work runs on the cloud computer. Closing the app, the laptop, or the phone does not stop a background turn or a routine.
Can a Bot send email by itself?
No. Cursor's email help says every outbound message waits as a draft until you press Send. That includes routines. A request inside an email the Bot received is not permission to send.
Is Grok Bot on the vibe-coding ranking?
No. This site ranks Cursor the editor first for vibe coding. Grok Bot is a separate Cursor app and is not a row on that list.
How much does Grok Bot cost?
Cursor's docs say access is included with every paid individual Cursor plan and with Cursor Teams. You can also link SuperGrok, SuperGrok Plus, or SuperGrok Heavy, or use a self-serve Grok Business seat. Usage resets weekly. This page does not print a dollar price. Check Cursor's Plans and billing page.