Grok Bot

Incomplete and not restorable: no export of a Bot is documented, and template links, which stay hosted by xAI, recreate only its profile, settings, skills and routines, excluding memory, history, files, computer access and logins.

• Create and manage Bots | SpaceXAI Docs
• Frequently asked questions | SpaceXAI Docs

No export is documented; memory, routines, files and sign-ins stay on the provider's cloud computer and backend, and template links carry only part of the configuration.

• Create and manage Bots | SpaceXAI Docs
• Manage Grok Bot computers | SpaceXAI Docs

Bots execute only on hosted computers in Cursor's cloud; no open-source runtime is available.

• Grok Bot for teams and enterprises | SpaceXAI Docs

Bots are tied to the user's Cursor account, and nothing lets others verify a Bot is the same agent without the provider.

• Grok Bot for teams and enterprises | SpaceXAI Docs

Bots cannot run outside the provider's service; admins and the provider can terminate computers, and access depends on a paid plan.

• Manage Grok Bot computers | SpaceXAI Docs
• Grok Bot | SpaceXAI Docs

Routines, triggers, connectors and memory depend on the hosted service and Cursor account integrations, and the provider manages model selection, so no capability survives a model swap.

• Skills and routines | SpaceXAI Docs
• Grok Bot security | SpaceXAI Docs

Files reside in /workspace on the cloud computer, but the storage format of memory, conversations and routines is not documented.

• Approvals, security, and privacy | SpaceXAI Docs

Owner-set descriptions, skills and Team Rules are visible, but the provider's system instructions and model orchestration are not published or exposed to users.

• Grok Bot for teams and enterprises | SpaceXAI Docs
• A Guide to Grok Bot | Composio

Backend data follows Cursor retention terms, action records are kept internally for 90 days, and Enterprise analytics derive conversation insights outside the owner-inspectable Bot state.

• Grok Bot security | SpaceXAI Docs
• Grok Bot for teams and enterprises | SpaceXAI Docs

Conversations show proposed operations and routines keep success and failure history. A detailed record of tool calls, shell commands and browsing can be streamed to the organization's own collector, but only on Enterprise, off by default and admin-facing.

• Skills and routines | SpaceXAI Docs
• Grok Bot for teams and enterprises | SpaceXAI Docs

Skills and routines are natural-language instructions with steps and decision rules that owners can read and edit; the agent runtime itself is not available as source.

• Skills and routines | SpaceXAI Docs

No advertising or sponsored placement in Bot context is documented, nor any explicit commitment against it.

• Approvals, security, and privacy | SpaceXAI Docs

Approvals gate actions before execution and Enterprise Action Recording captures tool calls, commands and browsing, but it is off by default and the docs do not say an action is blocked when it cannot be recorded.

• Approvals, security, and privacy | SpaceXAI Docs

Enterprise Action Recording and Audit Logs exist, but the docs do not say whether edits to or deletions from these records would be detectable.

• Grok Bot security | SpaceXAI Docs

On Enterprise, the platform records Bot actions on its backend and can stream them to the organization's own collector, outside the Bot's cloud computer. The docs do not state this as a protection, and other plans have no such record.

• Grok Bot for teams and enterprises | SpaceXAI Docs

Enterprise teams can stream recorded actions via OpenTelemetry to their own collectors and audit logs to a SIEM; individual and Teams plans have no documented log export.

• Grok Bot for teams and enterprises | SpaceXAI Docs

Bots share one cloud computer and can coordinate, but no way to match one side's record of an exchange against the other's is documented.

• Frequently asked questions | SpaceXAI Docs

The runtime is proprietary; the vendor has not published its orchestration code or reproducible builds.

• A Guide to Grok Bot | Composio
• Grok Bot | SpaceXAI Docs

The model and system configuration are provider-managed and not inspectable; only owner and team-authored rules, skills and settings are visible.

• Grok Bot security | SpaceXAI Docs

Bots act through signed-in accounts and shared static egress IPs; recipients have no documented way to verify a message came from this Bot under its owner's authority.

• Grok Bot security | SpaceXAI Docs

No documented procedure or open tool lets the owner check the integrity of the action record independently of the provider.

• Grok Bot security | SpaceXAI Docs

The docs describe no way for the owner to verify whether a Bot's memory, routines and computer state changed between two points in time.

• Manage Grok Bot computers | SpaceXAI Docs

Owners edit a Bot's name, description and routine instructions; provider system instructions are not editable, and on team plans Team Rules are non-negotiable for members.

• Create and manage Bots | SpaceXAI Docs
• Grok Bot for teams and enterprises | SpaceXAI Docs

Bots retain preferences, facts and summaries, but no interface to view, edit or delete individual memory items is documented beyond deleting the whole Bot.

• Create and manage Bots | SpaceXAI Docs

Owners can create skills in natural language, teach tasks by demonstration, and edit, pause or delete routines; the runtime logic is not modifiable.

• Skills and routines | SpaceXAI Docs

Owners can add plugins and custom remote or stdio MCP servers and set local execution to ask, always or never; per-Bot credential scoping is not available because Bots share one computer, and team MCP policy applies.

• How to Add MCP Servers to Grok Bot | Composio
• Approvals, security, and privacy | SpaceXAI Docs

Model selection is managed by the provider with no customer-facing model picker or local model option documented.

• Grok Bot security | SpaceXAI Docs

The product requires a paid Cursor or SuperGrok plan, and controls such as network allowlists, enforced Auto-review, action recording and computer management are Enterprise-only.

• Grok Bot | SpaceXAI Docs
• Grok Bot for teams and enterprises | SpaceXAI Docs

Enterprise admins can restrict network destinations to an allowlist and trust specific MCP servers, enforced by the platform. Individual owners rely on per-action approvals and cannot set in advance whom a Bot may contact.

• Grok Bot for teams and enterprises | SpaceXAI Docs

Sensitive actions are held for approval (Allow once, Deny, Always allow) before execution, with Auto-review rules that teams can enforce; local execution defaults to ask every time.

• Approvals, security, and privacy | SpaceXAI Docs
• Grok Bot for teams and enterprises | SpaceXAI Docs

Owners can send a stop message and pause routines; a hard computer termination is available only to Enterprise organization admins.

• Skills and routines | SpaceXAI Docs
• Manage Grok Bot computers | SpaceXAI Docs

All work runs on provider infrastructure, Grok Bot requires data storage and does not support Legacy Privacy Mode, and non-training depends on Cursor Privacy Mode settings rather than an explicit opt-in.

• Approvals, security, and privacy | SpaceXAI Docs
• Grok Bot security | SpaceXAI Docs

Connector OAuth tokens stay on Cursor's backend, never on the computer or with the model, and secrets are entered through masked requests; credentials remain provider-held and do not travel with the Bot.

• Grok Bot security | SpaceXAI Docs
• Approvals, security, and privacy | SpaceXAI Docs

Deleting a Bot removes its profile, conversation and routines but not shared computer files or sign-ins; backend data is deleted within 30 days after service ends, and daily encrypted backups exist.

• Create and manage Bots | SpaceXAI Docs
• Grok Bot security | SpaceXAI Docs