Grok Bot

• Persistent cloud computer: Bots use a cloud-hosted computer with browser sessions, files, and signed-in applications. Work can continue when the desktop or mobile client is closed.
• Cross-application task execution: Bots can work in browser-based applications, inboxes, websites, and developer tools, including services that lack a dedicated integration. A Bot may stop for a user when a website requires a login, CAPTCHA, two-factor authentication, or another human-only action.
• Role-specific context: Each Bot has a defined responsibility, conversational history, and saved preferences. Bots can retain workflow context and reusable instructions for future tasks.
• Multi-Bot coordination: Users can run several Bots in parallel, create group conversations, and hand work between Bots. Bots on the same account share a cloud computer, including its files, browser sessions, and logins; separate Bots are therefore not an access-control boundary.
• Skills and routines: A completed workflow can be saved as a skill with its steps, inputs, output requirements, and approval limits. Routines can run a skill on a schedule or, where supported, after an event.
• Approval controls: Users can define actions that require approval, including sending messages, publishing content, purchases, deletions, permission changes, and production-system updates.

• Audience: Individual operators, developers, sales teams, operations teams, support teams, and organizations that need agents to perform recurring work across existing web applications.
• Use Case: Grok Bot can support research, sales outreach preparation, inbox processing, customer-support tasks, billing and operations workflows, bug reproduction, and routine browser-based work that requires multiple steps across applications.

• Client platforms: macOS, Windows, Linux, iOS, and Android.
• Execution environment: Persistent cloud computer assigned per user.
• Automation model: Conversational task delegation, reusable skills, scheduled or event-triggered routines, and parallel Bot execution.
• Security model: User-controlled sign-ins, approval gates, and account-level privacy settings. Grok Bot requires cloud data storage and does not support Legacy Privacy Mode.

Grok Bot is included with eligible SuperGrok, Cursor, and Cursor Teams subscriptions, including SuperGrok, SuperGrok Plus, SuperGrok Heavy, Cursor Pro, Cursor Pro+, Cursor Ultra, and Cursor Teams Standard or Premium. X Premium+ subscribers can also access Grok Bot through their linked SuperGrok access.

In the United States, X Premium+ web pricing starts at $40 per month or $395 per year, before applicable taxes; pricing varies by location and purchase channel.

Eligible accounts receive weekly included Grok Bot usage. Once included usage is exhausted, eligible accounts can enable on-demand use billed by model and token consumption. The public Grok Bot documentation does not publish a fixed per-token, per-action, or per-Bot on-demand rate. Broader Grok Extra Usage Credits can start at $5, but the documentation does not explicitly state that this minimum or its rates apply to Grok Bot on-demand use.