What is Grok Bot?
Grok Bot is an AI teammate product built around persistent Bots: named assistants with a role, work context, and access to tools. You message a Bot with a task and relevant context. It can then work across apps and websites, keep you updated, and return for approval when an action needs it.
Grok Bot is separate from the Grok chat app. xAI introduced it on August 11, 2026. xAI had previously announced on February 2, 2026, that it was joining SpaceX; current product documentation identifies the company as SpaceX Super Intelligence LLC, or SpaceXSI. So “Grok Bot from xAI” is a familiar shorthand, while SpaceXSI is the company name used in current product materials.
What does Grok Bot do?
Grok Bot is intended for work that involves more than answering a question. Its Bots can use connected applications where available and computer interaction for other browser-based tasks. They can also coordinate with other Bots, keep role context between sessions, and save demonstrated workflows as skills or routines.
The company’s launch examples include sales research, administrative tasks, and an engineering Bot reproducing a product bug and handing a proposed fix to a debugging Bot. These examples show the product’s intended range; they do not guarantee a particular task will succeed in another team’s environment.
For software work, Grok Bot can use a browser, a filesystem, and a terminal on its hosted computer. It can access a code repository through an enabled connector or a permitted command-line workflow, then inspect or change files and run commands within the permissions you have configured. For a wider overview of agentic QA for mobile apps and AI QA testing tools, see the related clip.qa guides.
How does Grok Bot work?
Each Bot has its own conversation and role, but Bots on one account share the same persistent cloud computer. That computer keeps files, browser sessions, and command-line credentials available across the account’s Bot roster. Work can continue in the cloud when you close the app or your laptop.
Bots use connected apps when a suitable connector exists. Grok Bot also documents adding a custom MCP server by URL or by a command that runs on its computer. When the server is remote, the Bot can discover and use the tools it exposes, subject to the server’s authentication and the access you grant.
Grok Bot is expected to work with clip.qa’s remote MCP server, but that specific integration is not confirmed by the cited product documentation. Verify authentication and report retrieval before relying on it. clip.qa’s Chrome extension can capture browser console and network details; mobile reports can include device telemetry. The agent’s repository access and terminal permissions are separate. For a walkthrough, read how to fix bugs with Grok Bot and clip.qa.
How is Grok Bot different from other AI agents?
The useful comparison is the kind of work environment each agent has, rather than a single score. Grok Bot emphasizes persistent, cross-app work on a hosted computer. A coding-focused terminal agent emphasizes a repository and command-line loop. An MCP-enabled chat assistant can call connected tools, but editing a repository and running its tests depend on the assistant’s own workspace and command features.
| Agent type | Typical work surface | Useful when |
|---|---|---|
| Grok Bot | Persistent cloud computer, connected apps, browser, filesystem, terminal | A task spans tools or needs to continue in the background |
| Coding agent such as Grok Build | Coding-oriented terminal and repository workflow | The task is centered on inspecting, editing, and testing code |
| MCP-enabled chat assistant | Conversation plus the tools exposed by MCP servers | You want to retrieve or update information through connected services |
Grok Build is a separate SpaceXSI coding agent. Its official description focuses on a terminal interface, code tools, and the option to run locally with a configured inference service. Grok Bot is broader: it provides a persistent computer and connected applications for longer-running work. Teams may use both, depending on whether they need a general-purpose teammate or a coding-centered loop.
The same distinction applies to bug reporting. clip.qa creates the report and evidence; an agent uses that evidence to investigate code. See the AI code QA use case for how that handoff fits into a QA workflow.
How much does Grok Bot cost, and where can you use it?
Grok Bot is included with Premium, Super, and Ultra on the current X Subscription. The Free and Plus plans do not include it. The listed monthly prices are $30 for Premium, $100 for Super, and $200 for Ultra; tax may be added, and prices can change.
Grok Bot draws from the subscription’s shared weekly usage pool. The higher tiers include larger pools, and additional usage credits can cover work beyond the included allowance. Legacy Cursor, SuperGrok, and X Premium plans continue for existing customers, with eligibility depending on the account and plan.
The current documentation lists Grok Bot apps for macOS, Windows, Linux, iOS, and Android. The app surfaces sync Bots and conversations. Enterprise access and administrator controls vary by plan and account setup, so check the current official pricing page and Grok Bot FAQ before choosing a plan.
What are Grok Bot’s limits?
Grok Bot’s main trade-off is that its work environment is hosted and shared across Bots on the same account. A file, sign-in, or command-line credential on that computer can be available to the other Bots in that roster. Separate Bots are not separate security boundaries.
The product requires cloud data storage and does not support Cursor’s Legacy Privacy Mode. Privacy and training choices follow the applicable Cursor account settings. Review those terms before connecting sensitive repositories or data.
The cloud computer can also encounter ordinary web limits: a site may require a fresh login, block cloud traffic, present a CAPTCHA, or require a human approval. A Bot may hand the task back to you at that point. Usage limits can also constrain how much background work fits within a plan’s shared weekly allowance.
Grok Bot does not remove the need to review code changes. Give it scoped repository access, ask it to explain its evidence, and require it to report the commands and tests it ran. For a workflow that starts with a recorded bug, clip.qa’s AI bug report guide explains the report side of that process.
To try the recording-based report workflow, Sign up free.
Sources
- Grok Bot overview — product definition, supported platforms, and core capabilities. Date checked: 2026-11-05.
- Introducing Grok Bot — launch description, original beta announcement, and company examples. Date checked: 2026-11-05.
- xAI joins SpaceX — xAI’s announcement about joining SpaceX. Date checked: 2026-11-05.
- Grok Bot computer and apps — hosted computer, shared account context, connected apps, and adding MCP servers by URL or command. Date checked: 2026-11-05.
- Grok Bot FAQ — app distinction, platform access, usage model, and account eligibility. Date checked: 2026-11-05.
- X Subscription pricing — current monthly plan prices and the tiers that include Grok Bot. Date checked: 2026-11-05.
- X Subscription pricing documentation — current plan inclusions and shared weekly usage pool. Date checked: 2026-11-05.
- Grok Bot approvals, security, and privacy — cloud data storage, shared-computer boundary, and privacy controls. Date checked: 2026-11-05.
- Grok Build is now open source — how Grok Build differs as a coding-focused terminal agent. Date checked: 2026-11-05.