Skip to content
Grok Bot

Security

Grok Bot Security: What the Shared Computer Model Actually Means

Understand Grok Bot’s security model: the shared cloud computer, credential access, local-computer permissions, approvals, and why separate Bots are not security boundaries.

Grok Bot security is easy to misunderstand. People see a roster of Bots and assume isolation. xAI’s docs say something sharper.

1. One user, one shared Bot computer

Your account → shared cloud computer → Research Bot, Hiring Bot, Finance Bot, Chief of Staff

All Bots belonging to one user share the same persistent cloud computer, including files, browser sessions and command-line credentials. Treat a login or file on that computer as available to every Bot that user runs.

2. Separate Bots are organizational—not security—isolation

xAI explicitly says not to treat separate Bots as a security boundary. Between users, each person gets a dedicated Firecracker microVM with its own kernel, memory and virtual devices. Within one account, the computer is shared.

3. Local computer execution is separate

Access to the Mac or Windows machine in front of you is a separate capability from the cloud computer. Settings offer Ask every time, Always allow, or Never allow. The documented default is Ask every time. Use Never allow unless a Bot has a specific reason to work on local files.

4. Secrets and sensitive steps

Passwords, passkeys, two-factor codes, CAPTCHAs and payment confirmations should be completed with you taking control of the computer—or via a secure secret request for supported connections. Do not paste passwords into ordinary chat.

5. Practical configuration

  • Low risk research Bot → cloud tools only, drafts by default
  • More sensitive operations Bot → approval before sends, publishes, purchases, deletes
  • Local computer → Never allow unless genuinely required
  • Connect only the tools a workflow needs; sign out when access should end

What this means in practice

Use separate Bots for clearer jobs and memory—not for security isolation. Pair this article with Trust & cost. Do not treat this page as a blanket security guarantee; re-check xAI’s current Approvals, security, and privacy docs and Security FAQ when policies matter.