Grok Bot is SpaceXAI’s beta product for delegating real, multi-step work to persistent AI teammates. This page covers the documented workflow, access boundaries, and the checks we would use before trusting a Bot with business systems. We did not run an independent test or reproduce the vendor’s case studies.
What Grok Bot actually is
SpaceXAI describes Grok Bot as an always-on agent with its own cloud computer. A Bot can sign in to the tools, apps, inboxes, and websites a user authorizes, continue a task while the user is away, and return when it needs a decision. Multiple Bots can work in parallel, hand work to one another, and share context in a thread. The product is therefore closer to a delegated operations teammate than to a chat window or a prompt library.
The official launch describes workflows such as CRM updates, invoice processing, bug reproduction, sales research, and follow-up drafting. It also says users can demonstrate a workflow once and have a Bot remember the routine. Those examples are provider demonstrations and should not be read as a reliability guarantee. Grok Bot is in beta, and its usage meter is separate from ordinary Grok and Cursor allowances.
Best fit and not fit
Best fit: operations, sales, support, recruiting, and engineering teams with repetitive browser-based work, disposable accounts, clear approval checkpoints, and logs that can be reviewed.
Not fit yet: regulated decisions, production credentials, sensitive customer data, irreversible purchases, or unattended actions where a mistaken retry could create material harm. A cloud computer may reach more data than a clean API integration, so the permission boundary must be explicit.
Our editorial decision rule
Choose Grok Bot when the work is multi-step, repetitive, and reversible, and when a human can approve external actions. Choose a conventional assistant or a controlled workflow engine when the job is a one-off answer, a compliance-sensitive decision, or an action that cannot be rolled back. Start with read-only investigation, allow one connector at a time, require approval for messages, refunds, purchases, and code changes, and compare total review time with the existing process.
Evidence, limits, and setup checks
SpaceXAI’s official Grok Bot announcement supports the product description, beta status, plan availability, and intended workflow. The later customer-support case study contains vendor-reported cost and volume claims; we do not present those as independent benchmarks. Before adoption, verify current plan access, connector scope, retention, audit logs, enterprise terms, cancellation behavior, and regional availability. Review the Grok profile, compare ChatGPT vs Grok, and follow the AI privacy checklist. Our judgment is an editorial synthesis of official sources, not a first-hand user-experience claim.
September 28, 2026: Team Bots make Grok Bot shareable across a team
xAI announced Team Bots as a public beta for Teams and Enterprise plans. A group can build a bot around a shared role or process, provide context such as files and instructions, connect plugins, and add API credentials where a plugin is unavailable. Team members can share the bot’s expertise and also invite it into Slack. xAI says individual conversations and memories remain separate for each user even though the bot’s shared skills and context are common. That distinction is important: “shared bot” does not necessarily mean a shared transcript, but administrators still need to verify exactly which files, connectors, and credentials are visible to the bot and who can change them.
Best fit, limits, and a safe pilot
Team Bots may suit sales, support, engineering, or analytics groups that repeatedly answer questions from the same approved knowledge base. It is less suitable as an unreviewed interface to broad financial, HR, customer, or production systems. xAI’s launch examples—including bots querying data and updating dashboards—are company-described use cases, not proof that every integration is accurate or safe. Begin with read-only data, a narrow group, and one measurable workflow. Assign an owner, list allowed sources and actions, test whether one user’s corrections affect the shared bot, and require approval for writes, external messages, or commitments. Revoke unused credentials and monitor changes to the bot’s shared instructions.
Our editorial view and evidence
The useful product change is the combination of reusable team context with user-specific interactions; the main adoption question is governance, not model novelty. Primary source: xAI’s Team Bots announcement. Compare this with Manus for broader task automation and Cursor for engineering-team agents. xAI’s internal productivity examples are company claims, not independent outcome evidence. AI Tools Manual did not access the beta, test permissions, or audit memory isolation; confirm beta eligibility, data handling, credential scope, and admin controls before approval.
September 28, 2026: Grok Bot adds Team Bots
SpaceXAI announced Team Bots as a public beta for Teams and Enterprise plans. A Team Bot is configured once with a job, files, skills, and connected tools, then shared with teammates so they can work from common Bot configuration and team memory. SpaceXAI describes integrations through plugins such as Salesforce, Notion, and GitHub, plus Slack access and credentials for third-party APIs. The documentation distinguishes shared Bot context from each member’s private conversation. These are vendor-documented behaviors; organizations should verify the actual workspace controls and connected-app permissions before adding internal data.
What changes for teams
Team Bots are a meaningful step beyond sharing a prompt or a personal assistant: the Bot can carry a role-specific skill set and team memory across users, appear in Slack, and coordinate work across tools. SpaceXAI’s examples include morning account briefings, bug triage and ticket creation, marketing review, and read-only data analysis. The examples illustrate intended workflows; they are not independent case studies or guarantees of outcome. The official documentation says the team owner maintains the shared configuration, while teammates’ chats remain separate. It also says a plugin action uses the account of the person interacting with the Bot rather than lending another person’s access.
Governance questions before rollout
Shared memory can improve consistency, but a correction or fact saved to team memory may influence later users. Agree on what belongs in team memory, who can change Bot skills and credentials, what can be posted to Slack, and which actions require human approval. Begin with read-only or low-risk connectors, use a dedicated Bot for one bounded process, and keep customer messages, production changes, financial actions, and data exports behind explicit review. The vendor announcement does not establish a neutral security audit or the suitability of every connector for regulated data.
Our decision rule
Try a Team Bot when a stable, repeated team job needs shared instructions and cross-user consistency. Prefer a personal Bot for an individual’s private context; do not mix private and team knowledge just to make a Bot appear more capable. Measure correction rate, escalation frequency, unauthorized actions, and time saved during a limited pilot before expanding the roster. See our human-review-loop guide and the Grok vs. Gemini comparison for broader agent-selection context.
Evidence disclosure — verify before approval
Primary sources: SpaceXAI’s Team Bots announcement, Team Bots documentation, and Grok Bot overview. AI Tools Manual did not access a Teams or Enterprise tenant or independently test isolation, memory, permissions, Slack behavior, or security. Treat availability as beta and verify plan eligibility before rollout.
October 12–14, 2026: Grok Bot joins X Subscription and Grok Voice 3.0
SpaceXAI’s X Subscription announcement includes Grok Bot, Grok, Cursor and X. The official plan table lists Free at $0, Plus at $8/month, Premium at $30/month, Super at $100/month and Ultra at $200/month. Paid plans share Grok-model usage across Grok apps, X and Cursor; included usage is listed as 4x, 15x and 50x the Plus allowance for Premium, Super and Ultra. API usage is billed separately through top-ups at API list prices. Confirm country, eligibility, tax and current account entitlements before comparing costs. This is a pricing/access change, not evidence that all Grok Bot functions are available identically at every level. Check the official plan announcement before comparing total cost.
The company also says Grok Voice 3.0 powers Grok Bot’s voice mode. Separately, the Voice Agent API is listed at $0.08/minute, with `grok-voice-latest` switched automatically. Consumer-plan use and API minutes should not be conflated. See the official Voice 3.0 announcement.
This may make Grok Bot more convenient for users already in X, but buyers should first confirm whether bot access is included in their country and tier, how shared usage is measured, and which actions need confirmation. We have not tested Grok Bot or its voice workflows; we cannot independently verify vendor claims about quality, latency or enterprise outcomes. Compare this teammate-style product with Manus and Perplexity Computer. Next review: November 16, 2026.
Human review required: validate plan pricing and entitlements, shared-usage rules, rollout scope, Bot action permissions and any separate API charges before publication.
October 22, 2026: Grok Bot adds Pages, video, and new connected actions
The official Grok Bot changelog’s v0.75.2 entry groups several releases under “Pages, new chat cards, and video creation.” Bots can create editable reports, memos, and dashboards, or keep a Page updated; they can also make videos from a text description or shared image. The Library now supports pinned pages, files, and links, and the dashboard lists Pages users have shared. These capabilities bring Grok Bot closer to a persistent work surface rather than a chat-only assistant.
Permissions and transactions need human review
The release also describes Shop Pay checkout and one-time Shop cards, an X Money connection, Gmail draft/send and reply actions, Calendar event changes, and an enterprise-admin option to permanently delete a member’s Bot data. The changelog notes visibility indicators and controls to unshare or delete Pages, but teams still need to inspect the actual sharing state, connector scopes, purchase confirmations, and admin audit trail in their own workspace.
Editorial assessment: Pages and video creation may help users who need a deliverable that evolves over time; connected email, calendar, and payment actions carry a different risk profile. Start with a test Bot and non-sensitive content, restrict connectors to the minimum scope, require confirmation for external messages or purchases, and check what persists after deletion. We did not test these features, privacy controls, or payment flows.
Primary source: Grok Bot changelog. Related: our agent human-review guide. Next review: November 23, 2026. Human review: verify Page defaults, connector permissions, data-deletion scope, plan availability, and payment consent before approval.
October 23, 2026: Grok Bot adds Vault and email actions
The official Grok Bot changelog lists version 0.75.5 on October 23. It adds a Vault for logins, payment cards, and contact information; bots can forward messages from their own inbox while preserving formatting, images, and attachments. The same release records who requested each Slack message and adjusts the approval flow: Auto-review asks less often when an action was explicitly requested, and after a user denies an approval, the Bot should stop rather than retrying that action. Email and Slack messages may be sent once Auto-review allows them; routine turns otherwise remain drafts.
Why this changes the decision: Grok Bot is moving from a persistent task assistant toward an agent that can retain sensitive account data and take consequential communication or checkout actions. That is useful for repeat work, but it raises the cost of a mistaken instruction, compromised session, or over-broad permission. The changelog does not explain encryption, retention, administrator visibility, or recovery controls for every Vault item; do not infer those protections from the feature name.
Best fit, limits, and a safe pilot
This is most relevant to technically confident users who want a Bot to handle bounded email, Slack, or checkout tasks and can review each connected account. It is not a good first choice for regulated data, shared payment credentials, or unattended high-value purchases until the organization verifies its own policy and the product’s current controls. This update is based on the vendor changelog; we have not tested Vault, the approval flow, or payment handling.
- Begin with a dedicated inbox or low-privilege account, not an administrator mailbox.
- Store only credentials needed for a named task; avoid reusable payment methods until control and revocation behavior are confirmed.
- Keep approval prompts enabled for external sends and purchases; test deny, stop, and audit behavior with a harmless action.
- Review who can see the Vault, how items are removed, and what remains in logs before connecting work accounts.
Our assessment: the reduced friction is attractive, but the safety posture now matters as much as task quality. We would treat Vault as a sensitive credential manager and would not enable autonomous spending or broad email access by default. Compare this with our Grok assistant profile before deciding whether a persistent Bot is appropriate.
Primary source: Grok Bot official changelog, October 23, 2026. Next review: November 24, 2026.
nn
What the October 27 Shared Bots announcement adds
xAI’s October 27 account describes Shared Bots used by its sales organization for three stages of a deal: Account Intel for prospect research and Salesforce updates, Quote Bot for proposals and order forms, and Deal Bot for non-standard terms and approvals. The company says a team can maintain shared skills and connections to internal sources of truth, while each representative interacts with the shared agent under that person’s permissions. Account Intel can use Salesforce activity and Gong transcripts, and scheduled workflows can prepare briefings or draft follow-up messages.
The announcement is an implementation case study, not evidence that the same integrations, controls, or outcomes are available to every Grok Bot customer. xAI describes Quote Bot previewing proposed Salesforce changes and requesting confirmation, while Deal Bot has separate permissions for Deal Desk work. It also says human review remains required when decision criteria are unclear or when a Bot prepares customer-facing communications.
Fit, limits, and rollout safeguards
Shared Bots may be useful for teams with repeated workflows, documented business rules, and an owner for each connected data source. They are not a safe shortcut for granting broad CRM, contract, or call-transcript access. Before a pilot, map data permissions to job roles, restrict write actions, require confirmation for changes to pricing or customer records, log decisions, and test with non-customer data. Keep discounts, legal terms, and outbound messages with a named human approver.
Our assessment is that the new value is team-level reuse and governed handoffs, not simply more autonomous actions. Teams should compare the permissions actually available in their account with xAI’s described internal implementation. Related context: Perplexity Computer’s enterprise connector controls. Next review: November 11, 2026.
Evidence note: Capabilities above are attributed to xAI’s published account. AI Tools Manual did not test Grok Bot or independently inspect its connected systems.