Independent consulting on rolling out Grok Bot (xAI)
Grok Bot in your company: settle the rules before you demonstrate
With “Teach a task”, Grok Bot learns a workflow when someone on your team demonstrates it once. Before that happens with real data, data protection, the works council and credentials should be sorted out. We support the rollout.
How Grok Bot learns a workflow
Grok Bot is an AI agent from xAI that works on a persistent cloud computer and operates a browser there the way a person would. With “Teach a task” nobody has to describe the workflow: it is demonstrated once and recorded. That is convenient, and it means the agent may see more than the workflow needs. Each step raises a question that should be answered before the first real use.
Demonstrate
Someone on your team completes a task once in the browser of Grok Bot's cloud computer while the agent watches.
Settle first
Who records, and has this been agreed with the works council?
Recording
According to xAI, up to ten minutes of visible activity on the cloud computer, without microphone audio.
Settle first
Are customer or employee data on screen, or a password in plain view?
Skill
The recording becomes a draft skill that the agent later runs on request or on a schedule.
Settle first
Who reviews the draft, adds rules and approves it?
Cloud computer
Grok Bot works on a persistent computer in Cursor's cloud, currently in the United States according to xAI. All Bots on an account share it.
Settle first
Which sign-ins are stored there, and who else can use them?
Your systems
The agent clicks and types in mailboxes, CRM, portals and web applications it is signed in to.
Settle first
What may it do without asking, and what is logged?
Based on xAI’s documentation at docs.x.ai, as of 30 October 2026. Grok Bot was introduced as a beta in August 2026 and is evolving; features and terms may change.
What can go wrong during rollout
None of these points rules out Grok Bot. They show where a company without preparation ends up with a data protection, labour law or security problem.
The recording may capture more than the workflow
Demonstrating a task with real data also records whatever is visible in the applications at the time: customer names, emails, employee data. xAI itself advises against exposing secrets during the demonstration. Processing takes place at a service provider in the United States. Under the GDPR that requires a legal basis, a data processing agreement and safeguards for the transfer to a third country. Anysphere's data processing agreement also prohibits providing special categories of personal data.
Where there is a works council, it has to be involved
Under settled case law of the German Federal Labour Court, co-determination under Section 87(1) no. 6 of the Works Constitution Act applies as soon as a system is objectively capable of monitoring performance or behaviour. Screen recordings of employees usually are, even if they are only meant for training the agent.
Sign-ins live outside your company and apply to every Bot on an account
Grok Bot signs in with logins from its Vault, from a connected password manager (so far 1Password with personal or Family accounts, own vault only, rolling out gradually) or through a form a person fills in. It can read one-time codes from a connected mailbox. For single sign-on, passkeys or a CAPTCHA it cannot get past, a person takes over. The signed-in session then stays on the cloud computer. According to xAI, all Bots on an account share that computer with its files and sessions, and the separate screens are not security boundaries. Signing in an account with broad permissions there hands it to every Bot and skill on that account.
The agent follows instructions that are not yours
An agent reads web pages, emails and documents. If they contain a planted instruction, it may follow it (prompt injection). xAI marks outside content for the model but states that these safeguards reduce the risk without eliminating it. Under Cursor’s Grok Bot Terms, approvals and automated reviews are aids only.
Your team is ahead of IT
Grok Bot can be used with a personal subscription. Employees sometimes try tools like this before any rule exists, and company data then flows through private accounts without a contract reviewed by the company and without central administration. According to xAI, on self-serve Cursor Teams plans every member gets Grok Bot without an admin request. According to xAI, an organisation-wide switch, network controls and audit logs are only available in the Enterprise edition.
One account, one cloud computer
Your account
- Mailbox bot
- Invoices bot
- Research bot
One shared cloud computer
- Signed-in browser sessions
- Files in the workspace
- Command-line credentials
Cursor cloud, currently in the US per xAI
Your systems
- Mailbox
- CRM
- Customer portal
Separate screens, but no security boundary: every Bot can use every sign-in on this computer
What the Enterprise edition includes and what it does not
According to xAI, the organisation-wide switch, network controls, audit logs, action recording and SCIM are only available in the Enterprise edition. Self-serve teams do not see these settings, and a personal subscription does not have them either. Members sign in with their Cursor account; according to xAI, the account’s SSO configuration applies, for example SAML with Okta, Microsoft Entra, Google Workspace or OneLogin.
Enterprise edition only
- Organisation-wide switch deciding whether Grok Bot may be used
- Network controls for which destinations Bots may reach (without a policy everything is allowed; connected apps and MCP servers only with the additional switch “Apply to MCP servers”, which is off by default)
- Audit logs for admin, security and authentication events, including export to a SIEM
- Recording of Bot actions (Action Recording), off by default
- User provisioning via SCIM 2.0 from your own identity provider
- Inference hooks (beta): model requests go to your own policy server first, for example for data loss rules. New configurations start in shadow mode and do not block anything yet
Not available there either
- Inference hooks do not check actions, only the input sent to the model
- No retention policy per organisation
- No on-premises deployment, only Cursor-hosted cloud computers
Based on xAI’s security documentation at docs.x.ai/grok-bot/security, as of 30 October 2026.
How we support the rollout
The goal is that your team can use Grok Bot without losing control of data, access or co-determination. The steps build on each other, and you decide after each one whether to continue.
Inventory
Which workflows will be demonstrated, which data are visible while doing so, which accounts does the agent need, and who already uses Grok Bot or similar agents today?
Contract and data flows
Together with your data protection officer we compile which plan fits technically, which contract documents the vendor provides for it and what technical information they give on retention, training and processing location. Open points go to your legal counsel as a list of questions.
Accounts and permissions
Dedicated accounts for the agent instead of personal logins, only the permissions the workflow needs, no payments or approvals without confirmation (according to xAI, a payment card saved in the Vault is used without separate approval), network controls, sign-out and revocation in place.
Documents for the works council and a policy
A technical description of what is recorded, stored and analysed, as the basis for a works agreement, plus a short usage policy for your team. The legal drafting is done by your legal counsel.
Pilot on a low-risk workflow
One workflow with test data or without personal data, with logging, defined stop criteria and a review before more workflows are added. xAI itself points out that a test run performs real work.
What we do not do
We are not a law firm and do not provide legal advice. We deliver the technical and organisational basis on which your legal counsel, your data protection officer and your works council decide. We do not sell licences for xAI or Cursor and hold no stake in any vendor.
Alternatives
AI agents compared
ChatGPT Work, Claude Cowork, Copilot Studio and other agents side by side: where they work, how they sign in and what the business editions include.
See the comparison →Background
Securing autonomous AI agents
Permissions, approvals, logging and protection against planted instructions apply to every agent, not just Grok Bot. Our practical guide explains the basics.
Read the guide →Rules for AI
AI compliance and governance
When more than one tool is involved: policy, roles and evidence for using AI across the company, with reference to ISO 27001 and the AI Act.
AI compliance and governance →Frequently asked questions about Grok Bot in your company
What is Grok Bot?
Grok Bot is an AI agent from xAI, introduced as a beta on 11 August 2026. It works on a persistent cloud computer with a browser, file system and terminal and completes multi-step tasks there, on request or on a schedule. According to xAI, these computers run in Cursor's cloud. On its own sites, xAI now appears under the name SpaceXSI.
What is “Teach a task”?
With “Teach a task” you demonstrate a browser workflow to Grok Bot once. According to xAI, up to ten minutes of visible activity is recorded, without microphone audio. The agent turns it into a draft skill that you are meant to review, extend with decision rules and test on a safe example. According to xAI, the feature may be enabled gradually, so it is not necessarily visible in every account yet.
Can we use Grok Bot in our company?
There is no blanket answer. It depends on which data the agent sees, which plan you use and what the terms say about data processing and transfers to the United States. Until that has been checked, no personal data should end up in recordings or tasks.
Does the works council have to agree?
Where there is a works council and employees have their on-screen work recorded, there is a strong case for it. Under German Federal Labour Court case law, it is enough that a system is objectively capable of monitoring performance or behaviour; no intent is required. A works agreement is the usual route. We provide the technical description for it, the legal assessment belongs with your legal counsel.
Where is our data processed?
According to xAI, Grok Bot computers run in Cursor's cloud in the United States. Enterprise customers can have teams enrolled in Cursor's US-only data residency program, at a surcharge and with exceptions such as single sign-on and connected services. For the EU, Cursor generally offers inference-only coverage on request so far; whether that includes Grok Bot is not documented, and the documentation does not mention EU data residency for Grok Bot. If you buy The X Subscription, its terms say you buy from X Subscription Corp. in Texas, while the services are provided by the respective vendors. Which data processing agreement then applies, and whether it covers your use, is part of the review before rollout.
Where are our credentials stored when Grok Bot signs in?
Grok Bot can store logins and payment cards in its Vault; the values are filled into the page without the model seeing them. The signed-in session then stays on the cloud computer, and every Bot on the account can use it. Tokens for connected apps (OAuth) are held by Cursor, not on the computer. The agent should therefore get dedicated accounts with narrow permissions, not employees' personal logins, and no payment card in the Vault if every payment needs approval. According to xAI, deleting a Bot does not remove the sessions on the shared computer; they have to be ended deliberately.
How much does Grok Bot cost?
For new customers, xAI includes Grok Bot in the Premium, Super and Ultra plans of The X Subscription, not in Plus. List prices are 30, 100 and 200 US dollars per month plus tax, the same per seat for teams. Grok Bot draws on the seat's shared weekly usage; usage beyond that costs extra. According to xAI, existing Cursor, SuperGrok and X Premium plans continue. On Cursor Enterprise, an admin enables Grok Bot for the team, and for pricing the documentation refers to Cursor's account team (as of 30 October 2026). For a company rollout, the price matters less than which plan comes with the contracts and admin controls you need: the organisation-wide switch, network controls and audit logs are Enterprise only.
Is Grok Bot available in Germany?
We found no Germany-specific restriction in the Grok Bot documentation (as of 30 October 2026). That is not a general availability commitment; the subscription terms contain the usual country and export reservations. According to xAI, tagging @bot on X is not yet available for accounts based in the EU, the United Kingdom, Iceland, Liechtenstein, Norway and Australia, nor for accounts without a specific country on record.
Does Grok Bot run on Windows?
According to xAI, the desktop app is available for Windows (x64 and Arm64), macOS and Linux, plus apps for iPhone and Android. Most of the work happens on the cloud computer at Cursor. Through the desktop app, however, Grok Bot can also run commands on your own PC, read files and move files between the two computers. By default each local command needs confirmation; it can be blocked entirely, and admins can restrict it for the team. xAI recommends keeping local execution blocked unless a Bot needs it.
Do you also advise on other AI agents?
Yes. The same questions arise with any agent that operates browsers and applications on behalf of your team, such as ChatGPT Work, Claude Cowork or Copilot Studio with computer use. An overview with a comparison is on our page on AI agents for business. Our advice is vendor-independent, and we will tell you if another tool or classic automation fits better.
Are you affiliated with xAI or Cursor?
No. Blackfort Technology is an independent information security consultancy and is neither a partner nor a reseller of xAI or Anysphere, the company behind Cursor. We do not sell licences for these vendors.
As of 30 October 2026. Grok and Grok Bot are products of xAI, which now appears as SpaceXSI on its own sites; Cursor is a product of Anysphere. Blackfort Technology is not affiliated with either company. The information on Grok Bot is based on xAI’s public documentation and does not replace a review of the current terms. This page is not legal advice. The photos on this page are AI-generated illustrative images.
Before your team records its first workflow
Tell us which workflows Grok Bot should take over. In an initial call we work out what needs to be in place first.