Grok Bot's shared computer: why every Bot sees every login, and what to do about it

Every Grok Bot on your account runs on the same cloud computer, with one browser, one file system, one terminal and one set of signed-in sessions. A Bot called Finance and a Bot called Marketing are two roles on one machine, and either can reach anything the other signed into. That single fact explains most login, password and "why does it remember that" surprises.

At a glance#

What "shared" means in practice#

Cursor's help says that once you sign in to a site, every Bot on your account can use that sign-in until it expires. Approvals and ask-first rules control what a Bot does, not what it can see. That makes Bot boundaries useless as a security fence.

Design your access around it. If a login would be catastrophic in the hands of your least careful Bot, it does not belong on this computer. For sensitive accounts, use a second Grok Bot account or keep the login off entirely. Our safety guide and permissions guide cover how to set rules around that.

Passwords: type them yourself for now#

On October 5 a user found that after the in-chat Secure Form filled a GitHub password, the snapshot the Bot took before clicking Sign in showed the password in plain text. It never appeared in chat, but it landed in tool output and the transcript. Cursor staff replied that day that this should not happen, that a fix was in progress, and that signing in yourself is safest until it ships.

None of the later release notes mention snapshot redaction. 0.68.1 changed where Secure Forms fill, 0.71.2 put multi-field logins on one form, and 0.75.5 added a Vault in Settings that saves logins, cards and contact info. Treat the issue as open.

Safe sign-in, step by step#

1. When a Bot asks for a password, choose Open the screen, not the Secure Form.
2. The full-screen view opens in Watching (since the October 11 release). Press Take control.
3. If the computer is asleep, click the Computer is asleep preview to wake it in place (0.71.2 and later).
4. Type the password and press Sign in yourself. Finish two-factor or CAPTCHA.
5. Confirm the page has moved past the login form, then hand control back.
6. Never paste passwords, recovery codes, API keys or verification codes into chat.
7. If you already used the Secure Form for a password, change that password.

1Password quirks#

• Autofill says Filled but the field is empty (Instagram, Letterboxd and others, reported September 30). Type the password from 1Password yourself.
• Google password step will not fill, in the popup or full page (staff, October 10). Same workaround; the Google session usually persists afterwards.
• "Credential delivery outcome was unknown" was caused by one login with a website address over 2,000 characters. Cursor fixed it server-side on October 20; no app update needed.
• Since 0.71.2, screenshot, computer and browser actions keep working without 1Password connected.

Why logins vanish, and what blocks the browser#

Community reports from mid-August describe Chrome profiles on the shared computer resetting, so yesterday's sessions ask again. Some sites also expire sessions or verify every sensitive action, which no setting avoids. Two 0.77.0 fixes (October 26) should help: the Bot's browser keeps site logins after its last window closes, and keys stored in the system keyring, such as Okta Verify's, survive when the computer is recreated.

Symptom → Fix

• Site asks you to sign in again every day → Use a plugin from Connect Apps where one exists. Plugin OAuth tokens live on Cursor's backend, not in browser cookies. Our plugins guide covers setup.
• X says "We've temporarily limited your login" → Do not let the Bot retry. Staff suggested a new agent and signing in yourself. Since 0.75.5, asking a Bot about your X account connects X through your linked X account, even if you removed the X plugin.
• Site flags the cloud browser as automated (QuickBooks and marketplaces were reported) → Use a connector or a custom MCP server that talks to the API, and vote for a native connector if none exists.
• Site blocks by region or IP → Settings → Computer → turn on Route traffic through this computer, so traffic leaves through your own network. Staff called it the first thing to try, with no guarantee.
• Wanting the Bot to drive your local Chrome → Not possible. There is no extension, and the Bot only controls its cloud computer.

Since 0.78.1 (October 27), Settings says when the Bot's computer is asleep while routing is on, and Reset and Recover keep the current disk instead of restoring an older backup when the computer had been refusing saves.

Long threads and starting fresh#

A Bot's conversation grows without a visible context meter. Every turn re-reads it, and summarizing only kicks in near the model's limit, so old threads cost more per reply. Our usage limits guide shows how much that adds up.

Your reset options#

Hide a Bot rather than deleting it until you are sure. After a Duplicate, paste a short handoff summary as the first message.

Memory spreads further than it did. Since 0.75.2, what a personal Bot saves in one chat is remembered in all chats with it. Staff said on October 20 they could neither confirm nor rule out that chat history itself is merging across chats, and are checking. There is no memory editor yet: ask the Bot to print its memory profile and log, then delete specific entries.

Keep continuity with a notes file#

A community workaround from the long-running compact-context thread: give each long-lived Bot a small durable notes file that a routine rewrites at the end of every session. A fresh chat or Duplicate can then read that file first. If the notes stay small while the transcript balloons, tokens are going into tool output rather than real state.

Back up before you need to#

Copy your complete memory, routines and connector list into a folder named

backup-[bot-name]-[date]. Zip the folder and send the zip to me as an attachment

in this chat. Do not modify, merge or summarize any memory entries.

Run the same brief on a coordinating Bot for shared memory and skills. Keep the raw backup as its own zip; staff agreed it should not be folded straight into SKILL.md files, since memory goes stale while skills should stay stable.

Pre-flight checklist#

• Nothing signed into the shared computer would be catastrophic if any Bot touched it.
• Passwords are typed on screen by you, not through the Secure Form.
• Plugins are used wherever they exist; browser logins are the fallback.
• Local computer execution is off unless a task needs it.
• Each new task starts in a fresh chat; standing rules live in the Bot's profile.
• Finished Bots are hidden, not deleted.
• Important Bots have been zipped and backed up at least once.

Our take#

Treat the shared computer like one browser profile you have lent to a team of interns. Put only what you would let all of them touch on it, keep passwords off the Secure Form until Cursor confirms the snapshot fix, and reach for plugins before browser logins every time. If something still breaks, start from the troubleshooting matrix.

Frequently asked questions#

Do my Grok Bots have separate computers?#

No. The official overview describes one persistent cloud computer per account, with a browser, file system and terminal shared by every Bot. The FAQ on x.ai/bot, read October 25, says isolation is per user, not per Bot. Separate Bots are separate conversations and roles, not separate machines or logins.

Is it safe to type a password into the Grok Bot Secure Form?#

Not for passwords right now. On October 5 a user showed a Secure Form password appearing in plain text in a page snapshot, and Cursor staff said a fix was in progress. Release notes through 0.75.5 do not mention one. Choose Open the screen and type the password yourself; if you already used the form, change that password.

Why does Grok Bot keep losing my website logins?#

Community reports describe Chrome profiles on the shared computer resetting, and some sites expire sessions or demand verification for sensitive actions. Use a plugin where one exists, since its token does not depend on browser cookies. Since 0.77.0 (October 26) the Bot's browser keeps site logins after its last window closes.

Can I clear a Grok Bot's context?#

Not directly. There is no clear or Compact option, and staff said on October 19 the only supported way to shrink a working set is Duplicate or Delete. You can open a new chat with the same Bot via Ctrl+Shift+N, or Duplicate the Bot, which keeps profile, skills and routines but not history or learned memory.

How do I back up a Grok Bot's memory?#

There is no one-click export. Cursor staff said a Bot's durable state lives as plain text files on its computer: ask the Bot to copy its memory, routines and connectors into a folder, zip it and send it as a chat attachment. Version 0.77.0 added Import Memory, but no export.