Fix problems
Grok Bot's shared computer: why every Bot sees every login
By Tal Slavin · Last checked · Next review 2026-11-20
Grok Bot's shared computer: why every Bot sees every login
Every Bot shares one cloud computer and its logins: what that means for security, why sessions disappear, the Secure Form issue, and how to start fresh.
◈Key Takeaways (5)
- •One account has one persistent cloud computer; every Bot shares its browser, files, terminal and signed-in sessions.
- •Conversations, memory and routines belong to each Bot; files, installed packages and logins are shared.
- •Type sensitive passwords yourself on the Bot's screen; one user reported a Secure Form password in a page snapshot on October 5.
- •Sessions can disappear after a Reset or a browser profile reset, so expect to sign in again.
- •To start fresh, Duplicate a Bot or create a new one.
☰On this page (6 sections)
All of your Bots run on one persistent cloud computer. Conversations, memory and routines belong to each Bot. Files, installed packages and browser logins belong to the computer, so a login made for one Bot is available to every Bot on the account. Treat Bot names as roles, not as security boundaries.
What is shared and what is not#
| Item | Scope |
|---|---|
| Browser sessions and logins | Shared by every Bot |
| Files and installed packages | Shared |
| Command-line credentials | Shared |
| Conversations, memory, routines | Per Bot |
| Connector (plugin) tokens | Stay on Cursor's backend, not on the computer |
Prefer plugins to browser logins where one exists, because plugin tokens are kept off the shared computer. For why this matters for risk, see Is Grok Bot safe?.
The Secure Form password issue#
On October 5, 2026 a user reported that a password filled by the in-chat Secure Form appeared unmasked in the browser snapshot the Bot took before signing in. A Cursor staff member said the same day that a fix was in progress. We found no release note confirming a fix as of October 29, so treat it as open. Until it is confirmed fixed:
- Choose Open the screen (Take control).
- Type the password, and any two-factor code or CAPTCHA, yourself.
- Press Sign in yourself, then choose I'm done and tell the Bot to continue.
Never paste a password or one-time code into ordinary chat.
Why logins disappear#
Sites expire sessions on their own, some Chrome profiles on the shared computer have reset in community reports, and a Reset restores the last saved snapshot, which can drop recent sessions. Recover and Update Bot's Computer keep durable files and logins, but they can remove installed apps and packages. After any of these, sign in again where needed. Keep important secrets in Vault or a secure secret card, not in files or shell profiles.
Start fresh#
- Duplicate a Bot: keeps profile, settings, enabled skills, routines and avatar; not conversation history, learned memory or attachments.
- New Bot: a clean role with nothing carried over.
- Clear shared state: sign out of sites, remove sensitive files from
/workspace, revoke plugins you no longer use, and as a last step Reset the computer after saving anything you need. Deleting a Bot does not remove computer files or browser sessions.
There is no Compact or clear-context button; start a new chat to drop long history.
Frequently asked questions#
Do my Bots have separate computers?#
No. One cloud computer per account is shared by every Bot, with its browser, files, terminal and signed-in sessions. Isolation is per user, not per Bot.
Is the Secure Form password issue fixed?#
We could not confirm a fix. A user reported on October 5 that a Secure Form password appeared in a page snapshot, and staff said a fix was in progress. Type sensitive passwords yourself on the Bot's screen.
How do I start fresh?#
Duplicate a Bot to keep its profile, settings, skills, routines and avatar without history, learned memory or attachments, or make a new Bot. A computer Reset restores the last snapshot and can lose recent sessions.