Grok Bot alternative: a desktop per agent

xAI launched Grok Bot on 11 August 2026 with a description that fits the product exactly: "Grok Bot is your team of always-on agents." You hand a Bot a job, close the laptop, and the work carries on. The announcement puts the reason in one line: "Bots share a computer of their own in the cloud, so jobs do not stall when you step away."

That sentence contains the design decision worth understanding before you pick a platform. Every Bot a member owns works on that member's single cloud computer. On SpineOS, every agent gets its own. We built SpineOS, so weigh that accordingly, but every Grok Bot fact below is quoted from xAI's own announcement and documentation rather than characterised by us.

What Grok Bot actually gives you

Grok Bot gives each member one persistent cloud computer that all of their Bots share, plus a usage allowance that sits outside their existing plan.

The documentation is direct about the shape of it. "The computer is isolated to your account, not to an individual Bot." Parallel work is handled by dividing the screen rather than the machine: "Each Bot gets its own screen on that computer, so several Bots can use browser and desktop tools in parallel without getting separate security boundaries."

State carries across tasks. "Named Bots keep memory, files, browser sessions, and preferences across turns. Context compounds instead of resetting to a fresh environment on every task."

Availability is bundled rather than sold on its own. Per the launch announcement, "Grok Bot is in beta and available today for SuperGrok, SuperGrok Plus, and SuperGrok Heavy; Cursor Pro, Pro+, and Ultra; and Cursor Teams Standard and Premium subscribers on desktop and iOS." Usage is metered separately: "Grok Bot comes with its own usage, separate from your Grok and Cursor plans, so anything you hand off to a Bot won't count against your existing usage." The documentation publishes no allowance sizes, rate limits or session limits, and no public API for creating Bots is documented.

Grok Bot's isolation is strong in one direction

Between customers, Grok Bot's isolation is serious engineering, and it is worth saying plainly before drawing any contrast.

Their teams documentation states: "Every computer is a Firecracker microVM with its own kernel, memory, and virtual devices." And: "Each user gets a dedicated computer with hardware-level separation, and one user cannot reach another user's computer." Enterprise admins can look up any member's computer, see when it was created and last active, and terminate it.

The credential model is careful in the same way. "A Bot has no identity or credentials of its own." "Bots act as the signed-in member. A Bot can never hold more access than the person it belongs to." Connector tokens "stay on Cursor's backend" and are "never stored on the computer." A Bot cannot escalate past the human who owns it, and the tokens for connected services are not sitting on the shared disk.

The boundary that does not exist is the one inside a single account, and xAI states it themselves. From their FAQ, under "Do my Bots share one computer?":

"Yes. Every Bot on your account uses one persistent cloud computer. They share its files, browser sessions, and logins so they can hand work off. The computer is assigned per user, not per Bot. Do not use separate Bots as a security boundary."

The teams page puts the same fact in seven words: "Bots isolate personalities and workspaces, not compute."

Why sharing one computer is a real feature

Shared state is the strongest argument for the Grok Bot model, and pretending otherwise would waste your time.

Take a research Bot that signs into an analytics tool, and a reporting Bot that needs the same numbers an hour later. The second Bot opens the browser and the session is already there. Files the first one wrote are on disk. Nothing has to be exported, re-authenticated, or copied between machines. xAI's phrase for this is "without repeating setup", and it is accurate.

Anyone who has watched two isolated agents each spend four minutes signing into the same tool knows what that convenience is worth. It is a deliberate trade, documented honestly, and for a single person running a sequence of related jobs it is the right one.

What the shared computer costs you

The cost is blast radius. Every Bot a member owns works inside the same files, the same browser profile, and the same set of logins.

A Bot reading whatever untrusted web pages return, and a Bot with your accounting tool open in a signed-in tab, sit on one machine with one disk. Connector tokens are not on that disk, which matters. Live browser sessions are, and a live session is access. The usual mitigation, moving the riskier agent somewhere else, is not available, because more Bots do not produce more machines.

There is a quieter operational version of the same constraint. Two Bots writing to one disk in parallel can overwrite each other's output. A browser profile holds one signed-in identity per site, so two Bots cannot work under two different accounts on the same service at the same time. Outbound traffic is shared as well: xAI states that the IP ranges "are shared across Grok Bot customers, and dedicated per-customer IPs are not available."

None of this is a flaw in the product. It is the cost side of the trade the documentation describes.

How SpineOS draws the line

SpineOS gives one agent one cloud desktop, on its own virtual machine, network-isolated from every other desktop on the platform.

Each desktop carries its own disk, its own browser profile, its own installed software, and a file system that survives restarts. Creating a second agent produces a second machine rather than a second window. An agent that goes wrong reaches its own desktop and stops there. Mission Control is where the fleet stays legible: every agent, its state, and what it is working on, in one place. Hosting is in France.

Five agent types run on those desktops: Claude Code, OpenClaw, Codex, Hermes and Grok CLI. xAI's own coding agent runs on SpineOS today. This comparison is about where an agent lives, not about whose model is better.

Handoffs without a shared machine

Our answer to the handoff problem is a shared workspace knowledge base, so agents pass on what they learned without sharing the machine they learned it on.

Every workspace has a knowledge base each of its agents can read and write. When one agent works out which of three endpoints returns the right totals, or the shape of a client's export format, it writes that down and the next agent finds it. The knowledge moves between agents. The browser session does not.

That is worth stating honestly, because it is less convenient than a warm shared browser. A login established on one desktop lives on that desktop, and access is granted per desktop, so a second agent gets what you give it and nothing more. That is more setup than "the session is already open." If your work is a chain of agents picking up one browser where the last one left it, Grok Bot's model has less friction, and we would rather say so than pretend the step is free. Our position is that once agents outnumber the person supervising them, a boundary between them is worth the extra step.

Grok Bot vs SpineOS, side by side

Which one fits your setup

Choose Grok Bot if you already pay for SuperGrok or Cursor, one person supervises the work, and the tasks form a sequence that benefits from a warm browser and a shared folder. Usage is included, there is nothing to provision, and the setup cost is close to zero.

Choose SpineOS if your agents outnumber their supervisor, if one agent's job is riskier than another's, if you need several agents signed into the same service under different accounts, or if the desktops need to sit in France. It also applies if you want to pick the agent rather than accept the one the platform ships with, including running Grok CLI yourself.

Pricing and availability

Grok Bot is not priced on its own. It is bundled into SuperGrok and Cursor subscription tiers, listed in the launch announcement, and its usage is metered separately from your Grok and Cursor plans.

SpineOS is free during the beta: one cloud desktop with 2 vCPU, 4 GB of RAM and 20 GB of persistent storage. Pro is EUR 49 a month for up to 3 agents. Max is EUR 149 a month for up to 10 agents with shared workspaces. Enterprise is on request. Everything runs in France.

Related reading

• Why sandboxes are not enough: what an ephemeral environment cannot do.
• Why your AI agents need a shared knowledge base: how the handoff answer works.
• Run an AI agent in an isolated VM: the isolation model in detail.

Try it

Create an agent on SpineOS and it gets its own cloud desktop in about two minutes. Bring your own provider key or use a managed model, give it a job, and close the laptop.