Grok Bot is an AI teammate that works on a persistent cloud computer. It can use a browser, files, a terminal and connected tools. A Bot has a role and conversation that can develop over time; it is not simply a new name for a Grok API request or a reply from an X account.
Start at the official Grok Bot product page and its getting-started documentation. This guide was checked October 24, 2026. It follows public documentation; we did not buy a plan, sign in, create a Bot, connect an account or run a task.
Check access and downloads before subscribing
The current getting-started guide says Grok Bot uses a Cursor account. It lists eligible paid individual Cursor plans and Cursor Teams, linked individual SuperGrok subscriptions, and self-serve Grok Business seats. It also says that Legacy Privacy Mode is incompatible with the cloud storage Grok Bot requires.
The product page separately displays Premium at $30/month, Super at $100/month and Ultra at $200/month, billed monthly. It describes included weekly usage and additional usage billed by token cost. These are public page labels and prices, not a checkout we tested. Do not assume an identically named X or other subscription automatically grants the same access. Check the account's access screen and linked subscription before purchasing.
The setup guide documents desktop downloads for macOS, Windows and Linux, with architecture-specific choices. Follow the download links from the official page rather than a similarly named third-party site. We have not checked an installer, final regional price, taxes or your account's eligibility. Download availability does not establish subscription access.
Sign in and create a focused Bot
The documented desktop flow is to choose Sign in, finish browser authentication and return to the app. It may ask you to link an eligible Grok subscription. Follow your organization's SSO flow if applicable. Onboarding prepares the cloud computer and opens a first Bot conversation.
For another focused Bot, the Create and manage Bots guide gives this route:
- Choose New chat using the sidebar plus button, or
Cmd/Ctrl+N. - Select Create new Bot, or type a name and choose the create-Bot option.
- Give the new Bot its job, sources and approval boundaries in the first message.
- Ask it to remember durable instructions, then give it a task with a clear finish line.
- Use the Bot's name at the top of the chat to open its details when renaming it.
Those are documented steps, not screenshots from our own account. Prefer one useful role over a large roster with overlapping responsibilities. A document-review Bot and a purchasing Bot have different purposes and should not receive a vague instruction to “handle everything.”
Give the first task a result you can inspect
For a first trial, choose a non-sensitive document that needs no external account. An illustrative request is:
Read the attached project note. List its decisions and open questions with section references. Do not edit the source, send messages or create a routine. Return a draft for review.
This is an example prompt, not a task we executed. Check the answer against the attachment: did it identify the actual decisions, preserve uncertainty and point to the right sections? A plausible summary alone does not demonstrate that every source was read correctly.
The official Grok Bot 101 guide describes chat, scheduled or event-driven routines, and messages from other Bots as ways work can start. Begin with a direct request. Save recurring behavior only after the input, expected output and review point are clear.
Bots on one account share the computer
The computer-and-apps documentation describes one cloud computer per user. Bots share its files, browser sessions, logins and command-line credentials. Their separate roles or screens do not make them separate credential boundaries.
For example, signing into a website while working with one Bot can make that session available to other Bots on your account. Use only accounts and files appropriate for that shared environment. The fact that the computer is remote does not establish that every Bot has narrower access than you do.
Deleting a Bot is also different from removing shared-computer data. The management guide says deletion removes its active profile, conversation and routines, while shared files and sign-ins may remain. Hiding it does not pause its routines. Review the relevant account and routine controls rather than treating sidebar organization as access revocation.
Set approval rules before consequential actions
The approvals and privacy guide documents Auto Review, configured under Settings → General → Auto-review. It describes Ask first and Allow automatically rules, with Ask first taking precedence when both match. Team-enforced rules may be locked.
Keep rules specific to an action and scope. For example, ask for approval before external messages, purchases, publication or changes to a production system. Review the target and values on the actual proposed action, rather than allowing all future browser activity.
The guide explicitly describes Auto Review as model-based. It complements permissions and limited access; it is not proof that every unintended action will be blocked. A remembered instruction alone should not be treated as an enforced permission boundary.
For passwords, one-time codes and other sensitive login steps, use the documented takeover or supported secure-request flow, not ordinary chat. We did not test secret masking, approvals or account privacy controls.
Cloud work and local-computer access differ
The same approvals guide distinguishes the shared cloud computer from optional execution on your own Mac or Windows desktop. Local execution has its own setting under the computer controls. Leaving local access unavailable does not stop a Bot from using its cloud computer.
Enable local access only when the task actually needs it and the scope is acceptable. This guide does not require local execution, connector installation or any account credentials for its sample document task.
Troubleshoot the stage that failed
The official troubleshooting guide separates access, computer setup, authentication, connectors and running work:
| Symptom | First useful check |
|---|---|
| Sign-in appears complete but access is missing | Confirm the intended Cursor account, organization login and eligible linked plan |
| Computer setup is still progressing | Allow setup or an image update to finish before interpreting it as failure |
| A Bot appears stuck | Look for an approval, question, login handoff or usage limit in its conversation |
| A website keeps requesting login | Take over, finish the site's own verification and confirm the signed-in page before returning control |
| A connector is present but cannot act | Check its authentication and any administrator-provided configuration |
| A routine does not run | Check its enabled state, schedule, time zone, account access and recent failure history |
Avoid resetting the computer as an initial fix. The documentation distinguishes recovery/update from reset and warns that reset can lose recent unsynced work. A disconnected app also does not necessarily mean cloud work stopped.
This article does not reproduce authenticated UI, regional enrollment, weekly usage limits, successful automation or data-retention behavior. Public instructions are enough to explain the setup route and its boundaries; actual account access and task completion remain separate checks.