Do Grok Bots share one computer

Official Grok Bot overview and FAQ answer yes. Every Bot on your account uses one persistent cloud computer. They share its files, browser sessions, and app logins so they can hand work off. The computer is assigned per user, not per Bot.

What is shared

Docs list these as shared across Bots on the account:

1. Filesystem. Files a Bot writes are available to your other Bots.
2. Browser sessions and logins. A site you sign into from the computer stays signed in for other Bots that open the same browser state.
3. Handoffs. Group messages and direct handoffs can move context without rebuilding logins.

Each Bot still keeps its own conversation, role context, and working memory. FAQ: conversation and learned role stay separate, while shared files, sessions, group messages, and handoffs can move context between Bots.

Parallel work on one machine

Several Bots can work at the same time. FAQ: each Bot gets its own screen on the shared computer. One Bot can run one computer-use task on its screen at a time. Connectors, files, and coordination can still run in parallel across Bots.

Closing the desktop app, laptop, or phone does not stop background turns or routines — work stays on the cloud computer.

Security boundary

FAQ states plainly: Do not use separate Bots as a security boundary. Treat a login or file placed on the computer as available to all of your Bots. Put standing limits in each Bot’s description and use Auto-review Require Approval rules for sends, publishes, deletes, purchases, or production changes. Approvals, security, and privacy docs cover the full boundary and Cursor data settings.

Deleting a Bot removes that Bot’s active profile, conversation, and routines. Because Bots share a computer, files and logins on that computer may remain.

Pitfalls

• Creating a second Bot does not create a second computer or a separate login vault.
• Hiding a Bot from the sidebar does not isolate its prior files or sessions on the shared computer.
• For important decisions, ask the Bot to check the current source; memory alone does not replace a live source.