# Grok Bot's cloud computer: what your Bots share All your Bots work on one cloud computer and share its files, logins and programs. See what each Bot keeps to itself, how to take over and what Reset removes. *From Learn Grok Bot, an independent guide (not affiliated with SpaceXAI or Cursor). Web version: https://learngrokbot.com/shared-computer Last verified: 2026-10-07.* *Step 7 of 9 on the path "Learn Grok Bot, step by step". Before it: [Approvals and rules](https://learngrokbot.com/approvals.md). After it: [Teach a task](https://learngrokbot.com/skills.md).* All your Bots work on one computer in the cloud. It has a browser, files and a terminal, and it keeps running when your own computer is off. **In short** - Your account has one cloud computer. Every Bot you create works on it. - Files, website logins and installed programs sit on that computer, so every Bot has them. - Each Bot keeps its own conversation, its own memory and its own routines. - You can open the computer to watch a Bot work, and take over when a site wants your password or a code. - **Update** and **Reset** keep your Bots, files and logins. A reset removes installed programs, and so does one kind of update. ## One computer, shared by every Bot The computer belongs to your account. A Bot you add next month works on the same machine as the Bot you made today. The drawing shows the arrangement. You talk to each Bot in its own chat, and both Bots do their work in one place. Diagram: You message two Bots, Research and Inbox, each in its own chat. Both Bots work on the same cloud computer, which has a browser, files and a terminal. - You → Research: a chat each - You → Inbox - Research → One cloud computer: both work here - Inbox → One cloud computer - Note on One cloud computer: a browser, files and a terminal - The computer runs Linux. Its desktop has a Chrome browser, a file manager and a terminal. - A Bot that is partway through a job keeps going when you close the app, your laptop or your phone. Routines run there too. - When no Bot is working, the computer hibernates. Hibernating deletes nothing. ## What two Bots share, and what each keeps One computer means some things belong to all your Bots at once, and the rest stay with the Bot they started with. Tap each of the six things to see which is which. **Interactive: What's shared?** Open it: https://learngrokbot.com/widgets/shared-computer-whats-shared.html What it does: Two Bots on one account, Research and Inbox, drawn over the one cloud computer. Tap a thing that belongs to Research (a saved file, a website login, a conversation, a memory, a routine, an installed program) to see whether Inbox has it too, and why that matters. Its content as text: ### What's shared? Research and Inbox are two Bots on one account. Tap a thing that belongs to Research and see whether Inbox has it too. Research - Its conversation - What it remembers - Its routines Inbox - Its conversation - What it remembers - Its routines The one cloud computer Both Bots work here. - Files - Website logins - Installed programs Here are all six. The drawing shows where each one lives. Both Bots have it #### A file Research saved Files live on the computer, and every Bot can see them. Inbox can open the report Research saved. **Why it matters** One Bot can pick up where another left off. Ask for files to be kept in `/workspace`, the shared folder, so every Bot knows where to look. Both Bots have it #### A website you signed Research in to The browser's sign-ins belong to the computer. Inbox opens the same site and is already signed in. **Why it matters** You sign in once. From then on every Bot on your account can use that login, and signing out in one Bot's window signs the others out too. Research only #### Research's conversation Each Bot keeps its own conversation. What you told Research isn't in Inbox's. **Why it matters** Inbox starts without the background you gave Research. Tell Inbox yourself, or have Research save its notes as a file that Inbox can open. Research only #### What Research remembers A Bot holds on to preferences and facts it picks up as it works. That memory stays with the Bot that learned it. **Why it matters** Teach Research how you like a report laid out and Inbox still won't know. Tell each Bot the preferences its own job needs. Research only #### A routine Research runs A routine belongs to the Bot you set it up with. It's listed in that Bot's details and no other Bot runs it. **Why it matters** Delete Research and its routines are deleted with it. Both Bots have it #### A program Research installed Installed programs live on the computer, so Inbox can use the tool Research installed. **Why it matters** A computer update or a reset removes installed programs for every Bot at once. Files and logins stay. What sits on the computer is there for every Bot: files, website logins and installed programs. Each Bot's conversation, memory and routines are its own. So a second Bot walls nothing off. Whatever one Bot can reach on the computer, every Bot on your account can reach, and that includes any site you're signed in to there. ## Watch a Bot work, and step in when it needs you The computer has a screen, and you can open it from any Bot's chat. You'll want to when a Bot is slow and you wonder what it's doing, and when a site asks for something only you have. **Walkthrough: Watch a Bot work, then step in** ### Step 1: Open the Bot's computer Click the Bot's name at the top of its chat, then the **Computer** tab. The tile shows the Bot's screen. Move your pointer over the tile and click **Open**. ![The details panel for a Bot called Demo Price Watch, on its Computer tab. A tile shows a small picture of a web page with an Open button over it, captioned Demo Price Watch's screen](https://learngrokbot.com/assets/shots/shared-computer-open-computer.png) ### Step 2: Watch, or click and type The Bot's desktop fills the window, live. Your mouse and keyboard work here too. A click or a keystroke goes to the Bot's computer, so a stray one lands in the middle of the Bot's work. ![The right-hand side of the Bot's desktop, filling the app window: a Chrome browser showing a pricing page with the heading Trello your way and three plans, Standard at $5, Premium at $10 and Enterprise at $17.50. A small Exit fullscreen button sits at the top right corner of the window](https://learngrokbot.com/assets/shots/shared-computer-full-screen.png) 1. The Bot's own Chrome browser, on the page it's reading. Clicks, typing and page changes show as they happen. 2. **Exit fullscreen**, the small button at the top right, takes you back to the chat. The Bot carries on either way. ### Step 3: Click Take over when a Bot asks Some steps are yours alone: a password, a two-factor code, a CAPTCHA, a payment check. When a Bot reaches one, it stops and posts a **Computer** card that says what it needs, and its row in the sidebar starts **Waiting for you**. Click **Take over**. ![A card in a Bot's chat titled Computer. One line reads Sign in to GitHub, then hand the screen back. A grey note under it says the sign-in happens in the browser on the Bot's computer and stays signed in there. Below a blank preview tile are three buttons: Take over, I'm done and Skip](https://learngrokbot.com/assets/shots/shared-computer-take-over-card-first-hand.png) Click **Skip** if you don't want to do that step now. ### Step 4: Sign in yourself, then hand the computer back The Bot's browser fills the window, open on the site's own sign-in page. Type your password there, and any code the site sends you. A bar across the top says what the Bot is waiting for and holds two buttons. When you're in, click **I'm done, continue**. ![The right-hand side of the Bot's screen after Take over. A bar across the top holds two buttons, Skip this step and I'm done, continue. Under it, the Bot's Chrome browser shows GitHub's sign-in form, with a Username or email address field, a Password field and a Sign in button, all empty](https://learngrokbot.com/assets/shots/shared-computer-hand-back-first-hand.png) The card in the chat changes to **Done**, and the Bot picks up where it stopped. ### Step 5: Fill in a Secure Form if the Bot sends one A Bot has a second way to ask. A smaller card reads **Sign in to** and the site's name, with **Secure Form** under it. Click **Open** and the form appears inside the app. Fill it in and click **Continue**. ![A dialog titled Sign in to GitHub, Secure Form. It has a Username or email address field, a Password field, the line Never shown to your Bot. Filled directly to github.com. and a Continue button](https://learngrokbot.com/assets/shots/shared-computer-secure-form.png) 1. The fields match the site's sign-in page. 2. The form's own note on where your typing goes: **Never shown to your Bot. Filled directly to github.com.** 3. **Continue** lights up once every field is filled. To turn a form down, tell the Bot in chat to skip the sign-in. > **You should see** > > The site is signed in on the computer and the Bot carries on with the job. Every Bot on your account can use that login until it expires. ## Update or reset the computer The computer needs looking after now and then, and two controls do it. Both are in the desktop app, in **Settings** > **Updates**, under **Grok Bot's Computer**, and both act on every Bot at once. **What each one keeps and removes** | | Use it when | Keeps | Removes | |---|---|---|---| | Update, software only | An update is waiting | Everything, installed programs included | Nothing | | Update, whole computer | An update is waiting | Your Bots, files and logins | Installed programs | | Reset | The computer is stuck and nothing else has helped | Your Bots, files and logins, as last saved | Installed programs, and very recent changes if they couldn't be saved first | - The line under **Update Grok Bot's Computer** says which kind of update is waiting. With none waiting it reads "Your computer is on the latest version" and there's no button. - An update saves your work first and doesn't run if it can't. A reset interrupts whatever your Bots are doing, so pick a quiet moment. - Settings calls installed programs "installed apps and packages". Your chats and the plugins you've connected aren't on the computer, and no update or reset touches them. When the app says it can't reach the computer, work through [the recovery steps](https://learngrokbot.com/cant-reach-computer) in order. **Reset** is the last of them. ## Check you've got it You now know where each thing lives and what a reset does to it. Try the same thinking on a case this page hasn't covered. **Predict: You delete your Research Bot. Which of its things are still there afterwards?** - Nothing, because deleting a Bot clears out everything it made - The files it saved and the sites it was signed in to - Its conversation and its routines Answer: The files it saved and the sites it was signed in to Deleting a Bot removes what belonged to that Bot: its conversation and its routines. The files it saved and the logins it used are on the computer, which belongs to your account, so they stay and your other Bots can still use them. To put a Bot away and keep its work, right-click it in the sidebar and choose **Hide from sidebar**. ## Three mistakes with the shared computer Three things to avoid, each with what to do instead. > **Common mistake: Making a second Bot to keep an account private** > > A new Bot gets a new conversation and the same computer. It's already signed in wherever your other Bots are. > > **The fix:** Sign in on the computer only to accounts that every one of your Bots may use. Keep the rest off it. > **Common mistake: Pasting a password into the chat** > > A password or a one-time code in a message becomes part of the conversation. > > **The fix:** Ask the Bot to open the site's sign-in page and stop there. Then sign in yourself with **Take over** or the **Secure Form**. > **Common mistake: Counting on an installed program or a temporary file to last** > > A computer update and a reset both remove installed programs, and a temporary folder isn't a safe place for anything you need. > > **The fix:** Have your Bots save anything worth keeping in `/workspace`, or attach it to the chat. After a computer update or a reset, ask the Bot to install what it needs again. Next, show a Bot how to do a task by doing it once yourself on this computer. **Next:** [Teach a task and save it as a skill](https://learngrokbot.com/skills) Show a Bot a browser task once, then have it repeat the task whenever you ask. ### How big is Grok Bot's computer? SpaceXAI and Cursor don't publish its processor, memory or disk size. When space runs short the app shows **Computer is low on disk space**, and a Bot called Disk Saver suggests what to clean up. It asks before it deletes anything. ### Where does the computer run? In the United States, on Cursor's cloud. There's no setting for choosing a region. ### Can a Bot use my own computer too? Only if you allow it. The cloud computer is separate from the Mac or PC in front of you, and a Bot touches yours only under the **Execution on this computer** setting, which [approvals](https://learngrokbot.com/approvals) covers. - 2026-10-07: The **Take over** card and the screen you hand back from are now pictures from our own run of the app (version 0.68.1). The waiting card carries no **Action needed** tag in this version. - 2026-10-06: First published. ## Sources - [SpaceXAI docs: Use the computer and apps](https://docs.x.ai/grok-bot/computer-and-apps) - [Cursor Help Center: Grok Bot computer](https://cursor.com/help/grok-bot/computer-recovery) - [Cursor Help Center: Grok Bot How Tos](https://cursor.com/help/grok-bot/how-to) - [SpaceXAI docs: Grok Bot](https://docs.x.ai/grok-bot/overview) - [SpaceXAI docs: Create and manage Bots](https://docs.x.ai/grok-bot/bots) - [SpaceXAI docs: Skills and routines](https://docs.x.ai/grok-bot/skills-routines-and-automations) - [SpaceXAI docs: Approvals, security, and privacy](https://docs.x.ai/grok-bot/approvals-security-and-privacy) - [SpaceXAI docs: Grok Bot security](https://docs.x.ai/grok-bot/security) - [Cursor Help Center: Grok Bot FAQs](https://cursor.com/help/grok-bot/faqs) - [SpaceXAI: Grok Bot changelog](https://x.ai/changelog/bot) - [Cursor forum: staff on the browser session all Bots share](https://forum.cursor.com/t/grok-bot-ship-real-session-fences-bots-are-not-a-security-boundary/168476)