Grok Bot · Persistent personal agent
Product and access
Standalone bot service from the Grok ecosystem. Bots have separate roles and contexts but use the same persistent cloud computer for the account.
Core features
8 features from provider sources · sources reviewed on 30 September 2026. Availability and limitations are listed directly below.
Shared cloud computer
Bots on one account work on the same cloud computer with browser, file system, and terminal.
Source 4Long-term bot context
Retains role, preferences, files, and browser sessions for later tasks.
Source 1Use apps and websites
Uses available connectors or works through the browser with other websites.
Source 1Collaboration between multiple bots
Bots can work in parallel, exchange messages, and hand off tasks.
Source 1Demonstrate and save workflows
Can save a demonstrated workflow as a reusable skill and run it again on a schedule.
Source 1Chat, dictation, and voice
Accepts text, files, dictation, and voice conversations in desktop and mobile apps.
Source 3Approvals in the conversation
Shows activity and drafts in the conversation and pauses for approval before sending.
Source 1
Requirements and limits
‘Still open’ means the reviewed sources do not answer this point clearly.
Requirement
Eligible subscription required
Access requires a paid individual Cursor plan, Cursor Teams, or a linked individual SuperGrok subscription.
Source 5Requirement
Cloud storage must be enabled
Grok Bot requires cloud data storage and does not start when Legacy Privacy Mode is enabled.
Source 5Limitation
Websites may require human steps
Signing in, CAPTCHAs, or other human confirmation may require you to take over; automation should not bypass such barriers.
Source 4Limitation
Bots share the account computer
All bots on an account use the same persistent computer, including files and browser sessions. Separate bots therefore do not form a security boundary.
Source 4
Practical tasks
Editorial examples based on documented features. No product tests performed.
Recurring expense reconciliation
- Your input
- Give the bot a sample invoice, the approved storage location, and assignment rules.
- Possible result
- A saved process that organizes new receipts and flags ambiguities for review.
- What to check
- Compare booking data with the original receipts; explicitly approve changes or sending.
Parallel event research
- Your input
- Ask two named bots to research venues by capacity, accessibility, and price.
- Possible result
- Two parallel research tasks and a consolidated shortlist in the shared conversation.
- What to check
- Check availability, sources, and overlaps before contacting a venue.
Gather material on a topic and combine it into a working document.
Your possible prompt
Compare three providers for [task]. Use their official documentation. Show differences, sources, and open questions in a table.
Getting-started idea based on documented capabilities. Not an executed product test. Adapt the task, data, and permissions.
What you should know first
Features and platforms according to current official documentation. Account requirements and included usage depend on the linked Cursor or SuperGrok plan.
Requirements & limitations
Provider features and availability may change. Review results and limit access to what the task requires.
Setup
Set bot access, task, and permissions.
Pricing model
Check the provider plan. Check current terms and included quotas with the provider.
The classification indicates the scope of effort. It is not a price or performance commitment.
Sources from the provider
Editorial team: Michael Meierhoff · sources reviewed on . Provider information is not independent evidence of performance.
-
docs.x.ai /grok-bot/overview
-
x.ai /bot/guides/grok-bot-101
-
docs.x.ai /grok-bot/chat-and-collaboration
-
docs.x.ai /grok-bot/faq
-
docs.x.ai /grok-bot/get-started