Repeatable operations
Preparing recurring reconciliations, reports, checklists, triage queues, and review-ready updates across several systems.
Independent tool overview
Grok Bot at a glance
Grok Bot is SpaceXAI's beta product for creating persistent AI teammates that work through apps, websites, files, inboxes, browser sessions, and terminal tasks on a shared cloud computer. Bots can retain job context, collaborate in groups, learn reusable skills, and run scheduled or event-triggered routines. That makes the product more operational than a normal chatbot, but also raises the stakes: credentials, persistent sessions, unattended routines, and real external actions need least-privilege access, narrow approvals, audit evidence, and a human owner.
Visit the official Grok Bot site ↗
- Product type
- Persistent cloud-computer AI agent workspace
- Current status
- Active beta
- Launched
- August 11, 2026
- Core interface
- Message threads with Bots and groups
- Execution
- Shared cloud computer with browser and terminal
- Automation
- Reusable skills plus scheduled or event-triggered routines
- Routine limit
- Up to 50 routines per Bot
- Run history
- 20 most recent records per routine
- Desktop support
- macOS and Windows; no Linux app documented
- Mobile support
- iOS
- Lowest listed individual access
- SuperGrok at $30/month
- Reviewed
- August 31, 2026
Overview
What Grok Bot is
SpaceXAI launched Grok Bot in beta on August 11, 2026. A Bot is a durable AI teammate with a name, a defined job, a conversation, and working context that develops over time—not simply another name for the Grok 4.6 model.
Bots work on a shared computer in the cloud with browser and terminal access. They can sign into ordinary websites and apps, use supported connectors, read and create files, keep working after the user's device disconnects, and return results in the conversation.
Users can run several specialist Bots in parallel, put them in group chats, and let Bots message one another or pass work between roles. Shared computer files and browser sessions make handoffs easier, but also mean access granted for one workflow may be reachable by another Bot unless the environment is designed carefully.
A successful process can become a reusable skill and then a scheduled or event-triggered routine. SpaceXAI recommends proving the one-time task first, testing the saved process, defining missing-data and approval behavior, and only then enabling unattended automation.
As of August 31, 2026, Grok Bot is included with SuperGrok, SuperGrok Plus, SuperGrok Heavy, Cursor Pro, Cursor Pro+, Cursor Ultra, and Cursor Teams plans. Its usage is separate from normal Grok and Cursor allowances. The product is available on macOS, Windows, and iOS; there is no Linux desktop app in the current documentation.
Use cases
Who Grok Bot is best for
The strongest fit depends on the job you need the product to complete, not the size of its feature list.
Research and drafting
Collecting source-linked evidence from websites, files, inboxes, and connected systems before producing a document, spreadsheet, presentation, or draft message.
Specialist agent teams
Giving distinct Bots narrow jobs such as research, writing, inbox preparation, expense review, or bug reproduction and coordinating them in a group.
Browser-based workflows
Completing work in products that lack a clean API or MCP integration, provided access and actions are tightly controlled.
Scheduled preparation
Running a proven workflow in the background and delivering a review queue without automatically taking the consequential final action.
Cross-device delegation
Starting or reviewing a Bot conversation from desktop or iPhone while the cloud computer continues the underlying work.
Capabilities
Core Grok Bot features
Durable Bots
Each Bot has a job, conversation, and evolving working context so recurring work does not begin from a blank prompt.
Shared cloud computer
Bots use an always-available environment with a browser, terminal, and shared workspace instead of depending on the user's open laptop.
Website and app operation
A Bot can work through normal interfaces, including services without a dedicated connector, and can ask the user to take over for passwords, passkeys, two-factor codes, or CAPTCHAs.
Persistent sessions
Browser sessions can remain signed in on the shared computer and may be used by other Bots when appropriate.
Connectors and plugins
Supported services can be connected through the plugin settings; an installed connector may still require separate browser authentication.
Multi-Bot collaboration
Bots can run in parallel, message one another, share thread context, and coordinate inside group chats.
Skills
A completed process can be saved as reusable instructions covering inputs, steps, validation, output, and approval boundaries.
Teach by demonstration
Where rollout access is available, Grok Bot can observe up to ten minutes of visible browser interaction and turn it into a draft skill for review and testing.
Routines
A Bot can run a saved workflow on a schedule or, for supported Cursor account integrations, after a narrowly defined Slack or GitHub event.
Approval controls
Users can allow or deny a proposed action, create narrow require-approval rules, and use automated review where that feature is available.
Files and artifacts
Bots accept common documents, media, data, code, and notebook formats and can return reviewable documents, spreadsheets, presentations, screenshots, logs, or drafts.
Action visibility
The transcript can show tool activity, computer use, created files, questions, and approval requests alongside messages.
X connector
The August 29 integration can search posts, read a timeline, inspect mentions, and gather current X material after the account is connected.
Process
How the Grok Bot workflow works
Step 1
Assign one accountable job
Create a Bot around a specific outcome, source set, working style, approval boundary, and owner. Avoid a vague catch-all role with broad access.
Step 2
Begin read-only
Start with research, reconciliation, classification, or drafting. Require source links and a clear list of facts, inferences, completed actions, pending approvals, and unknowns.
Step 3
Use minimum access
Prefer scoped service accounts and read-only connectors. Do not place personal admin sessions, unrestricted production credentials, or unrelated customer data on the shared computer.
Step 4
Hand off secrets securely
Take control to enter passwords, passkeys, two-factor codes, and CAPTCHAs. Do not paste reusable secrets into prompts, saved skills, screenshots, or normal conversation text.
Step 5
Define explicit stops
Require approval before sending, publishing, purchasing, transferring funds, deleting, overwriting, changing permissions, accepting terms, contacting candidates or customers, or modifying production.
Step 6
Inspect the proposed action
Before approval, verify the exact account, recipient, record, amount, file, command, current value, proposed value, and expected effect. Deny anything ambiguous.
Step 7
Treat content as untrusted
Email, Slack, documents, websites, tickets, code, and social posts can contain prompt injection. Retrieved content must never expand the Bot's authority or override standing rules.
Step 8
Prove the manual run
Correct the one-time workflow until its output is reliably reviewable, then save the process as a skill with validation, missing-source behavior, and approval boundaries.
Step 9
Test the skill again
Run the saved process on a second safe input. Confirm current sources, expected format, failure reporting, evidence, and stopping behavior before creating a routine.
Step 10
Engineer the routine
Set an owner, schedule and time zone, narrow event filter, fresh input source, step and usage budget, timeout, idempotent retries, partial-completion report, and safe stale-data policy.
Step 11
Monitor unattended work
Review the recent run history, errors, approvals, created artifacts, and source-system effects. Pause routines after site, connector, schema, policy, or source changes and re-test them.
Step 12
Revoke completely
When work ends, pause or delete routines, sign out of websites, uninstall and revoke connectors, remove sensitive workspace files, and delete or hide the Bot as appropriate. Deleting a Bot alone does not clear shared files or browser sessions.
Cost
Grok Bot pricing and free plan
Grok Bot is bundled with eligible paid Grok and Cursor subscriptions and has a separate usage allowance from the subscriber's normal Grok or Cursor usage. The lowest current individual plan explicitly listing access is SuperGrok at $30 per month. SpaceXAI does not publish a simple per-Bot or per-compute price on the reviewed pages, and allowance details can vary by plan and rollout.
Free
$0/month
The current pricing page lists general Grok features but does not list Grok Bot access on the Free tier.
- Grok chat with limits
- Connectors
- No Grok Bot entitlement shown
SuperGrok
$30/month
The lowest currently listed individual Grok plan that explicitly includes Grok Bot.
- Grok Bot access
- Grok 4.6
- Connectors
- Higher Grok limits
- Bot usage is separate from normal Grok usage
SuperGrok Plus
$100/month
Higher-usage individual Grok subscription that also includes Grok Bot.
- Everything in SuperGrok
- Significantly higher usage across listed Grok products
- Priority access
- Early feature access
Other eligible individual plans
Plan-dependent
Grok Bot is also included with SuperGrok Heavy, Cursor Pro, Cursor Pro+, and Cursor Ultra.
- Separate Bot usage allowance
- Plan limits can differ
- Check the current checkout page before subscribing
Cursor Teams
Plan-dependent
Included with Cursor Teams Standard and Premium plans.
- Team access
- Administration varies by plan
- Bot usage is separate from normal Cursor usage
Enterprise
Contact sales
The launch materials direct enterprise users to a waitlist, while current pricing materials describe custom organization plans and security options.
- Availability may depend on rollout
- Custom rate limits and infrastructure
- SSO and SCIM options
- Custom retention and other controls may require contract review
Pricing checked . Check current pricing at the source ↗
Assessment
Grok Bot strengths and limitations
Where it stands out
- Cloud execution continues after the user's computer or phone disconnects.
- The message-thread interface makes delegation more approachable than building a workflow graph first.
- Browser and terminal access extends automation to tools that lack a clean API.
- Dedicated roles and persistent context can make recurring work more consistent than one-off chat sessions.
- Multiple Bots can work in parallel and coordinate inside groups.
- Skills provide a bridge from a corrected one-time task to a documented reusable process.
- Scheduled and event-triggered routines support background work once a workflow is proven.
- Built-in approval concepts encourage a review point before consequential external actions.
- The shared workspace supports artifact handoffs among specialist Bots.
- Current documentation gives unusually concrete advice on approval boundaries, stale-data handling, idempotent retries, and source-linked results.
- Bot usage is separated from the subscriber's normal Grok or Cursor allowance.
- Access is bundled into several existing Grok and Cursor subscriptions instead of requiring a separate per-seat product at launch.
What to consider
- Grok Bot is an early beta released in August 2026; features, limits, entitlement rules, documentation, and reliability may change quickly.
- Bots can hallucinate facts, misunderstand scope, choose the wrong account or record, misread interfaces, create poor artifacts, and report incomplete work as finished.
- Prompt injection in websites, email, Slack, documents, tickets, repositories, social posts, and tool output can manipulate an agent with real credentials.
- A shared cloud computer means files and browser sessions may be accessible across Bots, expanding the consequence of an overly broad login or secret.
- Deleting a Bot does not remove shared-computer files or browser sessions; access must be revoked and data cleared separately.
- Grok Bot requires cloud data storage and is incompatible with Cursor's Legacy Privacy Mode according to the current setup guide.
- Backend retention and account deletion follow applicable Cursor terms; teams must review the current contract and settings for their data class and jurisdiction.
- An approval only controls the pending action and does not undo earlier work or side effects.
- Always-allow rules and repeated prompts can create approval fatigue or normalize risky actions that differ subtly from the original scope.
- Auto Review is described as available only in some rollouts and should not be treated as a replacement for least privilege or human review.
- Teach-by-demonstration may not be enabled for every user, records visible interaction, and can miss decision rules or failure handling that were not demonstrated.
- A test run can perform real actions, so production credentials and live records are unsafe test inputs.
- Event listeners can consume usage, act on irrelevant content, or be triggered maliciously if matching rules are broad.
- Each Bot is limited to 50 routines and the app keeps only the 20 most recent run records per routine, which may be insufficient as a compliance audit trail.
- The current official documentation does not provide a Linux desktop application.
- The reviewed pricing pages do not publish a simple per-Bot, per-hour, or per-routine allowance, so heavy-workload cost and capacity are hard to model before a real trial.
- Supported plans and limits differ across Grok, Cursor individual, Teams, and future enterprise access.
- Grok Bot should not autonomously make medical, legal, employment, financial, security, compliance, identity, or production decisions.
- Reliability depends on third-party websites, connectors, authentication, interface layouts, source freshness, cloud-computer state, and the underlying model.
- Persistent automation needs an accountable human owner, monitoring, incident response, emergency revocation, and a safe fallback—not just a saved prompt.
Compare
Grok Bot alternatives
The right alternative depends on the specific output, workflow, controls and budget your project requires.
Agents
ChatGPT Agent
Choose ChatGPT Agent when OpenAI's consumer agent environment and ChatGPT ecosystem are a better fit than a persistent multi-Bot workspace.
Explore ChatGPT Agent →Agents
Manus
Choose Manus for a general autonomous-agent product centered on completing research, analysis, and web-based deliverables.
Explore Manus →Agents
Manus Cloud Computer
Choose Manus Cloud Computer when the priority is a no-code environment for always-on agents, scrapers, and hosted workloads.
Explore Manus Cloud Computer →Agents
Claude Managed Agents
Choose Claude Managed Agents when Anthropic's managed harness, memory approach, and enterprise ecosystem better match the organization.
Explore Claude Managed Agents →Agents
Gemini Managed Agents
Choose Gemini Managed Agents when a sandboxed agent API and Google ecosystem integration matter more than a teammate-style desktop app.
Explore Gemini Managed Agents →Coding
Grok Build
Choose Grok Build when the job is specifically repository-aware software development rather than cross-app business operations.
Explore Grok Build →Questions
Grok Bot FAQs
What is Grok Bot?
Grok Bot is SpaceXAI's beta workspace for durable AI teammates that use a shared cloud computer, apps, websites, files, connectors, skills, and routines to complete multi-step work.
Is Grok Bot the same as Grok 4.6?
No. Grok 4.6 is a model. Grok Bot is an agent product that adds persistent roles, conversations, a cloud computer, collaboration, approvals, files, skills, and automation around supported models.
How much does Grok Bot cost?
As of August 31, 2026, the lowest current individual plan explicitly listing access is SuperGrok at $30 per month. It is also included in higher SuperGrok plans, eligible Cursor individual plans, and Cursor Teams plans.
Does the free Grok plan include Grok Bot?
The current SpaceXAI pricing page does not list Grok Bot under the Free plan.
Does Grok Bot use my normal Grok or Cursor allowance?
SpaceXAI says Grok Bot has its own usage, separate from existing Grok and Cursor plan usage. Exact Bot limits are plan-dependent and are not fully itemized on the reviewed public pricing pages.
Can Grok Bot work while my laptop is closed?
Yes. Cloud-computer tasks and background routines can continue while the user's device is disconnected, subject to account access, usage, authentication, and routine state.
What computers and phones support it?
The current documentation lists desktop apps for macOS and Windows plus an iOS app. It says a Linux desktop app is not currently available.
Can several Bots work together?
Yes. Users can run Bots in parallel, mention them, put them in groups, and let them message one another or share work and context.
What is the difference between a skill and a routine?
A skill is a reusable set of instructions for doing a task. A routine assigns one Bot to run a workflow on a schedule or, where supported, after an event.
How many routines can a Bot have?
The current documentation says one Bot can own up to 50 routines and the app keeps the 20 most recent run records for each routine.
Can Grok Bot log into websites?
Yes. The user can take over the cloud computer to enter passwords, passkeys, two-factor codes, or CAPTCHAs, then return control. The resulting browser session can persist on the shared computer.
Is Grok Bot safe for unattended automation?
Not by default. Start read-only, use scoped accounts, treat retrieved content as untrusted, require approvals for external effects, test failure cases, monitor routines, and keep a human owner and emergency revocation path.
Does deleting a Bot remove its data and access?
Not completely. SpaceXAI says deleting a Bot removes its active profile, conversation, and routines, but does not remove shared-computer files or browser sessions. Connectors and source-service authorization also need separate revocation.
Can Grok Bot make purchases or production changes?
It may be technically capable of consequential actions through connected tools or a browser, but those actions should always be kept behind explicit, narrowly reviewed approval and organizational policy.
Is Grok Bot ready for regulated work?
Do not assume that. Review the applicable terms, retention, data location, access controls, audit requirements, vendor agreements, and organization plan before using it with regulated or sensitive data.
Bottom line
Our Grok Bot verdict
Grok Bot is a compelling early attempt to turn AI agents into durable teammates rather than disposable chat sessions. Its shared cloud computer, specialist Bots, skills, routines, and approval model could remove meaningful coordination work for teams already invested in Grok or Cursor. The same persistence that makes it useful also makes mistakes more consequential. Use it first for source-linked preparation and drafts, isolate credentials by role, keep external side effects behind approval, test every routine, and treat shared sessions, prompt injection, retention, and revocation as first-class system-design concerns.
Visit Grok Bot website ↗Similar Agents Tools
View all Agents AI tools →
Xirp
Xirp - Spotify's vendor-neutral workspace for Claude, Gemini, and Codex coding agents
Sonic-3.6
Cartesia's natural text-to-speech model for expressive, multilingual voice generation across 44 languages.
Buzz
Buzz - open-source workspace where AI agents join team chats as coworkers
Berd
Berd - Block's open-source desktop hub for running custom AI agents
AI training for the future of work.
Get access to all our AI courses, hundreds of real-world AI use cases, live expert-led workshops, an exclusive network of AI early adopters, and more.
AI Courses
Get unlimited access to all of our current & upcoming industry-specific AI courses for the duration of your subscription.
Daily Guides
To keep up with the rapid pace of AI, our team publishes AI implementation guides daily. Our library contains 300+ practical use cases to automate real-world work.
Workshops
Join weekly, live, interactive sessions with industry leaders who are at the forefront of AI for hands-on implementation guidance and exclusive insights.
Community
Network with an exclusive community of AI-first professionals who are working smarter with AI. Learn how early adopters are using AI in their work and businesses.