Learn
Customer Support & Success
Shared computer security for beginners
Bots on one account share one cloud computer: files, browser logins, and many credentials. Screens are separate work surfaces, not separate vaults.
One computer, many bots
Official docs assign the computer to your user account. Every Bot on that account uses it. Between different people, isolation is strict. Inside your account, it is not.
A second Bot is not a second computer. Do not use separate Bots as a security boundary, and do not put Client A’s secrets where Client B’s bot can reach them.
On that shared computer:
- Browser cookies and signed-in sessions are shared
- Files are visible to every Bot, including the workspace
- Command-line credentials are shared
- Installed connectors are account-wide
A file on that computer opens in the computer's default app. Why your bot opened that file in a strange app.
Prefer connectors and approvals over pasting passwords into chat. The Mac or Windows computer in front of you is a separate permission. The first local-command prompt applies to Grok Bot and the Bots on the account, not to one chat.
It can also be switched off. When your bot's job needs a computer that's switched off.
See also Approvals, security & privacy.
Screens are not vaults
Each Bot gets its own screen, so several Bots can use the desktop at once. One Bot runs one computer-use task on its screen at a time. The screens do not split files, cookies, or saved logins.
A Bot you just added lands here
Adding a template copies a recipe onto your account. It does not bring the other person’s computer, and it does not give the new Bot a private one. The new Bot can see what is already signed in. Read what a template copies and your first hour after you add a Bot.
A share link is not the computer
A public link lets someone copy configuration. It does not share your computer or your logins. Still strip secrets, customer data, and internal URLs before you share. An old link is not a promise the preview still matches what you remember. See when a share link is stale.
Cleaning up does not follow one Bot
Deleting a Bot removes that Bot’s profile, conversation, and routines. Files and browser sessions on the shared computer can remain. Sign out of a site when that login should stop. Remove sensitive files from the workspace. Revoke a connector in the source service when you no longer want it. Hiding a Bot does not sign those sessions out.
Next
Sources
Fetched 2026-09-23 CT.
Official computer and apps
https://docs.x.ai/grok-bot/computer-and-apps
Fetched 2026-09-23 CT.
One computer per account; screens are not a security boundary
Approvals, security, and privacy
https://docs.x.ai/grok-bot/approvals-security-and-privacy
Fetched 2026-09-23 CT.
Do not use separate Bots as a security boundary
Official FAQ
https://docs.x.ai/grok-bot/faq
Fetched 2026-09-23 CT.
Computer is assigned per user, not per Bot
Create and manage Bots
https://docs.x.ai/grok-bot/bots
Fetched 2026-09-23 CT.
A share copies configuration, not the computer
Start from a template
People share Grok Bots you can add and then change to fit your job. Each template opens on x.ai. bot.ski never installs anything.
Comments
Comments are from bot.ski members. They aren't reviewed by xAI.