Cloud computer maintenance: Update, Recover, Reset, and data safety
Each of your Bots runs on a persistent cloud computer. This page covers the complete approach to Grok Bot cloud computer recovery and routine maintenance: use Update to stay current in normal times, follow the official "least destructive" order when you can't connect, and only touch Reset as a last resort—knowing what each step preserves and what it might lose.
What you'll be able to do after this lesson
- Explain what Update, Recover, and Reset each preserve and clear, so you no longer click buttons blindly.
- Find the cloud computer maintenance entry in Settings > Computer and decide which operation to use right now.
- When you hit Reconnecting / Couldn't Reach Grok Bot's Computer errors, recover the cloud computer following the official 5-step order.
- Complete the data safety check before Reset, preserving the recent changes that can be preserved.
- Distinguish where "chat history," "saved files," and "unsaved changes" are each stored, and stop using
rm -rfto delete chats.
Your current predicament
- The Bot is working away and suddenly Reconnecting pops up in the chat—you don't know whether to wait, reopen the App, or which button to click.
- You've heard of Reset but aren't sure whether your files and logins will survive it, afraid everything will vanish with one click.
- Bots or chats seem to have "disappeared," or the cloud computer is nearly full, and you don't know where to start looking.
When to use this technique
When you need to:
- Keep the cloud computer up to date and troubleshoot the Bot reporting "computer can't connect";
- Make a choice among Update, Recover, and Reset that won't lose data;
- Figure out which data lives on the cloud computer and which lives elsewhere.
And you don't want to:
- Click Reset the moment something goes wrong and gamble on luck;
- Lose recent unsaved changes on the cloud computer.
🎒 Preparation before you start
- Completed Your first Bot: create it, assign work, and watch it work on the cloud computer, with at least one Bot in your account.
- Logged in on the desktop App. The cloud computer's Update/Recover/Reset can only be done on desktop; mobile does not support updating/recovering the computer.
- Don't let the App version get too old: when the version is more than 14 days old and an official new version is out, the App shows a full-screen Update required prompt—update the App first before troubleshooting the cloud computer; App updates and cloud computer updates are two different things.
- Bookmark the status page status.cursor.com and check official service status first when you can't connect.
- If the cloud computer holds important files, have the Bot package and download a copy locally first. Both Recover and Reset rebuild from "the most recently saved data," so recent changes made while the cloud computer was unreachable or failed to save may be lost.
Core idea
The Bot's files, logins, installed apps, and browser all live on the cloud computer, shared by all Bots in the same account; chat history is stored outside the cloud computer, so a cloud computer problem won't directly delete conversation history.
Maintenance falls into two categories—distinguish them first:
- App update: updates your local Grok Bot client. When the version is more than 14 days old and an official new version is out, you'll be forced to update (full-screen Update required prompt).
- Cloud computer maintenance: Update / Recover / Reset for the cloud computer itself in Settings > Computer—the focus of this page.
Comparison of the three operations (per the official help docs):
| Operation | What it does | Preserves | Clears |
|---|---|---|---|
| Update | Upgrades the cloud computer to the latest version. Two kinds: software update only refreshes the Grok Bot software; computer update replaces the whole machine and may be schedulable for later. The text under Update Bot's Computer in Settings > Computer will say which kind it is | Software update: everything, including installed apps; computer update: saved Bots, files, and logins | Software update: none; computer update: installed apps and packages |
| Recover | First tries to save current data, then rebuilds the cloud computer from saved data on the latest version; work in progress will be interrupted | Saved Bots, files, and logins | Installed apps and packages; recent changes made while the cloud computer was unreachable or failed to save |
| Reset | Rebuilds the cloud computer from the most recently saved data on the latest version; work in progress will be interrupted | Saved Bots, files, and logins | Installed apps and packages; recent changes made while the cloud computer was unreachable or failed to save |
Key insight: Both Recover and Reset rebuild from "the most recently saved data". Only two things can truly be lost—installed apps and packages (you'll need to reinstall them), and recent changes that failed to save. Saved Bots, files, and logins are restored after all three operations.
One more look at "what data, and will it be lost":
| Data | Recovery status |
|---|---|
| Chat history | Stored outside the cloud computer; a cloud computer failure can't delete it |
| Saved Bots, files, and logins | Restored after Update, Recover, and Reset |
| Unsaved recent changes | Update saves them first and won't run if saving fails; Recover/Reset save them first if the cloud computer is reachable, but they may be lost if it isn't |
| Installed apps and packages | kept by software updates; cleared by computer updates, Recover, and Reset, requiring reinstallation |
| Project directories like node_modules and Python venv | are not included in what gets saved, so they must be reinstalled after a computer update / Recover / Reset |
| Files that exist only on your local Mac/Windows | cloud computer recovery cannot reach them, back them up yourself |
Follow Along
Step 1: Find the cloud computer maintenance entry point (Settings > Computer)
Why: Update, Recover, and Reset are all initiated from the same entry point. Learn where it is first, so you're not hunting all over the interface when something breaks.
Use the computer preview on the right side of the chat to watch the Bot work; to do maintenance, open Settings > Computer and find the actions in the Bot's computer section. When the cloud computer shows Reconnecting, the reconnect screen also directly provides a Recover entry point.
You should see: The Bot's computer section lists the actions available for this cloud computer; if an Update is pending, the text below the button will state whether it's "software refresh only" or "a full computer update."
- You can find the Bot's computer section in Settings > Computer
Step 2: For routine maintenance, prefer Update
Why: Update is the least destructive—software updates clear nothing; even a full-replacement computer update only clears installed apps and packages, while saved files and logins remain.
In Settings > Computer, select Update Bot's Computer; if you're offered the option to schedule it for later, pick a time when the Bot isn't working.
You should see: Updates usually finish within a few minutes; downloading a large image or transferring data takes longer—if it shows Update still running, keep waiting. Afterward the Bot resumes work, and previously saved files and logins are still there.
Two minor hiccups—no need to panic about either:
Update says files aren't ready to be backed up (aren't ready): nothing will change—wait a bit and try again, don't force it with Reset.
Settings shows An agent couldn't pause in time, so the computer was not updated: let that Bot finish its work first, then Update again.
After the Update, have the Bot list the working directory to confirm the files are still there
Step 3: If the computer can't be reached, follow the 5-step order to do Grok Bot cloud computer recovery
Why: The official guidance is a recovery order of increasing destructiveness—start with the mildest, with Reset last; and during Reconnecting, your Bots, files, and logins are safe.
When you see Reconnecting or a Couldn't Reach Grok Bot's Computer error, follow this order:
- First wait for the automatic reconnection, then choose Retry. Your data is safe during this time, do not Reset now.
- If that still doesn't work, fully quit Grok Bot and reopen it. On Mac, choose Quit from the menu bar—don't just close the window.
- If Settings > Computer offers an Update, do the Update first.
- If it still can't be reached, or the update seems stuck and a Recover computer option appears, do the Recover. If the update is just slow, Keep waiting is the safe default.
- Only Reset after trying all of the above (see Step 4).
You should see: Reconnecting and Recover usually finish within a few minutes; during that time you can choose Continue in Background to run it in the background. After Recover: saved files and logins are still there; installed apps and packages are cleared and must be reinstalled; if the cloud computer was previously unreachable and saving failed, recent changes may be lost. If the computer still looks empty after Recover, don't put anything into it—contact support right away.
Two iron rules:
When an Update or Reset is already running, do not start a second one—repeated Resets interrupt recoveries that haven't finished.
If Recover or Reset fails, use Retry Recovery / Retry Reset once, then stop and contact support (support@x.ai).
The error is gone, the computer preview shows the desktop, and the Bot responds normally
Step 4: Only Reset if Recover didn't work—do the data safety checks first
Why: Like Recover, Reset rebuilds from the most recently saved data—it can't recover recent changes that failed to save, and it interrupts work in progress—so finish the checks before pressing it.
Confirm three things before Reset:
- Has the Bot recently disappeared or had a failed save? Contact support first—don't rush to Reset.
- Is the computer still Reconnecting? Wait for it to finish, and don't Reset during that time.
- Is no Update or Reset currently running? If one is, wait for it to finish.
If it's just that "a chat or Bot seems to be missing," don't Reset yet. Chats are stored outside the cloud computer—follow the official checklist: fully quit and reopen the app; check on another device with the same account (including the iPhone app); check the sidebar for Hidden Bots (desktop) / Show Hidden Bots (mobile); confirm you're signed in to the same Cursor account. Only contact support if it can't be found on any device.
Once all checks pass, perform the Reset in Settings > Computer.
You should see: The cloud computer is rebuilt on the latest version from the most recently saved data: saved Bots, files, and logins are restored; installed apps and packages are cleared; project directories like node_modules and Python venv were never included in what gets saved, so all must be reinstalled; recent changes lost when the cloud computer was unreachable or saving failed are gone; chat history is unaffected.
- After the Reset, have the Bot open a website you were logged in to before, to confirm the saved login still works
Checkpoints ✅
- You can state what each of the three operations "keeps / clears"—in particular, that Reset also keeps saved files and logins.
- When you hit Reconnecting, your first reaction is to wait + Retry, not Reset.
- You know the entry point is Bot's computer in Settings > Computer, and that Recover can also be accessed from the reconnect screen.
- You completed the three checks before Reset: no Bot disappearance / failed saves, not in Reconnecting, and no Update/Reset currently running.
- Important files have an additional backup outside the cloud computer.
Pitfall Reminders
❌ Reset at the first sign of trouble
Why: Reset is not a universal "factory restore" button. Like Recover, it rebuilds from the most recently saved data—it can't recover recent changes that failed to save, and it interrupts work in progress. The right approach: Follow the official 5-step order — wait and Retry → fully quit and reopen → Update → Recover → and only then Reset.
❌ Deleting chats with rm -rf on the cloud computer
Why: Chat history is stored outside the cloud computer's file system, so deleting files won't delete chats — and you might accidentally delete files the Bot needs. The right approach: Chats are not managed by the cloud computer's file system, so don't try to clean up chats by deleting files; keep only the files the Bot needs for its work on the cloud computer.
❌ Panicking into cleanup or Reset when the disk is almost full
Why: A nearly full disk does not mean data loss. When space is running low, the Bot will notify you once in the chat, naming the largest files/folders and their sizes, and will only delete them with your consent. The right approach: Review the list the Bot reports and then decide what to delete; say "no" and the files stay untouched. Cleanup only affects cloud computer files and never touches chats.
❌ Putting sensitive credentials directly on the cloud computer
Why: All Bots under the same account share one cloud computer — cookies, logins, files, and command-line credentials are all shared, with no isolation between Bots. The right approach: Keep sensitive information like account passwords in Vault (next lesson); don't put anything that shouldn't be shared on the cloud computer.
If you hit an error not listed on this page, go to Error Quick Reference: Find Fixes by the Exact Error Message and search by the original text.
Lesson Summary
✅ On this page you learned:
- The cloud computer maintenance entry point is Bot's computer under Settings > Computer; to watch the Bot work, use the computer preview on the right side of the chat.
- Update first: a software update clears nothing; a computer update only clears installed apps and packages, while saved files and logins remain.
- Grok Bot cloud computer recovery follows 5 steps: wait and Retry → fully quit and reopen → Update → Recover → and only then Reset.
- Reset is not a wipe: it rebuilds from the most recently saved data, keeping saved Bots, files, and logins; what's lost are installed apps/packages and recent changes that failed to save.
- Chat history is stored outside the cloud computer; a nearly full disk is not data loss, and the Bot will ask you before deleting anything.
Key operations recap:
| Operation | When to use | Keeps | Clears |
|---|---|---|---|
| Update | Routine maintenance; install whenever updates are available | Software update: everything; computer update: saved Bots/files/logins | Software update: nothing; computer update: installed apps and packages |
| Recover | Can't connect, update stuck | Saved Bots, files, and logins | Installed apps and packages; recent changes that failed to save |
| Reset | Last resort when the first four steps all fail | Saved Bots, files, and logins | Installed apps and packages; recent changes that failed to save |
Next Lesson Preview
Saved logins on the cloud computer are preserved, but they are visible to all Bots under the same account. The next lesson Vault and Secure Logins: Let the Bot Log In for You Without Seeing Your Password teaches you how to put account passwords into Vault: the Bot can fill them in for you but can never see them in plain text.
You will learn:
- What Vault can store (logins, cards, etc.) and why the Bot can't see the values.
- How to add entries manually, and how to import CSVs from password managers like 1Password and Chrome.
- The order in which a Bot logs into websites: Vault → connected password manager → Secure Form.
- When to use Secure Form instead of sending your password directly to the Bot.