Grok Bot

The documentation describes no export of a Bot (profile, memory, routines, conversation) and no import into any runtime Cursor does not operate; Grok Bot runs only on Cursor-hosted cloud computers. Template sharing produces a link that can only be added to another Grok Bot account.

• Grok Bot security
• Create and manage Bots
• Grok Bot security FAQ

No agent export exists; memory, conversation history, routines, skills, the cloud computer's disk and connector OAuth tokens (kept on Cursor's backend) all remain with the provider. Individual result files can be saved from cards, and Bot duplication/templates omit conversation history and learned memory.

• Create and manage Bots
• Files and results
• Grok Bot security
• Use the computer and apps

Grok Bot requires a Cursor account and plan, runs only on Cursor-hosted computers with Cursor-managed models, and the Terms of Service let Anysphere suspend or discontinue access at any time without notice.

• Grok Bot security
• Get started
• Cursor Terms of Service

Cursor manages model selection; there is no customer-facing model picker and the serving mix can change without a guaranteed vendor set. Owners cannot select any model, local or otherwise.

• Grok Bot security
• Settings and notifications
• Grok Bot security FAQ

Agent state lives in Cursor's cloud; the Terms of Service allow suspension or termination without notice and deletion of the account and its information on payment failure, and advise users to keep their own copies. No post-termination export window or shutdown plan is published; the DPA's 30-day delete-or-return clause covers personal data on written request, not the agent.

• Cursor Terms of Service
• Cursor Data Processing Agreement

Bot memory, conversation history, routines and settings are held on Cursor's backend and reached only through the Grok Bot apps; no storage format or schema is published. Files in /workspace are readable through the Cursor-hosted computer's terminal.

• Create and manage Bots
• Use the computer and apps
• Grok Bot security

The documentation offers no view of the assembled model context (base prompt, injected untrusted-content markers, reviewer inputs), and provider-controlled switches such as gradual feature rollouts cannot be determined by the owner. Model identity is visible only after the fact in usage analytics; enabled plugin tools are listed.

• Grok Bot security
• Settings and notifications
• Skills and routines

The privacy policy states personal data is kept 'as long as necessary' for business needs without bounded periods, backend retention for deleted Bots 'follows the applicable Cursor terms', and flagged content may be stored by model providers for investigation. No item-by-item view of provider-held data is documented.

• Cursor Privacy Policy
• Create and manage Bots
• Cursor Data Use & Privacy Overview

No paid placement or sponsored tools are documented, and the Marketplace presents first-party-listed plugins. The absence of self-preferencing is not backed by source or a binding commitment, and Cursor-chosen models and defaults cannot be replaced.

• Use the computer and apps
• Skills and routines
• Grok Bot security

For a Pro account the record is the conversation transcript plus routine run history, which keeps only the 20 most recent runs per routine; Action Recording (90-day internal store) is Enterprise-only and off by default. No mechanism is documented that tells the owner when an action goes unrecorded, and provider-side actions (content removal, disabling actions, computer recreation) are not described as recorded for the owner.

• Skills and routines
• Message and collaborate
• Grok Bot security
• Grok Bot Terms

No integrity data, hash chaining, signatures or verifier for the action record is documented.

• Grok Bot security
• Grok Bot for teams and enterprises

The transcript is stored on Cursor's backend, outside the cloud computer the Bot's tools operate on, but no protection of the record is documented. Bots can create, edit and delete routines (automation writes), and deleting a routine is immediate with no undo; these writes are gated only by model-based Auto Review.

• Skills and routines
• Grok Bot security

Grok Bot is proprietary: the Terms of Service forbid reverse engineering and derivative works, and the hosted computer and backend are closed Cursor services.

• Cursor Terms of Service
• Grok Bot security

A Bot has no identity of its own; it acts as the signed-in member through a Cursor account and the member's browser sessions, all of which the provider can revoke.

• Grok Bot security
• Grok Bot security FAQ

No change log or version history of Bot descriptions, memory, skills, settings or model is documented. Reset restores the cloud computer from the last saved snapshot but shows no diff or attribution and does not cover backend state.

• Settings and notifications
• Use the computer and apps
• Grok Bot security

The owner can edit each Bot's name and description, write and edit private skills, and edit routine instructions. The provider's base instructions and Auto Review policy are not exposed and cannot be replaced.

• Create and manage Bots
• Skills and routines
• Settings and notifications

Bots retain preferences, facts and summaries across sessions, but no UI to list, edit or delete memory items is documented; correction is by telling the Bot in chat. Duplication and account deletion are the only documented bulk operations.

• Create and manage Bots
• Grok Bot FAQ
• Team Bots

Owners can install Marketplace plugins, add custom MCP servers (remote HTTPS or command) and enable or disable individual plugin tools without review. The built-in shell, browser and computer-use capabilities have no documented removal setting.

• Use the computer and apps
• Settings and notifications
• Team Bots

Owners can set Auto-review rules and local-execution policy. Other provider-imposed protections have no owner override: the cloud VM sandbox, the takeover requirement for passwords, CAPTCHAs and payments, and write-only secret handling.

• Approvals, security, and privacy
• Grok Bot security
• Store secrets securely

Cursor manages model selection and the serving mix can change over time without notice; stale computer images are recreated on the fresh image; the Terms of Service let Anysphere modify the service at any time without notice, and Grok Bot Terms updates that are not materially adverse take effect on posting.

• Grok Bot security
• Cursor Terms of Service
• Grok Bot Terms

For a Pro account, network egress controls are Enterprise-only (default allow-all), there are no per-recipient contact limits, and scoping relies mainly on Auto-review rules evaluated by a model, which the docs say does not review memory writes or most settings changes. Per-plugin tool toggles and local-execution policy exist. Spend was treated as met (G11) because payment steps are handed to the owner.

• Grok Bot security
• Grok Bot security FAQ
• Approvals, security, and privacy
• Settings and notifications

Owners can write 'Ask first' Auto-review rules and use per-command approval for local execution, but whether an action matches a rule is decided by a review model. The agent changing its own settings is graded in C1.

• Approvals, security, and privacy
• Grok Bot security

The documented stop is a direct 'Stop now' chat message to one Bot; routines must be paused separately per Bot, and closing the app does not stop cloud work. No single control halting all Bots, routines and background work is documented; the organization-wide computer terminate is Enterprise admin only.

• Message and collaborate
• Skills and routines
• Troubleshooting
• Manage Grok Bot computers

Content is sent to model providers that Cursor selects and can change, not destinations the owner chooses. Usage data is collected with no documented off switch, flagged inputs may be analysed to improve enforcement, and model providers may store flagged data. The Privacy Policy changes take effect on posting without specific consent. Privacy Mode (no training) is documented as on by default only for Enterprise teams, although the Terms of Service state content is not used for training without explicit agreement.

• Cursor Data Use & Privacy Overview
• Cursor Privacy Policy
• Cursor Terms of Service
• Cursor Privacy and Data Governance
• Grok Bot security

Installed plugins are listed and can be uninstalled, and Bot secrets are listed by name with Remove/Replace. Browser sessions and command-line credentials on the shared computer are not itemised, connector tokens are held on Cursor's backend, and deletion of the provider-side token copy on uninstall is not documented.

• Grok Bot security
• Approvals, security, and privacy
• Store secrets securely
• Settings and notifications

Whole-agent deletion requires cancelling any subscription and then deleting the entire Cursor account (deleting a Bot leaves computer files and sessions); the help page states all data is removed within 30 days, but completion confirmation and the reach into daily backups and model-provider flagged data are not documented.

• Delete your Grok Bot account
• Create and manage Bots
• Grok Bot security
• Cursor Data Use & Privacy Overview