Wednesday, 6:50 AM
The owner of a small baking-supplies shop opens his phone. In the group chat, three messages are waiting from three bots. "I checked the supplier portal. Two products are back in stock, and I updated the sheet." "I drafted an email to the customers who were waiting for them. I haven't sent it." "A competitor dropped the price on stand mixers. The summary is in the folder."
He never wrote the supplier-portal check as an instruction. He showed it once, in a five-minute recording of himself doing it.
That's Grok Bot. And what matters most about it isn't just what the bots can do. It's that they all work at the same desk.
Grok Bot is the product from SpaceXAI, the company that was called xAI until this summer, and it lets you build a team of permanent AI agents. Each bot gets a name and a role, and they all work on one shared computer in the cloud. In our comparison of Muse, dots and Grok Bot it got one column in a table. Here it gets a full guide: where the name comes from, how it's built, how you teach it a task by demonstration, what stops it, what it costs, whether it's available in Israel and in Hebrew, and dozens of ideas for a small business. We checked every detail against the official SpaceXAI and Cursor documentation. What hasn't been published is labeled as such.
Full disclosure: Platin Digital is an OpenAI Select Partner. That's why we took extra care to be fair to Grok Bot, and every assessment of ours is marked as ours.
In short
- Grok Bot is a team of permanent agents from SpaceXAI (formerly xAI), launched in beta on August 11, 2026. All your bots work on a single cloud computer with a browser, files and a terminal, and they keep working when your own computer is off.
- The standout feature is Teach a task: you record a process in the browser, up to ten minutes, and the bot turns it into a draft skill you can check, fix and schedule. It's rolling out gradually, and only on desktop.
- Before actions run, a model called Auto Review goes over what the bot plans to do, according to rules you write. You type passwords, verification codes and CAPTCHAs yourself. But all the bots share the same logins, and SpaceXAI states explicitly that separate bots are not a security boundary.
- It's included in Cursor plans starting at $20 a month, or by linking a SuperGrok subscription. No list of countries has been published, Hebrew isn't on the published list of languages, and the computers run in the US.
What is Grok Bot? A workshop of apprentices
The bottom line: Grok Bot isn't a chatbot and it isn't a single agent. It's a workshop: several apprentices, each with a role, working at the same bench and learning by watching.
In our comparison of the three big agents, we picked an image for each one. Meta's Muse was born at home. OpenAI's dots were born in the office. Grok Bot was born in the workshop, and that image explains almost everything in this guide.
Apprentices, not one assistant. You create several bots. Each has a name, a role and a description of how it works. One does research, one prepares drafts, one tracks suppliers. They hand work to each other, and you can put up to six of them in a single group chat.
One bench. All the apprentices work at the same bench: one computer in the cloud, with the same files, the same browser and the same logins. That's what lets them pass work along without friction. It's also what demands caution, and we'll get to that in the security section.
Learning by watching. A good apprentice doesn't need written instructions. You show him once, and he repeats it. In Grok Bot this is called Teach a task.
And they carry on after the owner goes home. According to the documentation, closing the app, the laptop or the phone doesn't stop work that's already running in the background or a scheduled routine.
Source: the official Grok Bot documentation on docs.x.ai, the Skills, routines and automations and Chat and collaboration pages, as of October 6, 2026.
xAI, SpaceXAI and Cursor: who's who
The bottom line: Grok Bot carries the Grok name and is presented on x.ai, but you sign in with a Cursor account, and its computers run on Cursor's cloud. All of these companies are now part of SpaceX.
It's confusing, so here's the chronology in plain English:
How we got to Grok Bot: four steps in 2026
- February: SpaceX acquires xAIElon Musk's AI company, which develops Grok, becomes part of SpaceX
- July: renamed SpaceXAIAccording to Engadget, the change was announced on July 6, with a new logo
- August 11: Grok Bot in betaSpaceXAI presents it as "AI teammates" with their own cloud computer
- August 14: Cursor joins SpaceXThe company behind the Cursor code editor announces it is part of SpaceX
Sources: Engadget on the rename, SpaceXAI's Grok Bot announcement, and Cursor's blog from August 14, 2026. In gold: the Grok Bot launch.
According to Cursor's blog, the collaboration with SpaceXAI began back in April, around model training. What matters to you as a user is the practical result:
- The account is a Cursor account. You sign up and sign in with Cursor, and privacy and training settings follow your Cursor account.
- Cursor chooses the model. According to the documentation, there's no model picker, and the model serving each request can change. On launch day, VentureBeat quoted an early tester who said the automatic routing between models wasn't especially good in his tests. That's one person's impression, not a measurement.
- The computers run on Cursor's cloud, in the US. You can't install this on your own server.
- It suits people who don't code, too. Despite the Cursor connection, the official examples include sales, hiring, marketing, expenses and operations, not just code.
SpaceXAI's announcement says the product started as an internal prototype and spread through the company. The message it chose to stress is the gap between work that's 90% done and work that's 100% done. In other words, the claim is that the bot doesn't stop at a draft but finishes the job inside the apps themselves.
How Grok Bot works: one computer, several screens
The bottom line: each account gets one cloud computer. Every bot gets its own screen and its own memory, but the files, the browser and the logins are shared by all. Auto Review sits between the bots and the world.
The bot. According to the documentation, a bot is a permanent "teammate" with a name, a role, its own conversation and a working context that develops over time. You create one from New and then Create new Bot. In its description you write the standing rules, and in messages you write what's relevant to the specific task.
The memory. A bot can save work preferences, important facts and summaries of what it did. The memory is separate for each bot, even when the files are shared. The documentation advises against relying on memory for important decisions and recommends checking against the current source. When you duplicate a bot, the profile, settings and picture carry over, but not the conversations or what it learned.
The computer. In the Agent Computer view you watch the bot's clicks, typing and navigation in real time. Each bot works on its own screen, so several bots can work in parallel, but each bot runs one task at a time. Files worth keeping go in the /workspace folder. If something breaks, Settings > Updates has a Reset option that restores the computer from a backup.
The hands. There are two ways. Plugins from the in-app Marketplace, such as Gmail, Google Calendar and Google Drive, with the option to connect several accounts per service. And the browser: sites with no proper integration, where the bot works using your login. The documentation warns that some sites block automation.
The team. In a group chat you choose between two and six bots, and address them with @ or with @everyone. Bots can also message each other, for example when one bot owns a source of information and another owns the deliverable. And if priorities change midway, you send a message, or click Stop now.
Teach a task: how you teach a bot by demonstration
The bottom line: you show the bot once how to do something in the browser, up to ten minutes, and it writes a draft skill from it. The draft is a starting point, not a finished product: you need to add decision rules and error handling, and test it on a safe example.
This is what most sets Grok Bot apart from its two big competitors. We found no published equivalent feature in Muse or dots. Here's the process, according to the documentation:
Teach a task: from one demonstration to a standing routine
- Describe what you'll showIn a one-on-one chat with the bot, open the computer view, choose Teach a task and describe the outcome
- Record it onceDo the process yourself, up to ten minutes. The screen is captured, the microphone isn't
- The bot writes a draft skillSteps, expected output and limits. No full decision rules, no error handling
- Review and complete itAdd "what to do if," run it on a safe example, and only then schedule it as a routine
Based on the Skills, routines and automations page in the Grok Bot documentation. In gold: your steps. According to the documentation, the feature is rolling out gradually and isn't available in the mobile app.
Skill, routine and automation: three words worth telling apart
The documentation distinguishes between three concepts, and without the distinction it's easy to get confused:
| Concept | What it is | Good to know |
|---|---|---|
| Skill | Reusable instructions: how to do a task. Steps, decision rules, expected output and safety limits | Available to all bots in the account, if they have the needed connections and logins. You call it with / in the compose line |
| Routine | Tells one bot when to run a process: on a schedule, or after an event where supported | Up to 50 routines per bot. The last 20 runs of each routine are kept. Deletion is immediate and can't be undone |
| Event trigger | A routine that starts from an event, such as in Slack or GitHub, through the connections in your Cursor account | The documentation warns against a broad trigger like "every new message": it creates noise, consumes quota and raises the chance of acting on irrelevant input |
A routine is defined with an exact time and time zone, for example "every weekday at 8:00 AM." Before you turn it on, you click Test run. The documentation points out that a run does real work, so you test on safe input and keep every write action behind an approval.
What's the common mistake? Thinking the recording is the program. A recording shows the normal case. It doesn't know what to do when the supplier's portal shows an error message, when a product appears twice or when the table is empty. You add that in writing after the recording, and that's what the review step is for.
Before you record your first task, go through the list. Nothing is saved:
Before you teach the first task
Approvals: Allow once, Always allow, Deny, and what's in between
The bottom line: there are three layers. Auto Review checks actions before they run. Your rules, Ask first and Allow automatically, steer it. And when an action is waiting, you decide: once, always, or no.
The three buttons. Every action waiting for approval is shown with its target and values. Allow once approves only this time. Always allow saves a rule that will match similar actions in the future. Deny blocks. The buttons also work on iPhone.
Two kinds of rules. You write the rules in plain language, under Settings > General > Auto-review:
- Ask first always stops any action that matches it.
- Allow automatically lets an action through only if the reviewer found no other reason to stop.
- When two rules conflict, Ask first wins.
The documentation recommends writing narrow rules, like "ask before any outgoing email to an external address," not broad ones like "approve everything in the browser." Here's how that might look in a small business:
Example rules in a small business
Allow automatically
- Read emails and tag them with a label
- Create files in the workspace folder
- Update an internal tracking sheet
- Search competitors' public websites
Ask first
- Send an email or message to an external address
- Publish a post, comment or review
- Change anything on the site, store or campaign
- Run a command on your computer
You do it yourself
- Passwords, passkeys and verification codes
- CAPTCHA and identity verification
- Payment approval
- Changing a budget or payment method
The red column is based on the list of cases where, according to the documentation, the bot is supposed to hand control to you. The other examples are our own illustration.
Takeover. Passwords, passkeys, one-time codes, CAPTCHAs, payment approvals and identity verification: according to the documentation, the bot is supposed to hand control of the computer to you. You complete the step in Agent Computer and hand control back. You can do this from your phone too. Don't paste a password into the chat. For connections that support it, there's a secure request in which the value is hidden, not saved in the transcript and not shown to the model.
Your computer. A bot can run commands on your local computer too, but only if you allow it. The default is Ask every time, and you can choose Always allow or Never allow. On the security page, SpaceXAI recommends Never allow unless the bot has a specific reason to work on local files. We agree.
Security, honestly: the shared desk
The bottom line: SpaceXAI publishes detailed, candid security documentation. The point every business has to understand: all your bots share one computer, so any login you give one bot is available to all of them.
The documentation says this in several places, explicitly. In the FAQ: "Do not use separate Bots as a security boundary." And on the computer page: the screens are separate work surfaces, "not separate security boundaries." In other words, if you logged in to your bank account through the management bot, the research bot can reach that same login too.
MythEach bot is a separate cell, so I can give each one different access
In realityAll the bots in the account share the files, the browser cookies, the logins and the credentials on the command line. Each one has only its own workspace screen and memory.
MythI deleted the bot, so its access is gone
In realityAccording to the documentation, deleting a bot doesn't delete the files on the shared computer and doesn't disconnect logins. You have to stop routines, log out of sites, remove plugins and delete sensitive files from the workspace yourself.
MythAuto Review will catch every mistake
In realityAuto Review is model-based. SpaceXAI writes that the protections reduce risk but don't eliminate it, and that it complements least-privilege access rather than replacing it.
MythStop now restores the previous state
In realityStopping halts work from now on. Actions that were already carried out, like an email that was sent or a record that changed, remain.
MythText on a website can't influence the bot
In realityThat's exactly the risk called prompt injection. According to the documentation, external content is marked to the model as untrusted information, and there are several layers of protection. Here too, they reduce risk but don't eliminate it.
What else is worth knowing:
- The computers are in the US. According to the security page, Grok Bot computers currently run in the US, only on Cursor's cloud. Cursor's existing data residency program doesn't apply to Grok Bot by default, and a written commitment requires contacting the sales team.
- Between users, separation is strict. Each user signs in with their own Cursor account, and bots act only with the permissions of the signed-in user.
- Privacy according to Cursor. Grok Bot requires cloud data storage, so it doesn't work with Legacy Privacy Mode. Training settings follow your Cursor account.
- A Team Bot gets its own computer. In Slack channels and groups, a Team Bot runs on a separate shared computer that belongs to neither the owner nor any team member. In a private conversation, it works on the computer of the person talking to it.
- Advanced controls are reserved for Enterprise. A network-level allowlist of sites (by default, everything is open), audit logs, and processed command logging that is kept for 90 days and is off by default.
How much does Grok Bot cost: plans and prices
The bottom line: Grok Bot isn't sold separately. It's included in paid Cursor plans, starting at $20 a month, or by linking a SuperGrok or X Premium+ subscription. There's a free trial in the form of credit.
As of October 2026, according to Cursor's pricing and help pages:
| Plan | Price per month | Grok Bot | Good to know |
|---|---|---|---|
| Cursor Hobby | Free | Not included | Grok Bot starts at Pro |
| Cursor Pro | $20 | Included | Weekly quota. The cheapest plan that includes it |
| Cursor Pro+ | $60 | Included | A larger weekly quota than Pro |
| Cursor Ultra | $200 | Included | The highest quota among the individual plans |
| Cursor Teams, Standard seat | $40 per user | Included for every team member | No need for a Premium seat or a request to an admin |
| Cursor Teams, Premium seat | $120 per user | Included | 5x the usage of a Standard seat in Cursor |
| Cursor Enterprise | Not published, custom | Rolling out | Access, network and audit controls for Grok Bot |
| SuperGrok, SuperGrok Plus, SuperGrok Heavy, X Premium+ | Per x.ai pricing | Via link to a Cursor account | Heavy gets the highest quota. SuperGrok Lite, Team and Enterprise are not included |
A few small details that make a difference:
- The free trial is credit, not a number of days, and it also has a seven-day window. Usage is measured by agent steps and tokens, not by number of messages. The credit amount hasn't been published.
- Beyond the quota, you can continue with pay-per-use, but only if you turned on On-demand. Billing is monthly, and you can set a cap. We recommend setting one.
- The SuperGrok link is a usage grant, not a Cursor plan. It doesn't stack with an existing Cursor plan, and it's permanent: it can't be moved to another account.
- In a team, a Team Bot's usage counts against the quota of each team member who uses it, not the quota of the person who created it.
And what about the $120 and $300 from the headlines? At launch, Grok Bot opened only to SuperGrok Heavy, Cursor Ultra and Cursor Teams Premium subscribers. VentureBeat wrote on August 11 about $120, the price of a Premium seat. 9to5Mac wrote on September 4 that the starting price had been $300 a month, and that it now works with Cursor Pro at $20. In all cases, the subscription includes more than the bot: all of Cursor, or all of Grok.
Platforms: where you talk to Grok Bot
The bottom line: you set up on a computer and use it from anywhere. You can do most of the day-to-day work from your phone, but teaching tasks and editing routines stay on the computer.
| Platform | Requirements | What you can do |
|---|---|---|
| macOS | Apple silicon or Intel | Everything. Required for the first setup |
| Windows | x64 or Arm64 | Everything |
| Linux | x64 or Arm64, in deb, rpm or AppImage files | Everything |
| iPhone and iPad | iOS 18 or iPadOS 18 and later | Messages, dictation, voice conversation, images and files, creating bots and groups, viewing the computer, takeover for a password or code, pausing and resuming routines |
| Android | Version 9 and later | Same as iPhone |
| Slack | Team Bot only | The owner adds the bot, and it writes under its own name. Team members link their own Slack account |
According to the documentation, editing a routine's schedule or instructions, running a test, Teach a task and some advanced settings are available only on desktop. Push notifications on mobile are still rolling out. The app interface is available in more than 20 languages. According to 9to5Mac, at launch it arrived on Mac and iPhone, and in early September iPad and Android were added.
You can also talk to it: a live voice conversation, dictation (Cmd or Ctrl plus D on desktop), and the bot can send a voice message with a transcript. Microsoft Teams, WhatsApp and Telegram don't appear as channels in the documentation we reviewed.
How to set up your first bot: step by step
The bottom line: setup is simple, but it starts on a desktop. What determines the result is the role you give the bot, and how narrow it is.
The steps are based on the Get started page in the official documentation:
- Make sure you have a suitable plan: paid Cursor, Cursor Teams, or a SuperGrok subscription you'll link. If your Cursor account is set to Legacy Privacy Mode, you'll need to switch to a supported setting.
- Install the desktop app from the Grok Bot download page: for macOS, Windows or Linux.
- Sign in. Choose Sign in, complete the login in the browser and return to the app. You link a SuperGrok subscription under Settings > Usage & Billing.
- Create your first bot. Choose one of the suggested bots, or Create your own, and give it a short name, one role and a description of how it works.
- Give it a task. In writing or by dictation, with five things: the outcome, the sources, the constraints, the deliverable, and where you want to check in before it continues.
- Connect the tools it needs. When the bot needs access to a site, open Agent Computer, take over, log in and hand control back.
- Test and refine. Ask for corrections, and save a process that works as a skill or a routine.
Grok Bot examples in a small business
The bottom line: Grok Bot is especially strong in three situations: work that splits across several roles, processes that live on sites with no ready integration, and tasks that are easier to show than to write. All the examples here are our own illustration, not documentation of a particular user.
SpaceXAI's official examples include an outbound sales bot, a recruiting bot, a bot that tracks media budgets, a weekly expense-reconciliation bot and a "chief of staff" bot that summarizes what changed. The official marketing guide from September 24 has six bots, among them a bot that builds campaign structures in Google Ads and fills them with approved copy, and an analyst bot that pulls data from Google Ads and makes recommendations, but according to the guide doesn't change an ad, a bid or a budget. Here's how that translates to a small business:
Online store
- Suppliers bot: checks stock and shipping dates in supplier portals
- Catalog bot: finds products with no image, price or description
- Service bot: draft replies to recurring questions, for your approval
- Competitors bot: a weekly summary of public prices and promotions
Service providers
- Meetings bot: a prep page before every meeting, from email and calendar
- Quotes bot: a list of open quotes and draft reminders
- Reviews bot: tracks new reviews and drafts responses
- Chief of staff bot: a morning summary of what needs a decision
Marketing and advertising
- Research bot: competitors' landing pages and messaging gaps
- Campaigns bot: a draft campaign structure, no spend until approved
- Analyst bot: a weekly report and recommendations, without touching the budget
- Content bot: draft posts from recordings and documents
Operations and admin
- Expenses bot: matches receipts from email to a sheet and flags what's missing
- Recruiting bot: a first screen of resumes against written requirements
- Tenders bot: a daily check of public tender sites
- Vendor bot: tracks subscription and contract renewals
Teach a task on older systems that have no integration
Here Grok Bot is truly different. Many small businesses work with a system that has only a browser interface: a supplier portal, an old appointment-booking system, a shipping company's interface. They have no API and no plugin. This is exactly what Teach a task was built for.
| The system | What you record | The rule you add |
|---|---|---|
| A supplier's order portal | Go to the stock page, search ten SKUs, copy to a sheet | Allow automatically for reading and updating the sheet. Ask first for ordering |
| An old appointment-booking system | Export tomorrow's appointment list and mark who hasn't confirmed | Ask first for every message to a patient or customer |
| A shipping company's interface | Check the status of open shipments and list the delays | A draft customer update only. Sending: Ask first |
| A workshop registration system | Copy new registrants to a sheet and prepare a confirmation email | Ask first for every outgoing email |
| A tender or government authority site | Search by keywords and summarize new tenders | Read-only. No registering and no submitting |
| A store admin interface | A list of products with no image or with zero stock | Read-only. Any product change: Ask first |
| A WordPress admin interface | A list of plugins waiting for updates and comments awaiting approval | Read-only. A plugin update only after a backup, and with your approval |
Look at the right-hand column. It matters more than the recording. And in every one of these rows, the login to the system will be available to all the bots in the account, not just the one that learned the task.
A day with three bots
Pick a time, and see how one day might look in a small shop with three bots. An illustration. The business, the names and the numbers are fictional.
Suppliers bot · routine every weekday at 7:00 AM · taught with Teach a task
I logged in to the pan supplier's portal and checked the ten SKUs on the list. Two are back in stock, and one is marked "out of stock" until the end of the month. I updated the inventory sheet.
✓ Sheet updated · nothing ordered
The rule: reading and updating the sheet under Allow automatically. Any order: Ask first.
Service bot · one-on-one chat
Someone emailed asking when the mixer is back in stock. Can you answer her?
According to the sheet the suppliers bot updated this morning, it's back at the end of the month. I drafted a reply with the date and an offer to let her know when it arrives.
! Draft waiting · Allow once · Deny
Sending an email to an external address: Ask first. The bot read the sheet because the files are shared across all the bots.
Marketing bot · one-off task
Prepare a search campaign structure for baking pans, with three versions of the copy. Don't turn anything on.
I prepared the campaign structure, the ad groups and three versions of the copy. The campaign is saved paused, with no active budget. The decision to turn it on is yours.
✓ Draft ready · ! Activation and budget: yours
The login to the ads account is available to the other two bots as well. That's exactly the point to weigh before you connect.
Group chat · all three bots
@everyone what needs a decision from me today?
Service bot: one draft is waiting for approval. Marketing bot: the campaign structure is waiting for review. Suppliers bot: no open decisions, but one SKU is out until the end of the month.
2 open decisions · 1 note
In a group chat you can combine between two and six bots, and address all of them with @everyone.
The owner · from the phone, before bed
I approve the email to the customer. I'll review the campaign tomorrow.
The email was sent. The campaign stays paused. In the morning I'll run the stock check again, as usual.
✓ Sent with your approval · campaign waiting
An illustration. The business, the names and the content are fictional. Allow once approvals work from the iPhone too.
Grok Bot vs Muse vs dots, in five lines
The bottom line: each of the three has a home turf. The full, line-by-line comparison is in the article Muse, dots or Grok Bot.
- Grok Bot is a team of bots on a shared computer, with learning by demonstration. Strong on sites with no ready integration and on several bots in parallel, and included in Cursor from $20.
- Meta Muse is a personal agent, strong in shopping, WhatsApp and Meta's tools. It has a free tier, but as of today it's available only in the US and Canada.
- OpenAI dots are agents inside ChatGPT, with a separate computer for each dot and detailed rules for each type of action. Included in plans from $100.
- On separation between agents, dots lead, because each dot has its own computer. In Grok Bot all the bots share one computer.
- For ready-made work in Google Ads, only Grok Bot has an official guide. For WordPress we found no ready integration in any of the three.
Grok Bot in Hebrew and in Israel: what we know
The bottom line: SpaceXAI and Cursor haven't published a list of countries, and we found no restriction that refers to Israel. Hebrew doesn't appear on the published list of languages. The way to know is to test it yourself, in the free trial. If you're outside Israel, check availability and local rules for your own country.
- Availability in Israel: not published. Cursor's plans page doesn't mention a geographic restriction for Grok Bot, and access is determined by the subscription. But there's also no explicit confirmation that Israel is included.
- Hebrew interface: not published. According to the documentation, the app is available in more than 20 languages. The published examples include English, Spanish, French, German, Japanese, Korean and Chinese. Hebrew isn't among them.
- Working in Hebrew: not published. There's no model picker, and Cursor chooses the model. Whether the bot writes a good email in Hebrew, understands a Hebrew website and gets text direction right is something you need to check on a real task.
- The computers are in the US. If you have a legal or contractual obligation to keep certain information in Israel, such as medical information or customer information, check with an advisor before you connect those systems.
Here's how to test it in half an hour:
- Open a Cursor Pro plan, or use the free trial. The credit is limited, so save it for a focused test.
- Install the desktop app, and check whether Hebrew appears as an interface language in the settings.
- Create one bot, and give it a task in Hebrew: summarize a page from an Israeli website and write a draft email in Hebrew.
- Check three things: the quality of the Hebrew, the word order and text direction in the draft, and whether the Israeli site blocked the cloud browser.
- If everything works, try one task with Teach a task, if the feature is already open to you.
Who Grok Bot suits, and when a dedicated agent makes sense
The bottom line: Grok Bot is a strong and relatively inexpensive tool for people willing to manage it themselves. A dedicated agent justifies itself when you need separation between systems, a deep connection to your website and advertising, or someone to set it up and maintain it.
We don't think either one is always better. They're two tools for two jobs:
Grok Bot
An off-the-shelf team of bots, which you manage
- You start quickly, from $20 a month
- Several bots in parallel, each with a role
- Learns a browser process from a demonstration
- Works with your logins, shared by all the bots
- Rules, connections and cleanup are your responsibility
A dedicated agent for the business
Set up around your systems
- Requires setup and a break-in period
- A separate server, with a dedicated user and permission for each system
- Direct connection to WordPress, Google Ads, Meta and Analytics
- Approval rules that follow the business's processes
- Whoever sets it up also maintains and documents it
A short quiz. Answer "Yes" if the sentence is true for you today:
And in fairness: for a business with a few old browser systems and research and tracking tasks, Grok Bot can be entirely enough. A dedicated agent justifies itself when the work lives in WordPress and advertising accounts, when each system needs its own user and permission, or when you don't have time to manage it. We explained what goes into such a setup in What goes into building an AI agent, and the full picture in the guide An AI agent for your business.
And what does this mean for Platin Digital
Platin Digital is an OpenAI Select Partner. We set up agents for businesses with whichever models and tools fit each business best, from OpenAI, Anthropic, Google and others, running on a separate cloud server for each client, connecting to WordPress, Google Ads, Meta and Analytics with a dedicated user and minimum permission in each system, and receiving tasks through Telegram. Publishing, budget changes and sensitive actions always wait for your approval.
We see Grok Bot as a serious product with an excellent idea: teaching an agent by demonstration. If it fits some of your tasks, we'll say so.
Frequently asked questions
What is Grok Bot?
Grok Bot is a product from SpaceXAI, the company formerly called xAI, launched in beta on August 11, 2026. In it you create a team of permanent bots, each with a name and a role, that work on a shared cloud computer with a browser, files and a terminal, and keep working even when your own computer is off. You can teach them a process by demonstration, schedule routines for them and talk to them from desktop and mobile. You sign in with a Cursor account, and Cursor also chooses the model.
How much does Grok Bot cost?
It isn't sold separately. According to Cursor, it's included in the Pro plan at $20, Pro+ at $60 and Ultra at $200 a month, and in Cursor Teams, at $40 or $120 per user per month. You can also link a SuperGrok, SuperGrok Plus, SuperGrok Heavy or X Premium+ subscription. There's a free trial in the form of credit with a seven-day window, and beyond the quota you can pay per use if you turned that on.
Is Grok Bot available in Israel and does it work in Hebrew?
No list of countries has been published, and we found no restriction that refers to Israel, but no explicit confirmation either. The interface is available in more than 20 languages, and Hebrew isn't among the published examples. The quality of work in Hebrew hasn't been published. The bots' computers run in the US. The way to know is to test it in the free trial, with a small task in Hebrew. If you're outside Israel, check availability for your own country.
What is Teach a task?
A feature in which you show the bot a process in the browser instead of writing it instructions. You choose Teach a task in a one-on-one chat, describe the outcome, carry out the process once, up to ten minutes, and the bot writes a draft skill from it. The microphone isn't recorded. You need to complete the draft with decision rules and error handling and test it on a safe example. According to the documentation, the feature is rolling out gradually and is available only on desktop.
Are my bots separated from each other?
Only partly. Each bot has its own workspace, conversation and memory, but all of them share one cloud computer, with the same files, the same browser cookies and the same logins. SpaceXAI states explicitly that separate bots shouldn't be used as a security boundary. Deleting a bot also doesn't delete files and logins from the shared computer. Between different users, the separation is strict.
Can Grok Bot manage Google Ads and my business website?
In an official guide from September 24, SpaceXAI shows a bot that builds campaign structures in Google Ads and an analyst bot that pulls data and makes recommendations, without changing ads or budget. This works through your account and your login, on a computer that all the bots share. We found no ready integration for WordPress, but a bot can enter the admin interface in the browser. For ongoing work on the website and advertising, a dedicated agent with a separate user and permission for each system is usually a better fit, and budget changes and publishing should always wait for your approval.
Sources
- https://x.ai/news/introducing-grok-bot
- https://x.ai/bot/guides/grok-bot-101
- https://x.ai/bot/guides/grok-bot-for-marketing
- https://docs.x.ai/grok-bot/overview
- https://docs.x.ai/grok-bot/get-started
- https://docs.x.ai/grok-bot/faq
- https://docs.x.ai/grok-bot/bots
- https://docs.x.ai/grok-bot/chat-and-collaboration
- https://docs.x.ai/grok-bot/computer-and-apps
- https://docs.x.ai/grok-bot/skills-routines-and-automations
- https://docs.x.ai/grok-bot/approvals-security-and-privacy
- https://docs.x.ai/grok-bot/security
- https://docs.x.ai/grok-bot/team-bots
- https://docs.x.ai/grok-bot/mobile
- https://docs.x.ai/grok-bot/settings-and-notifications
- https://docs.x.ai/grok-bot/use-cases
- https://cursor.com/help/grok-bot/plans
- https://cursor.com/pricing
- https://cursor.com/docs/account/pricing
- https://cursor.com/docs/account/teams/pricing
- https://cursor.com/blog/joining-spacex
- https://venturebeat.com/orchestration/spacexais-grok-bot-turns-agents-into-persistent-digital-coworkers-that-can-operate-your-apps-for-120-per-month
- https://9to5mac.com/2026/09/04/spacexai-expands-grok-bot-to-ipad-as-access-expands-to-cheaper-plans/
- https://www.engadget.com/2209300/xai-now-officially-spacexai/
