Frequently asked questions

Bots can use a persistent cloud computer, connected tools, websites, and files to complete work—not only answer questions. They can continue in the background, keep role-specific context, and coordinate with other Bots.

Use the Grok Bot desktop app on macOS or Windows, or the companion app on iOS. The same Bots and conversations sync across your signed-in devices.

Yes. Bot work runs on the cloud computer. Closing the app, laptop, or iPhone does not stop a background turn or routine.

Yes. Every Bot on your account uses one persistent cloud computer. They share its files, browser sessions, and logins so they can hand work off.

The computer is assigned per user, not per Bot. Do not use separate Bots as a security boundary.

Yes. Bots can reason, use connectors, work with files, and coordinate in parallel. Each Bot gets its own screen on the shared computer. One Bot can run one computer-use task on its screen at a time.

A Bot can retain stable preferences, role context, and summaries of prior work. Its conversation and learned role are separate from other Bots, while shared files, browser sessions, group messages, and direct handoffs can move context between them.

For important decisions, ask the Bot to check the current source rather than relying on memory.

Grok Bot can use many browser-based tools, including services without a dedicated connector. A site may still block automation, require a new login, present a CAPTCHA, or require human confirmation. The Bot should hand those steps to you rather than bypassing them.

Use a connector when one is available for a more structured and reliable integration.

The answer depends on the tool, the risk of the action, and—when enforcement is enabled—your Auto-review rules. Sensitive or consequential actions can stop for approval. Passwords, two-factor codes, CAPTCHAs, and similar human-only steps use a computer takeover.

Put standing boundaries in each Bot's description and add narrow Require Approval rules for actions such as sending, publishing, deleting, purchasing, or changing production systems.

Grok Bot uses Cursor authentication and account data settings. Training opt-out follows the applicable Cursor account and privacy settings.

Grok Bot requires cloud data storage, so Legacy Privacy Mode is not supported. All of your Bots can access the same cloud computer assigned to your account. See Approvals, security, and privacy for the full boundary and links to current Cursor security information.

Availability and billing depend on the account and plan. Eligible plans include SuperGrok Heavy, Cursor Ultra, and Cursor Teams Premium. Grok Bot subscriptions include weekly usage; eligible accounts can add on-demand usage billed from model and token cost. Review the current access page or Cursor pricing for current terms. Enterprise customers should contact their Cursor account team.

Team and enterprise access is rolling out. Availability and required plans can vary by organization. Contact your Cursor account team for current access and supported administrative controls.

• macOS on Apple silicon and Intel
• Windows on x64 and Arm64
• iPhone on iOS 18 or later

Linux desktop, Android, and iPad are not supported at initial launch.

A skill describes how to perform a task. A routine assigns a workflow to one Bot and tells it when to run—on a schedule or, where supported, after an event.

Test the skill on a real one-time task before turning it into a routine.

When Teach a task is available, record one browser workflow from the computer view. The Bot turns the demonstration into a draft skill that you can review and test. The rollout may be gradual, and the recording is limited to ten minutes.

Deletion removes the Bot's active profile, conversation, and routines from Grok Bot. Because Bots share a computer, files and logins on that computer may remain. Backend retention follows the applicable Cursor terms. Hide the Bot instead if you may need its work later.