Grok Bot Uses Persistent Cloud Computers to Keep AI Agents Working

SpaceXAI’s Grok Bot launched in beta Aug. 11, 2026, with a cloud-based setup that lets AI agents continue working after a user closes a laptop.

The system gives users Bots that can sign into tools, operate across applications and websites, save demonstrated workflows as routines and return for approval when authorization is required. Multiple Bots can work in parallel, exchange context and coordinate through shared threads or group chats.

Each user receives one persistent Firecracker microVM in the United States. Bots under the same user account share that computer, its files and browser sessions, making the environment a common workspace rather than separate computing environments for each Bot.

Desktop and mobile applications serve as thin clients for conversations, reviews and approvals. The work itself runs on the hosted computer through Cursor servers.

Lee Robinson, a SpaceXAI team member, outlined four design choices for the system: a minimal user interface, a lightweight client paired with a more capable server-side harness, a persistent cloud computer, and browser automation combined with code execution.

“The best UI is none at all,” Robinson wrote Aug. 17, 2026.

Grok Bot’s controls include Auto Review, which can request approval for potentially risky actions. Team and enterprise administrators can add approval requirements and network restrictions. OAuth tokens for connected apps remain with the relevant app backends, while the Bot receives the resulting tool data.

Initial access was listed for SuperGrok, SuperGrok Plus, SuperGrok Heavy, Cursor Pro, Pro+, Ultra, and Cursor Teams Standard and Premium subscribers. Cursor selects the model used for Grok Bot tasks, but the exact model used for each task is not publicly identified.

The setup extends Grok Bot’s routine-service functions, including service sign-ups, merchant contact and scheduling. Those tasks add outside-party interactions to the Bot’s ability to work with files, browsers and connected tools on a user’s behalf.

Because multiple Bots under one account share the same persistent environment, the account’s permissions, connected-tool policies and approval settings govern their access to the workspace.