Grok Bot

About Grok Bot

Grok Bot lets you create named AI teammates that keep working on a persistent cloud computer. Give one a research job, another an operations role, and let them use connected apps, browse websites, and hand work between each other.

The important qualification is that your Bots share one computer. They have separate conversations and screens, but the same files, browser sessions, and app logins. That makes collaboration convenient; it does not give every Bot an isolated environment.

I would consider Grok Bot for repeatable work that crosses several tools, especially if I already paid for an eligible Cursor or SuperGrok plan. Cursor Pro at $20/month includes access. Subscriptions come with weekly usage, and additional work can incur on-demand charges, so access and workload cost are separate buying decisions.

What is Grok Bot?

Grok Bot is a task-execution product with a roster of persistent agents. You create a Bot, give it a job and relevant access, then message it with the outcome you want. Its cloud workspace includes a browser, filesystem, and terminal.

Although xAI presents the product, Grok Bot signs in through a Cursor account and runs on Cursor-hosted computers. Current xAI documentation links to Cursor's billing rules. It is separate from the ordinary Grok chat app, with a different usage meter.

The name also does not mean every task runs on one fixed Grok model. Cursor chooses the serving model, the mix can change, and there is no customer-facing model picker. If model choice is a major reason you are buying an agent, that is a meaningful constraint.

The current platform list includes macOS, Windows, Linux, iOS, and Android. These apps are interfaces to cloud work: closing your laptop or phone does not stop a cloud task or routine.

Who is Grok Bot for?

Grok Bot fits operators who repeatedly move information between tools: collecting invoices from vendor portals, preparing account research, or turning customer issues into a reproduction report for engineering. The appeal is giving those jobs a persistent owner without setting up a server yourself.

For example, an operations Bot could gather invoice files into a project folder and prepare a list of missing documents. A second Bot could review that list against the supplied requirements. That is an illustrative workflow, not a promise that every vendor portal will permit unattended access.

I would start with one role and a visible finish line. Add another Bot only when a separate responsibility helps.

If you mainly need a reliable place to record deadlines, start with our guide to task-management apps. Grok Bot is for delegating execution. It is a poor match for someone who needs self-hosting, a fixed model provider, or separate credentials for every client-specific Bot.

Grok Bot pros and cons

Grok Bot features: Shared computers, specialist Bots and routines

Several Bots working on one computer

Each Bot gets its own screen on the account's cloud computer. Several Bots can work in parallel, although one Bot can run only one computer-use task on its screen at a time.

Files and signed-in browser sessions are shared. A Bot can pick up a document another Bot saved without a download-and-upload relay. Conversation history and learned context remain separate per Bot, so handing off the relevant explanation still matters.

This arrangement suits related jobs inside one working environment. I would not use different Bot names as the separation between unrelated clients. Deleting a Bot does not remove the shared computer's files or signed-in sessions either.

Give handoffs an owner

Group chats support two to six Bots. You can mention a specific Bot, ask for work from the group, or let Bots message one another asynchronously. A receiving Bot can wake, perform its part, and reply later.

A useful split might put source collection with one Bot and checking a draft's claims with another. Someone still needs to own the final deliverable.

Human messages in groups can include attachments, but Bot-to-group handoffs are text-only. A Bot that needs another Bot to inspect an image should send it directly rather than assume the group handoff carried it.

Save a method, then schedule it

A skill describes how to do a job: inputs, steps, decision rules, expected output, and checks. A routine tells a particular Bot when to run it. Private skills are shared across your Bots, while each routine has an owner.

The Teach a task feature can record visible computer interaction for up to ten minutes, without microphone audio. It turns the demonstration into a draft skill to review and test. Availability can roll out gradually, and one recording will not necessarily capture exceptions such as a missing file or changed website.

Bots support up to 50 routines each, with the 20 most recent run records retained per routine. Schedules can run while your laptop is closed. Event-triggered work can also start from a Slack message or GitHub notification through account integrations, which are separate from simply installing those plugins.

A routine's Test run performs real tool and file actions. It is useful for checking the workflow, but it is not a simulation that automatically avoids changes.

Use connectors where available, a browser where needed

Grok Bot can use structured app connectors and operate websites through its browser. You can watch its computer and take over when a site needs a password, passkey, CAPTCHA, or another human step. Persistent sessions reduce repeated sign-ins, though sites can still expire them.

Connectors have specific limits. Gmail supports one mailbox at a time according to Cursor's service-specific help. Google Sheets edits depend on the connected account's permissions; view-only access does not become write access. Slack posts through the connected user's account and channel access.

That is why I would assess an agent against the actual apps in a workflow, not the length of its integration list. Browser access can fill gaps, but it does not guarantee that every website will cooperate.

Review messages without abandoning the conversation

Grok Bot supports text, attachments, dictation, live voice chat, and voice memos with transcripts. Email and Slack drafts can appear as editable cards, so you can review recipients and wording before choosing to send or discard them.

A direct message from you takes priority over background work. You can redirect a job when the brief changes, but stopping work does not undo actions already completed. Auto Review adds action checks; it does not make every result correct or every action reversible.

Grok Bot vs OpenClaw, Dot and Poke

OpenClaw is the stronger candidate for someone who wants control over the runtime and model setup. It supports messaging channels, browser work, memory, skills, and scheduled jobs. You also operate the Gateway and keep its host available. Grok Bot removes that hosting job but gives up self-hosting and model selection.

Dot is worth comparing if ChatGPT already contains the context you want an assistant to use. Its current personal offer starts with one Dot; Grok Bot exposes multiple named roles and group handoffs now. Dot's Pro rollout excludes the EEA, Switzerland, and UK, while Business Premium has a broader supported-region policy.

Poke is the lighter option for email, calendar, and reminders through Apple Messages, Telegram, WhatsApp, or RCS. Its free plan makes it easier to explore that style of assistance without buying a cloud-computer workflow.

Grok Bot pricing: Eligible plans and usage billing

Grok Bot access comes through eligible subscriptions rather than a separate required Bot subscription. These are published monthly routes in September 2026:

Cursor prices exclude applicable taxes. Individual SuperGrok Plus, SuperGrok Heavy, and X Premium+ also qualify for linking. SuperGrok Lite, Team, and Enterprise do not. An eligible mobile user shares the same account entitlement rather than needing another subscription for the phone app.

The weekly allowance is not a published number of completed tasks. It resets weekly, and higher tiers provide more headroom. Once it runs out, Grok Bot stops unless on-demand usage is enabled. Extra usage is billed through Cursor against the on-demand monthly limit.

The monthly spending limit is not a hard mid-run stop. A Bot already working can finish past it, after which additional on-demand work stops until the limit increases or the billing cycle resets. Self-serve Teams has on-demand usage enabled by default, so teams should not assume included usage is their only possible charge.

Cursor and linked SuperGrok or X Premium+ usage grants do not stack. Paying both subscriptions does not combine their Bot allowances, and linking does not cancel either bill. The account link is permanent and cannot be moved or unlinked by the user, so the Cursor account you choose matters.

There is a usage-credit trial with a seven-day window. It is not seven days of unlimited work: one long job can consume the credit. That trial does not automatically become a paid plan. An Apple App Store introductory offer is different and can renew into a paid Apple subscription unless canceled; Android has no in-app trial.

If you already have an eligible subscription, explore Grok Bot with that account before buying a higher tier. I would measure the usage of one recurring job first rather than upgrade on the assumption that more Bots require the most expensive plan.

Verdict: Give one Bot a useful recurring job

Choose Grok Bot if you want managed cloud agents with distinct ongoing roles and do not want to maintain the runtime. Existing Cursor and eligible SuperGrok subscribers have the clearest reason to start: access may already be part of a bill they pay.

I would give one Bot a bounded operations task, inspect the result and usage, then decide whether another role helps. Choose OpenClaw for self-hosting and model control, Dot for existing ChatGPT context, or Poke for messaging-first personal help. Shared computers and metered work are central to the decision, not small-print details.

FAQ

Is Grok Bot the same as Grok chat?

No. They are separate apps with separate meters. A Weekly SuperGrok Limit in the Grok chat app is not the Grok Bot allowance. Grok Bot uses your Cursor account, including when access comes from a linked subscription.

Does Grok Bot keep working when my laptop is closed?

Yes. Cloud tasks and routines continue independently of the app being open. Work that specifically needs your local computer is a separate capability with its own permissions.

Does Grok Bot support Windows, Linux, and Android?

Yes. The current xAI documentation lists macOS, Windows, Linux, iOS, and Android.

Do separate Bots have separate app accounts?

Not by default. Your Bots share the account's cloud computer, browser sessions, files, and connected plugins. Separate conversations and screens do not isolate those shared resources.