Grok Bot Explained: What It Does, Pricing, and Whether It Is Worth It

Grok Bot is an agent product from SpaceXAI and Cursor that lets people create persistent AI teammates, give them access to a cloud computer, and send them into websites, files, connected tools and recurring workflows. SpaceXAI launched Grok Bot on August 11 and expanded access later in August.

Updated October 1, 2026. Cursor now includes Grok Bot with its US$20/month Pro plan, and SpaceXAI lists Linux, iPad and Android support. Grok 4.7 has also launched. The access, platform and model sections below reflect those changes.

The short version is promising, with an asterisk large enough to deserve its own desk.

Grok Bot is one of the clearest attempts yet to turn autonomous agents into an approachable work product. It can keep running when your laptop is closed, coordinate several named Bots, learn repeatable processes and finish work inside the tools where that work belongs. Paid Cursor access starts at US$20 per month for an individual through Pro, or US$40 per user per month through Teams Standard.

It is also an early beta that may hold browser sessions, files and command-line credentials on one shared cloud computer. Every Bot on an account can access that same environment. Grok Bot should begin with bounded, reviewable work rather than unrestricted control of a business.

Grok Bot at a glance

Prices and access reflect the official Grok Bot plans, Cursor pricing and SpaceXAI platform list checked on October 1, 2026. Grok Bot is changing quickly, so verify the live plan before subscribing.

What is Grok Bot?

Grok Bot is separate from the ordinary Grok chatbot available on grok.com, X and the Grok mobile app.

Regular Grok primarily answers, researches, reasons and creates inside a conversation. Grok Bot is designed to take a task into a working environment and complete the surrounding actions. A Bot can open websites, sign into apps, work with files, use a terminal, call connected tools and continue after the user's device is closed.

SpaceXAI describes each Bot as a persistent, named teammate. A user might create a researcher, an account manager, an operations assistant and a chief of staff, then place them in a group conversation so they can pass work among themselves.

The approachable interface is the main product idea. Instead of building a conventional automation flow before anything useful happens, the user describes a job in a message, supplies the relevant access and reviews the result.

That simplicity does not remove the underlying complexity. Grok Bot is still operating a remote computer, authenticating with outside services, choosing actions and consuming metered AI usage. The friendly names make the system easier to direct. They do not make permissions, cost or failure handling disappear.

Where Grok 4.7 fits

SpaceXAI released Grok 4.7 on September 21 after Grok 4.6. The company says it trained Grok 4.7 to understand the Grok Bot harness and handle longer tasks. Its release does not establish which model every Grok Bot account uses by default.

The relevant buying decision is the Grok Bot system around the model: persistent work, computer access, multi-Bot handoffs, routines, permissions and usage costs. A newer model can improve the worker without resolving the risks created by the workplace.

How Grok Bot works

Each user receives a persistent managed cloud computer with a browser, filesystem and terminal. Connectors and MCP-enabled tools can provide structured access where available, while computer use lets a Bot work through websites and applications without a dedicated integration.

Named Bots retain their role, conversation and preferences. They can also exchange messages, join group conversations and hand off tasks. Several Bots can reason and work in parallel, with each Bot receiving its own screen on the shared computer.

The word "shared" matters.

All Bots belonging to one user operate on the same cloud computer. They can access its shared files, browser sessions, signed-in accounts and command-line credentials. One Bot can continue from work another has saved, which makes collaboration practical. It also means separate Bots cannot be treated as separate security zones. The official architecture documentation states this boundary directly.

Several launch-week reports described each Bot as receiving an isolated computer. The current official documentation is more precise: each user receives one account-level computer, each Bot receives its own screen, and all of that user's Bots share the underlying files, sessions and credentials. This analysis follows the official architecture rather than the conflicting summaries.

The official documentation recommends keeping passwords, two-factor codes, passkeys, CAPTCHAs and payment confirmations out of ordinary chat. For those steps, the user takes control of the cloud computer, completes the sensitive action and hands control back.

What can Grok Bot do?

The current product is broad enough to cover research, operations, sales, marketing, support, recruiting, product work and engineering. The useful distinction is that it can act across several tools rather than producing a draft that stops inside chat.

Work across websites and apps

A Bot can navigate browser-based services, use connected tools, work with files and run terminal commands. This allows it to update a CRM, collect information from several sources, prepare a document, reproduce a software issue or leave completed work in the application where a person expects to find it.

Sites can still block automation, request a fresh login, show a CAPTCHA or require human confirmation. A connector is generally more reliable than visual browser control when both are available.

Run several Bots in parallel

Users can assign different roles to different Bots and allow them to coordinate through direct messages, threads or group conversations. A research Bot can collect material, a writing Bot can turn it into a draft, and a supervising Bot can review the output or request another pass.

This reduces the amount of copying and re-explaining between separate AI chats. It does not guarantee that the Bots will choose the right division of work or catch one another's errors.

Remember roles and working preferences

Named Bots can retain stable preferences, role context and summaries of earlier work. Files, shared browser sessions and explicit handoffs can move additional context between Bots.

Memory is useful for continuity, although it should not become the source of truth for current prices, policies or business decisions. SpaceXAI's own documentation advises asking a Bot to check the current source when accuracy matters.

Turn a successful task into a reusable skill

A skill records how to perform a job, including the inputs, sequence, decision rules, expected output, validation steps and approval boundaries.

Grok Bot can also create a draft skill from a demonstrated browser workflow when the "Teach a task" feature is available. The user performs the process once for up to ten minutes, reviews the generated instructions and tests them on a safe example.

A demonstration captures visible steps. It may miss the judgment, exceptions and failure handling that an experienced person applies without thinking. The generated skill should be treated as a first draft.

Run recurring routines

A routine assigns a workflow to one Bot and tells it when to run. Routines can operate on a schedule while the user's laptop is closed. Supported integrations may also trigger work from events such as a Slack message or GitHub notification.

Grok Bot currently allows a Bot to own up to 50 routines and keeps the 20 most recent run records for each routine. SpaceXAI recommends testing a routine before enabling it and defining what should happen when source data is missing or stale.

Start and supervise work from mobile

The mobile app connects to the same Bots, conversations, routines, connectors and cloud computer as the desktop application. SpaceXAI now lists iPhone, iPad and Android support. Users can start tasks, attach files or photos, answer questions, review results, approve steps and take over the computer for sensitive actions.

Some advanced controls remain desktop-only. Editing a routine, inspecting full run history and teaching a workflow currently require the desktop app.

What Grok Bot cannot safely promise

The launch language presents Bots as teammates that finish work and return only when approval is required. That is the product ambition, not an independently established reliability rate.

Choosely has not completed documented hands-on testing, and SpaceXAI has not published a simple success rate for end-to-end jobs across third-party applications. Early users may find impressive completions alongside login friction, blocked websites, incorrect decisions, incomplete work and expensive retries.

Current practical limits include:

• A website may block automation or require human takeover.
• One Bot can run one computer-use task on its screen at a time.
• Teach-by-demonstration is rolling out gradually.
• Push notifications are still rolling out.
• The product depends on cloud storage and persistent account access.
• Included weekly usage is described by tier rather than published as a universal number of tasks.
• A long agent run can consume a large share of trial or paid usage.

The correct benchmark is completed useful work after corrections, retries and review time. A charming group chat is not a productivity result.

SpaceXAI's current overview lists macOS, Windows and Linux desktop apps, and mobile apps for iPhone, iPad and Android. Platform support has expanded since the original August publication.

How much does Grok Bot cost?

Grok Bot does not currently have one standalone subscription price. Access is included through eligible Cursor plans or granted by linking an eligible individual SuperGrok account to a Cursor account. The official billing guide explains how the eligible routes share weekly and on-demand usage.

The listed prices are monthly US prices before applicable taxes. Cursor's live pricing lists Pro at US$20 per month and Teams Standard at US$40 per user per month; Cursor's billing guide confirms eligibility across paid individual tiers. Verify prices for other plans on the provider's live checkout before subscribing.

Individual SuperGrok and X Premium+ accounts can now link for Grok Bot access. SuperGrok Team and Enterprise subscriptions cannot use the individual linking route.

The cheapest route is not automatically the best-value route

For an individual who wants Grok Bot and already values Cursor's coding tools, Pro is the lowest advertised Cursor entry point at US$20 per month. Pro+ offers a larger weekly Grok Bot allowance; compare included usage before paying more. Existing eligible SuperGrok or X Premium+ subscribers can link their accounts instead of buying Cursor Pro solely for access.

Teams can enter at a lower per-person sticker price through Cursor Teams Standard, although the total bill scales with seats and usage.

The correct comparison is the whole subscription being purchased, not Grok Bot in isolation.

Usage can extend beyond the subscription

Paid Grok Bot access includes usage that resets weekly. When the included allowance is exhausted, eligible Cursor accounts can continue through shared on-demand spending if it is enabled.

The trial is also usage-based. It comes with a seven-day window, but a large or long-running job can consume most or all of the trial credit in one run. Used trial credit is not restored simply because the result was disappointing.

One more detail deserves attention: linking an individual SuperGrok subscription to a Cursor account is described as permanent. The link cannot currently be removed or moved to another Cursor account without support intervention. Check the signed-in account carefully before confirming it.

Grok Bot security and privacy

Grok Bot's strongest feature and its largest risk come from the same place. It can enter the systems where real work happens.

Every Bot can reach the shared environment

Files, browser sessions and command-line credentials placed on the user-level cloud computer are available across that user's Bot roster. A sales Bot and a finance Bot may have different names and instructions, but those names do not create technical isolation.

Use separate service accounts, narrow permissions and temporary access where the connected platform supports them. Sign out of services and remove sensitive files when a project ends.

Approval rules need to be explicit

SpaceXAI recommends approval boundaries for sending messages, publishing, purchasing, transferring money, deleting data, changing permissions, modifying production systems and accepting legal terms.

Grok Bot offers "Require Approval" and "Always Allow" rules when Auto Review enforcement is available. Auto Review is model-based and should complement least privilege. It should not become permission to allow everything in a browser. SpaceXAI's security and privacy guide recommends narrow rules for consequential actions.

An approval also controls the proposed action only. It does not reverse earlier work the Bot has already completed.

Cloud storage is required

Grok Bot uses Cursor authentication and account data settings. It requires cloud data storage and does not support Cursor's Legacy Privacy Mode. Training opt-out follows the applicable Cursor account and privacy settings.

Organizations should review current Cursor security documentation, contractual terms, retention controls and administrative settings before connecting customer information, production infrastructure or regulated data.

Who should consider Grok Bot?

Grok Bot is most relevant to people whose work contains repeatable multi-step jobs spread across several tools.

Good candidates include:

• Solo operators who repeatedly research, prepare and publish structured work.
• Sales teams that research accounts and prepare outreach for human approval.
• Operations teams that reconcile information across inboxes, portals and internal systems.
• Product and engineering teams that reproduce issues, prepare tickets and hand work between specialists.
• Agencies that can define clear client boundaries and reusable processes.
• Existing paid Cursor users who already have Grok Bot access.

The best first task has a clear finish line, uses replaceable or low-risk data and leaves consequential action for human approval.

Examples include preparing a weekly competitor brief, reconciling a non-sensitive report, drafting support responses, organizing research into a document or reproducing a bug in staging.

Who should wait?

Grok Bot is a weaker fit for:

• Anyone seeking a cheap general chatbot.
• Teams that cannot place work or credentials on a persistent cloud computer.
• Regulated organizations that have not completed security and procurement review.
• Users expecting fixed, easily understood task limits.
• Workflows where a mistaken send, purchase, deletion or production change would be difficult to reverse.
• Teams without enough repeated work to justify setup, supervision and a subscription.

For a one-off question, document or research task, a conventional assistant may remain faster and cheaper.

Grok Bot versus ChatGPT Work and Claude Cowork

Grok Bot enters a market already moving beyond chat.

Its clearest specialist identity is persistent delegated work. Multiple named Bots share a cloud computer, continue while the user's devices are closed, message one another and turn successful work into scheduled routines.

ChatGPT Work is currently the broader connected workspace in Choosely's assessment, especially when work crosses research, cloud services, reusable artifacts and multiple devices. Claude Cowork has the sharper file-heavy and desktop-centered identity, particularly when the job begins in source folders and ends in a polished professional deliverable.

Grok Bot becomes the interesting choice when the user wants several persistent roles operating inside live tools with minimal workflow-building overhead. It also asks for a larger leap of trust because its value increases as more applications, files and credentials enter the shared environment.

Read Choosely's full comparison of ChatGPT Work and Claude Cowork for the adjacent buying decision.

The Choosely verdict

Grok Bot is one of the most convincing product designs yet for making autonomous agents understandable to ordinary professionals. Named roles, messaging, shared context, background work and teachable routines turn a complicated agent system into something that resembles delegation.

The product is still asking users to trust an early beta with a persistent computer and access to real accounts. Its weekly limits are not translated into a predictable number of completed jobs, every Bot shares the same machine, and polished vendor examples do not establish reliability across an individual user's stack.

Start with one narrow workflow that produces a reviewable draft or report. Keep sending, publishing, purchasing, deleting and production changes behind approval. Measure completed useful work, usage consumed and correction time for at least a week.

If Grok Bot reliably returns finished work at a lower cost than doing the same job manually or correcting another agent, it has earned a role. If most of the time goes into supervision, the little team of Bots is still a very expensive group chat.

Frequently asked questions

Is Grok Bot the same as Grok on X?

No. Grok on X and grok.com is the general AI assistant. Grok Bot is a separate agent product that operates through a persistent cloud computer and uses a Cursor account for authentication.

Can Grok Bot work while my computer is off?

Yes. Work runs on the cloud computer, so closing the desktop app, laptop or iPhone does not stop an active background turn or routine.

Does every Grok Bot have its own computer?

Not exactly. Every user receives one persistent cloud computer. All Bots belonging to that user share its files, browser sessions, app logins and command-line credentials, although each Bot receives its own screen for parallel work.

Is Grok Bot free?

There is a free usage-credit trial with a seven-day window. Continued access is available through a paid individual Cursor plan, a self-serve Cursor Teams plan, or a linked eligible individual SuperGrok or X Premium+ subscription. The ordinary free Grok plan does not include Grok Bot.

What is the cheapest Grok Bot plan?

The lowest advertised Cursor individual route is Pro at US$20 per month; Teams Standard starts at US$40 per user per month. An existing eligible SuperGrok or X Premium+ subscription can also grant access. Prices exclude applicable taxes and should be checked live.

Is Grok Bot available on Android or iPad?

Yes. SpaceXAI currently lists macOS, Windows, Linux, iPhone, iPad and Android support.

Can Grok Bot send emails or make purchases?

It can operate in tools where those actions are possible, subject to access and controls. Users should require approval before sending, publishing, purchasing, deleting, transferring funds or changing production systems.

Keep your AI stack honest

If Grok Bot earns a place in your workflow, record the job it owns, the plan it requires and the result that justifies the cost. Choosely lets you save the tools you trust, preserve the reason each one belongs and review the stack as pricing, access and capabilities change.

Save your AI stack free