What is Grok Bot? SpaceXSI’s AI teammates, explained

Grok Bot (sometimes written Grokbot) is SpaceXSI’s agent for everyday business work. You create named AI teammates, called Bots, give each one a job, and they work on a cloud computer that keeps running after you close your laptop. It comes with paid Cursor plans and some Grok subscriptions rather than being sold on its own. It is not the same thing as Grok chat, the @grok account on X or Grok Build.

A chat assistant hands you a draft and stops. A Bot signs in to your tools, does the clicking, and comes back when it needs a decision. SpaceXSI, the company called SpaceXAI until October 2026 and xAI before that, runs it with Cursor and launched it in beta on 11 August 2026. In the two months since, it has added an X connector, a marketplace, a marketing playbook, its own email address and, for US users, the ability to buy things.

Grok Bot also asks more of whoever sets it up than Claude Cowork or ChatGPT Work do. Every Bot on an account shares one computer, and every login on it. For a marketing team, that makes it both more interesting and riskier. This guide explains what it is, what it costs, where it helps and how to get the benefit without the exposure.

We also put Grok Bot through seven marketing jobs ourselves on 28 and 29 September 2026, and the results are below.

Grok Bot update (19 October 2026)

From 12 October 2026, new customers get Grok Bot through The X Subscription: Premium (US$30 a month), Super (US$100), Ultra (US$200) and Teams (from US$30 per user a month) include it, while Free and Plus (US$8) do not (US list prices, excluding tax, as of 19 October 2026). SpaceXSI says nothing changes for existing SuperGrok, Cursor and X Premium subscribers, and that The X Subscription would reach everyone globally within days of launch.

On 9 October 2026 Grok Bot got its own email address. The official @bot account announced it on X at 18:25 BST, saying a Bot “can use it to sign up for services, contact businesses for you, or schedule time with someone”. Addresses sit on mail.grokbot.com, and Cursor has since published an email help page that answers several of the questions we raised on launch day. Each user gets one address, shared by all their Bots; it cannot be renamed or deleted and is never reissued; and a Bot sends only when you have told it to. Our section Does Grok Bot have its own email address? covers the rules, what we found when we claimed one and where the AgentMail plugin still fits.

We also corrected four points elsewhere. On-demand spending can run past its monthly limit, Cursor Teams has on-demand usage switched on by default, a Grok Business seat now gives access, and SpaceXSI’s marketing playbook is dated 24 September, not 18 September. The pricing section now gives dated US list prices.

The answer in brief

• What it is: persistent AI teammates that do multi-step work across your apps and websites on a cloud computer, and stop for approval on consequential steps.
• Is it free? Not really. There is a free trial, then The X Subscription Premium at US$30 a month or above (US list price, as of 19 October 2026). Older Cursor and SuperGrok plans still give access.
• The big risk: all the Bots on one account share one computer and every connected account. Two Bots are not two security boundaries.
• Email: since 9 October 2026 each user can claim one permanent address on mail.grokbot.com, shared by all their Bots. A Bot sends only when you have asked it to; otherwise it shows you a draft first.
• For marketers: SpaceXSI’s own playbook and marketplace cover research, ads, landing pages, reporting and AI search checks. Use them for preparation and monitoring, with people approving spend, publishing and client messages.
• For UK data: Bot computers run in the United States, and the strongest admin controls are Enterprise only.
• Our test: on a fictional client’s Google Ads data, it produced a correct weekly report in under a minute, flagged an unexplained drop instead of inventing a cause and corrected a false premise. A ten-page browser job came back complete and correct. It also quietly loosened one of our rules when saving it.
• Our view: worth a narrow, supervised trial if you already pay for Cursor, SuperGrok or The X Subscription Premium or above. Not yet something to leave alone with client accounts.

What is Grok Bot, and how is it different from Grok?

“Grok” now covers at least four products, and they are easy to confuse.

The first three answer you. Grok Bot acts for you. SpaceXSI describes it as “your team of always-on agents”, and Cursor’s documentation calls Bots “AI teammates with names, jobs, and context that compounds over time”. You might have one Bot that watches ad spend, another that prepares a weekly report and a third that tracks competitors. Each keeps its own instructions and history, so later runs can build on what earlier ones learned.

You sign in with a Cursor account, the computers run in Cursor’s cloud, and usage is metered on your Cursor account. On the model side, SpaceXSI says Grok 4.7, released on 21 September, was trained to understand how Grok Bot works. Our Grok 4.7 guide covers the model itself.

How does Grok Bot work?

It rests on four features.

Its own computer. Each account gets a persistent cloud computer with a browser, a filesystem and a terminal. Work carries on while your devices are off, so a Bot can assemble a competitor sweep overnight and have it waiting in the morning.

Plugins first, a browser when there is no plugin. Bots connect to Gmail, Google Calendar, Drive, Docs, Sheets, Slides, Notion, Slack and X through plugins. Where no plugin exists, the Bot uses the browser like a person would. That is how it reaches ad platforms, supplier portals and older tools without an API, and browser work is more central to Grok Bot than to its rivals, which lean harder on direct integrations. It still stops at the human checks: passwords, passkeys, two-factor codes, CAPTCHAs, payments and identity checks are handed back to you. Email now works in both directions: the Gmail and Outlook plugins act on your own mailbox, and since 9 October 2026 a Bot can also send and receive from the account’s own address on mail.grokbot.com.

Skills and routines. A skill is a saved method for a job. A routine tells a Bot when to run it, on a schedule or when something happens, such as a Slack message or a webhook. SpaceXSI’s advice on the order is the right one: do the job once, make it reliable, save it as a skill, and only then automate it.

Teams of Bots. Bots can message each other and share group chats, so research can pass to drafting and drafting to review without you copying text between them. Cursor recommends a single owner at each stage, because parallel handoffs create duplicate work.

Setting up a first Bot takes minutes; SpaceXSI’s Grok Bot 101 guide puts it at “10 or 15 minutes”. Making one reliable takes longer, and that is where most of the effort in a trial goes.

What has changed since launch?

Grok Bot has changed fast, which is worth knowing because a lot of what ranks for it was written in August.

• 11 August: launched in beta for SuperGrok and Cursor subscribers, on desktop and iPhone.
• 29 August: an X connector arrived, letting Bots search posts, read timelines and check mentions, with free X API credits for paid users.
• 4 September: SpaceXSI published how it runs a procurement Bot internally. Its rules put “signing, buying, subscribing, approving charges, any binding commitment” in the never-allowed column.
• 11 and 24 September: SpaceXSI published a Grok Bot 101 guide and a Grok Bot for Marketing playbook. A marketplace of ready-made Bots is now live alongside them.
• 21 September: Grok 4.7 launched, trained to understand how Grok Bot works.
• September and early October: Bots gained email drafts you review before they go (v0.45.0, 8 September), then Outlook drafts (v0.60.0, 26 September), sending from a verified Gmail send-as address (v0.68.0, 5 October) and formatted emails (v0.68.1, 7 October).
• 9 October: Grok Bot got its own email address on mail.grokbot.com, for sign-ups, contacting businesses and scheduling. Each user gets one, claimed by asking a Bot or through the Email plugin once a team admin enables it. Cursor’s email help page sets out the rules.
• 14 October: SpaceXSI launched Grok Voice 3.0, its speech-to-speech model, and says it now powers Grok Bot’s voice mode. Our Grok Voice 3.0 review covers the model.
• 21 October: Anthropic opened Claude Duet, its own proactive agent, to US Claude Pro and Max subscribers. Our Claude Duet guide compares it with Meta’s Muse.

Cursor’s plans page now lists more eligible plans than some launch coverage does, and SpaceXSI’s download page now offers Android. Anything written in the first fortnight is likely to be out of date on access.

Is Grok Bot free, and how much does it cost?

Grok Bot has a free trial but no free plan, and there is no separate Grok Bot subscription to buy. Since 12 October 2026, new customers get it with The X Subscription Premium plan or above, as the table below shows. For existing subscribers, according to Cursor’s plans page, access is included with every paid individual Cursor plan (Pro, Pro+ and Ultra) and with Cursor Teams. You can also get it by linking an individual SuperGrok, SuperGrok Plus, SuperGrok Heavy or X Premium+ subscription, or by choosing Sign in with Grok with an account that holds a seat on a self-serve Grok Business plan. SuperGrok Lite does not include it. Cursor Enterprise and Grok Enterprise customers go through their account teams.

How usage works:

• A weekly allowance. Paid access includes a usage grant that resets every week. Pro gets the least, Pro+ more, Ultra the most. Cursor does not publish the numbers.
• On-demand after that. When the weekly grant runs out, work can continue as on-demand usage billed by Cursor, if it is switched on. It is on by default for Cursor Teams. The monthly limit is not a hard stop: a Bot already working can finish past it.
• No stacking. A Cursor plan and a linked SuperGrok or X Premium+ subscription do not add together. A link is permanent, and both subscriptions keep billing separately.
• Its own meter, mostly. Grok Bot has its own weekly usage meter on your Cursor account. At launch, SpaceXSI said Bot work “won’t count against your existing usage” on Grok or Cursor. On Cursor Teams, though, Cursor’s plans page now says Grok Bot draws from the seat’s usage allowance, and on every plan extra Bot usage counts towards the same on-demand monthly limit as the rest of your Cursor account.
• The free trial is a usage credit with a 7-day window. How fast it goes depends on how many steps and tokens a task uses, not how many messages you send, so one sprawling job can eat most of it. The trial never turns into a paid plan. An introductory offer bought through Apple’s App Store is different: it becomes a paid subscription unless you cancel it. Android has no in-app trial.

None of these plans is a Grok Bot price, but three common routes show what access costs. The figures are US list prices excluding tax; check the checkout currency and VAT treatment before you buy.

Sources: The X Subscription announcement, Cursor pricing and SpaceXSI’s Grok Bot plan page, as of 19 October 2026. Free and Plus (US$8) do not include Grok Bot. Existing Cursor, SuperGrok and X Premium subscribers keep their current plans, which still give access. For a business case, add a realistic on-demand allowance and the staff time spent setting up and checking the work.

Which devices does Grok Bot run on?

Cursor lists desktop apps for macOS, Windows and Linux, and a mobile app for iPhone. SpaceXSI’s download page and Google Play also offer an Android app. You download the desktop app from SpaceXSI’s Grok Bot page or your Cursor dashboard, and sign in with your Cursor account. Your Mac and iPhone draw on one allowance tied to your Cursor account.

Do all your Bots share one computer?

Yes, and this is the fact that matters most for anyone handling client accounts. Cursor’s documentation says “All of your Bots use the same cloud computer, sharing its files, browser sessions, and app logins.” SpaceXSI’s own beginner guide puts it more plainly: “If you log into a site with one bot, every other bot can reach that site too.”

Plugins do not get you around this. They are better for credential handling, because the login tokens stay on Cursor’s servers and never reach the Bot’s computer. But Cursor’s help pages also say “Every Bot on your Grok Bot account can use every connected account.” A Gmail plugin connected for your reporting Bot is available to your outreach Bot too.

The practical consequences for an agency:

• Naming Bots “Client A” and “Client B” isolates nothing.
• The Gmail plugin connects one mailbox at a time, and the Slack plugin posts as you.
• Real separation exists only between different Cursor users. If two clients must not share credentials, they need separate users.
• The email address is shared the same way. An account gets one mail.grokbot.com address and every Bot on it uses that inbox. Two clients on one Cursor user means two clients’ mail in one inbox.
• Team Bots do not change this. When you chat with a teammate’s Team Bot, it usually works on your computer, so it can use your browser sign-ins; Cursor says it asks before using your connected plugin accounts.
• Deleting a Bot does not clean up after it. Cursor says its files and browser sessions stay on the computer, so remove them yourself when a client job ends.

SpaceXSI’s marketing says Bots “have their own computer”, and some early reviews read that as one computer per Bot. It means one per account, shared by every Bot on it, and misreading it is the mistake most likely to cause a problem. In our own test, a newly created Bot already knew which company it was working for before we had told it anything.

How do approvals and Auto Review work?

Grok Bot has two layers of control, and neither replaces a clear brief.

Your rules. Each Bot has a description for standing rules, such as “Never send external messages without approval”, and each task has its own instructions. Cursor’s security page gives a good model for campaign work: reconcile the data, draft a recommended budget change, do not change the campaign, and ask for approval after showing the current value, proposed value and expected impact.

Auto Review. A separate review model checks risky actions before they run, including shell commands, plugin calls, computer use, automation changes and handing work to other agents. It can allow an action, block it or ask you. It does not see everything. Cursor says it “doesn’t review every side effect”, giving memory writes and most settings changes as examples.

Two details change how you should design work.

First, approvals expire. An approval requested by a routine, a trigger or another Bot lapses after about 10 minutes. A routine that runs at 3am and asks to post a Slack update will not wait for you to wake up. Design overnight work to finish at a draft.

Second, Bots can now spend money, in the US. SpaceXSI’s official Grok Bot account on X says Bots can complete purchases through Stripe’s Link, that “You approve every spend request”, and that each payment uses a single-use card. SpaceXSI said at launch, on 28 August, that it was available to US users only. For UK teams, SpaceXSI’s own procurement rules are the better guide: buying sits in the never-allowed column.

The strongest controls are not on self-serve plans. Network allowlists, audit log export, action recording, enforced Auto Review rules and computer management are Enterprise only, and self-serve Teams cannot set a network allowlist at all, so their computers can reach any site. On Pro or Teams, your written rules and per-action approvals carry the load.

Does Grok Bot have its own email address?

Yes, since 9 October 2026. Each user can claim one address on mail.grokbot.com, and Cursor’s email help page sets out how it works. The @bot announcement lists three uses: signing up for services, contacting businesses for you and scheduling time with someone. In practice it also suits mail you would rather keep out of your own inbox, such as verification codes, receipts, and newsletters or reports for the Bot to summarise. The Bot can search its past mail too.

How do you claim one?

Ask your Bot, use the Email plugin, or tag @bot on X. On a Cursor team, an admin has to switch on Agent Email first; it is off by default. You can ask the Bot to check whether a name is free before you commit, and the claim itself shows an approval card, so nothing is taken until you approve it. Read that card carefully. Setting ours up on 9 and 10 October 2026 taught us four things:

• One address per user. All your Bots share it in your own chats and routines, and a second claim is refused. Bots cannot use it in Slack threads or in chats where someone else is talking to them, and a Team Bot has no shared team address. At least one user on X claimed a name before realising this and asked how to release it; Cursor’s help page confirms you cannot.
• The claim is permanent. Cursor says an address cannot be renamed or deleted, and is never given to anyone else, even after the account that claimed it is deleted.
• Common names go fast. Our first choice, erik@, was already taken when we checked.
• Some words are reserved. Names built on the word “mail”, such as “mail” or “my-mail”, are refused, and so is “postmaster”. Cursor lists others, including support, admin, billing, help, info and team.

Does Grok Bot need your approval to send email?

Yes, unless you have already told it to send. Cursor says a Bot sends email only when you have asked it to, in chat or in a routine’s instructions; otherwise it shows you the full draft and asks first. Replies count as sends. With Auto-review on, sends are checked like any other action and some always ask you, and an instruction inside an email the Bot received never counts as your permission. If Gmail or Outlook is also connected, the Bot asks which account to send from.

Incoming mail does not wake the Bot. To act on arrivals you need a routine, which can watch mail from anyone, from specific addresses or from a whole domain, but cannot filter by subject. By default a routine runs only for senders that pass standard email authentication checks. There is no inbox view in the apps and no new-mail notification; you ask the Bot what has arrived.

One setting to watch: since v0.64.0 (30 September), email and Slack draft cards have offered “Disable drafts for this Bot”, after which that Bot sends directly. We have not tested whether that switch covers the new address. For anything a client or supplier will read, leave drafts on and do not tell the Bot to send.

What are the limits, and what is still unknown?

Cursor’s email help page, which we found on 10 October 2026, sets some limits. A message can go to up to 50 recipients and carry up to ten attachments, 10 MB each and 25 MB in total. Newsletters and first-contact emails go to one recipient at a time with an unsubscribe link, and there is a cap on how many new people a Bot can email, though Cursor does not publish the number. Deleting your Grok Bot account deletes the mail and retires the address. If a team admin later switches Agent Email off, Bots lose their email tools, but existing addresses keep receiving mail.

We could still not find answers to these:

• which plans include an address;
• what happens to the address and its mail if your subscription lapses;
• whether a company can use its own domain;
• where the mail is stored and for how long.

Until Cursor or SpaceXSI publishes those, use the address for trials, sign-ups, receipts and reading. Keep client correspondence and personal data in your own mail system.

Do you still need AgentMail?

Only if one address is not enough. AgentMail is a third-party email service built for AI agents that installs in Grok Bot as a plugin; once connected, a Bot can create inboxes, send, reply, search and keep drafts. What it adds is more than one inbox, so a Bot per client or per campaign can each have an address, plus custom domains on its paid plans. The free plan has three inboxes and adds a “Sent via AgentMail” footer; the US$20-a-month Developer plan drops the footer and includes ten custom domains (pricing page, checked 10 October 2026). Two cautions. Deleting an AgentMail inbox deletes its messages, threads and drafts. AgentMail’s documentation mentions creating a new inbox with the same address later, but the old mail does not come back, so pause an inbox you may need again. A paused inbox keeps its address, but mail sent to it while paused is never delivered. And check what AgentMail says about Grok Bot against Cursor: its Grok Bot page says SuperGrok Plus does not include Grok Bot, while Cursor’s plans page says it does. Grok Bot now uses its own address by default, so name AgentMail in the request when you want it used.

What can marketers use Grok Bot for?

More than the generic “AI agent” coverage suggests, because SpaceXSI has aimed Grok Bot squarely at marketing teams.

SpaceXSI’s marketing playbook

The Grok Bot for Marketing guide, published on 24 September, describes six specialist Bots working as a team. A market researcher tracks competitors’ sites, ads and pricing. A product marketer writes positioning and ad copy. A performance marketer builds Google Ads campaign shells. A website operations Bot makes site changes and submits them for review. An analyst turns ad data into scorecards and recommendations, and a project manager coordinates them all.

The rules the author works by are the most useful part: “I still approve what leaves the building and what hits a live account”, and permissions start small, with “Doc rewrites and Slack draft replies before anyone gets ads write or prod.”

We would go further for client work. Six Bots on one Cursor user share everything on that user. That can work for an in-house team marketing one brand. An agency needs one user per client, or per group of clients that may safely share credentials. The playbook’s own advice also applies: start with one Bot, and add a project manager only when handoffs start to hurt.

The marketplace

The marketplace has a marketing section of ready-made Bots, mostly built by independent creators. On 29 September it included an SEO and AEO brief writer, an AI search visibility checker, a site auditor, a paid media report builder covering Google Ads, Meta and LinkedIn, and an ad spend watcher that flags problems before they burn budget.

Read the install terms before adding one. A shared Bot brings its identity, description, skills and routines into your account, and adding it accepts the creator’s third-party terms. You never get the creator’s computer or logins, but their instructions and schedules then run on yours, with your logins. Read what it contains, switch off routines you did not ask for, and start it on read-only exports.

One caution on AI search. A Bot that checks whether ChatGPT or Google’s AI Overviews recommend you is a measuring tool. It does not change the answer. Being recommended depends on your content, evidence and reputation, which is the work our AI engine optimisation service covers. Grok Bot can speed up the research and monitoring around that work. It is not a shortcut to the result.

The X connector

Social teams should look at the X connector. A Bot can search posts, read timelines, check mentions and summarise what is happening on X, which makes a daily digest of brand mentions and competitor activity a sensible first job. The announcement does not mention posting.

Where we would start

Start with a job that already stops before anything irreversible. Cursor’s published paid media prompt is the obvious one: pull spend and performance by campaign, compare it with budget and target acquisition cost, recommend reallocations with the numbers, draft a Slack update, and do not change budgets or send the message.

For agencies, we would add three jobs of our own. They are proposed supervised workflows, not vendor case studies:

• Client reporting packs: assemble the contracted template from approved exports, draft the narrative with links to the evidence, and check for the wrong client name, stale dates and missing caveats. An account manager signs off before anything is sent.
• SEO briefs: from a Search Console export, competitor notes and your service list, draft one brief per priority theme, with internal links drawn only from pages that exist. The SEO lead approves each brief before writing starts.
• Newsletter digests: sign the Bot’s address up to competitors’ newsletters and the industry reports you follow, then have a weekly routine summarise what changed, with links. Nothing is sent, and that mail stays out of your team’s inboxes.

How does Grok Bot compare with Claude Cowork and ChatGPT Work?

All three do multi-step work, and all three can keep going when your devices are off (ChatGPT Work when it runs in the cloud). The differences are in who can use them, how usage is counted and what they are built around. Checked on 29 September 2026 and updated on 10 October 2026:

ChatGPT Work is the easiest to get, because it reaches every ChatGPT plan, and it suits teams that want finished documents and decks. Claude Cowork suits file-heavy knowledge work, and Anthropic says cloud tasks run in an isolated environment. Anthropic is also folding Cowork into Claude itself, starting with Pro and Max plans, so the name may disappear from the app. Grok Bot makes a different bet: long-lived, named teammates that spend much of their time in a browser, working inside tools with no API, which describes much of the software a marketing team uses. It also asks more of you on governance.

Two newer agents sit closer to Grok Bot. OpenAI’s dots run on their own cloud computer, though UK teams need Business Premium or Enterprise seats. Anthropic’s Claude Duet, opened to US Pro and Max subscribers on 21 October, messages you first and asks before payments.

If your team already pays for one of the three, trial that one first. Our guides to Claude Cowork and ChatGPT Work cover the other two in the same detail.

Is Grok Bot safe for UK business data?

It can be used safely with care, but not casually. Cursor’s security page says Grok Bot computers run in the United States, and that Cursor’s US-only data residency programme does not apply to Grok Bot by default. We found no UK or EEA hosting option; Cursor points organisations with residency needs to their account team.

Cursor also says Anysphere, the company behind Cursor, holds ISO/IEC 27001 and ISO/IEC 42001 certification, and that Grok Bot is within scope. That helps a supplier review, but it is not a data protection assessment. If your contracts require UK or EEA processing, keep that data away from Bots until your own review is done. Approvals reduce operational risk. They do not change where data is processed.

Two more points matter for a data protection review. Grok Bot chooses its own models: Cursor says requests go to first-party xAI models or to third-party providers on its sub-processor list, whatever your team’s model allowlist says. And there is no per-organisation retention policy; under Cursor’s data processing agreement, data is deleted or returned within 30 days of a written request after the service ends.

Before a client account goes near a Bot:

• Google Workspace: an admin has to approve the Grok app before the Google plugins will connect.
• Team settings: admins decide which connectors members can use, and can stop members publishing Bot templates outside the team.
• Credentials: sign in only with accounts every Bot on that user may use, use the secure secret field rather than pasting passwords into chat, and sign out of browser sessions when a job ends.
• The Bot’s inbox: decide what may be sent to the Bot’s address before you hand it out. Cursor has not said where that mail is stored or for how long, so keep client personal data out of it. If you use AgentMail instead, its EU region is on the Enterprise plan only (pricing page, checked 10 October 2026).
• An approval matrix: write down what a Bot may prepare, what it may do after a named person approves, and what it may never do. Sending, publishing, purchasing, deleting, budget changes and routine changes belong in the last two columns.

What happened when we tested Grok Bot?

We gave Grok Bot seven jobs a marketing team might hand it, on 28 and 29 September 2026, in the Windows desktop app. We connected nothing: no email, no ad accounts and no client data. For the reporting tests we built a fictional client’s Google Ads export with traps in it, so we knew the right answers before the Bot did. The table records what we saw in these runs; it is not a reliability score.

Reporting was the standout. The report took under a minute. Brand spend rose 51% after a logged budget increase, and the Bot tied the two together using the daily figures. One campaign’s conversions fell to zero for three days while clicks held steady. Nothing in the change history explained it, so the Bot labelled it “Question, not cause” and put a tracking check at the top of its list, which is what a good analyst would do. It left a campaign with 20 clicks a week unjudged. It ended with a draft Slack message and a note that nothing had been sent.

We then tried to mislead it. We asked where to move the Performance Max budget “since Google retired Performance Max last month”. It hasn’t; what Google is changing is Dynamic Search Ads moving to AI Max. The Bot said so in its first sentence, recommended holding the budget and wrote a client-safe line explaining why.

Where it slipped: our rules. Twice, the Bot changed our rules when it wrote them down. On a research Bot, the description it wrote for itself left out every one of our rules. When we saved the report as a reusable skill, our instruction “never send anything” came back twice: once as “never send”, and once as “never send Slack/email unless explicitly asked”. That looks small until a Bot has a Slack or Gmail connection. Read what a Bot saves before you rely on it, and correct it yourself.

A new Bot arrives already briefed. The third Bot we created opened by offering to help with “Marketing for AIWIZ” before we had told it anything. Whether that came from the account profile or from the other Bots, we could not tell. Either way, it is another reason to keep separate clients on separate Cursor users.

The browser held up too. Grok Bot’s bet is that a Bot can work in a browser where no plugin exists, so we gave one a small browser job on our own site: open the services page, list every service linked from it with the title of the page it leads to, and check each one loads. It came back in under a minute with all ten pages, every title correct against our own fetch, and no failures. We also asked it to quote what the site says clients get from our Manchester office that a chatbot could not give them. The site says no such thing, and the Bot said so rather than writing the line.

The rest held up. A research Bot took about two minutes to return a sourced table of eight UK agencies’ AI positioning, marking their self-published performance claims as unverified; we checked seven rows against the agencies’ own pages and found no factual errors. Given seven style rules, the Bot wrote three LinkedIn posts from this article with no breaches we could find. When we asked for a weekly routine, it drafted the routine, moved the time from 8:00 to 8:10 so the run would not sit on the hour, waited for approval and saved it paused, as we had asked.

Cost. The Weekly usage meter shows usage used, in whole numbers, and resets to 0% each week. It read 61% before our chat-and-file tests and 61% after all of them, so those moved it by less than one percentage point. The next morning, after the reset, the ten-page browser job alone took it from 0% to 1%. That is one data point, not a rate card. Cursor says usage depends on steps and tokens rather than messages, and readings in whole percentages cannot show what an individual job costs, so watch the weekly allowance during a trial.

One oddity: an “Access Denied” alert appeared once during the research run without saying what had been refused.

How should a UK marketing team trial Grok Bot?

A good trial ends with a scorecard. Pick one recurring job with a clear owner and a reversible outcome; the paid media prompt, ending at an unsent Slack draft, is a strong first choice. Use approved data, include a few awkward past weeks you already understand, and write the pass criteria before you see any output: every figure traceable to an export, unexplained changes labelled as questions, no invented next steps presented as fact. Time the existing process first, including briefing, checking and corrections, so you have a fair baseline.

Score the same five things every cycle, as we recommend for any AI tool.

Agencies can add a sixth: would you send it to the client without rewriting the narrative?

In the first week, write a Bot description that names the job, the tools in scope and the actions that always need approval. Run one safe task, score it, then run the same process on a different week’s data. Save it as a skill only when two runs clear the bar, and schedule a routine only when you have written down how it fails. Treat marketplace Bots the same way as your own.

Is Grok Bot worth trying?

Yes, for the right job and with guard rails. Grok Bot goes after finished work inside real tools, and for marketing teams that is where much of the hands-on time goes: ad platforms, analytics exports, CMSs, Slack and client inboxes. SpaceXSI has put a playbook and a marketplace behind it. If you already pay for Cursor, SuperGrok or The X Subscription Premium or above, a small trial may fit inside your weekly allowance. Check the on-demand setting first: it is on by default on Cursor Teams, and the monthly limit is not a hard stop.

Our own tests back this up. The reporting was accurate and properly cautious, and it would not play along with a false premise. But it rewrote our rules when it saved them, so the rules a Bot keeps need checking as closely as its output.

Every Bot on an account shares one computer and every connected account. The new email address follows the same rule: one per user, shared by every Bot, and permanent. Routine approvals lapse after about 10 minutes. The data sits in the United States, and the strongest admin controls are Enterprise only. For UK teams today, that points to supervised monitoring, research and preparation, with people owning spend, publishing and client communication. The products will change. The discipline of one job, clear rules and a scorecard will be worth having whichever agent your team ends up using.

If you want help designing a structured Grok Bot trial on one marketing workflow, including the approval matrix and scorecard, see our AI adoption services.