Grok BotKnown issues

Illustration: a taped cardboard moving box seen at a three-quarter angle, with one paper folder leaning against its side, in black and white.
Illustration

Grok Bot computers were rebuilt today; reinstall system apps

A planned server move around 4:30 PM ET rebuilt Grok Bot computers. Home folders and saved logins survived; system-wide apps and the browser profile did not.

If an app you installed on your Grok Bot's computer is gone tonight, or the browser lost its extensions and tabs, you didn't break anything. Cursor staff confirmed that "around 4:30 PM ET" on October 13 they "ran a planned infrastructure migration that moved Grok Bot computers onto new servers," and computers were rebuilt as part of it. Reinstall what you need, and keep installers in your home folder from now on.

  • What survived: "the files in your home folder and your saved logins."
  • What didn't: "apps installed system-wide and the browser’s own profile (extensions, history, open tabs)."
  • Can it be undone? No. "The previous computer can’t be restored, so those apps will need to be reinstalled."
  • Current state: staff say the rebuilt computer "is running normally on the latest version now."
  • Did you cause it? No. Staff told the reporter "it wasn’t the Update option in settings."

What changed#

A user reported at 7:08 PM ET that their Grok Bot's computer was reset around 6:28 PM ET on Oct 13 without their permission, wiping the browser and some other apps they had installed. (That post has since been hidden after community flags, so we paraphrase it here.) They had not chosen Update Bot's Computer.

At 7:37 PM ET, staff member kevinn replied that the reset came from the planned server move earlier in the afternoon. The rebuild works like a computer update: your home folder and saved logins carry over, anything installed outside the home folder does not. The reporter noticed the change about two hours after the time staff gave for the move; staff did not say how long the migration ran.

As of 8:20 PM ET, status.cursor.com showed no incident and no scheduled maintenance entry for the move.

Why it matters#

Many people set up their Bot's computer once and forget it: a desktop app, a CLI installed with a system package manager, a browser extension for a site the Bot works on. Those are the pieces this rebuild dropped. A routine that depends on one of them can fail tonight or tomorrow morning with an error that looks unrelated, like a missing command or a site that suddenly wants a sign-in step the extension used to handle.

How to check and recover#

  1. Ask your Bot to list what it expects to find: CLIs, desktop apps and browser extensions its routines use.
  2. Have it check each one is still installed. Anything in your home folder should be fine.
  3. Reinstall what's missing. Where you can, keep installers or portable apps in your home folder so a future rebuild keeps them, as staff suggested.
  4. Open the browser and re-add any extensions. Staff said saved logins carry over, so you may not need to sign back in, but check the sites your routines use.
  5. Run your most important routine once by hand to confirm it works before its next scheduled fire.

Example prompt for your Bot:

Your computer was rebuilt today and system-wide apps and browser extensions were removed. List every app, CLI and browser extension my routines and skills depend on, check which ones are missing now, and show me the list with where you'd install each one. Wait for my OK before installing anything. Then install into my home folder where possible and tell me what you couldn't reinstall.

Good to know#

  • Your files are safe if they live in your home folder. Staff said home-folder files and saved logins carry over in a rebuild.
  • This is the same split as Update Bot's Computer: the settings docs say a computer update keeps files and logins but removes installed apps and packages.
  • Bots on one account share one computer, so a single reinstall covers all of them.
  • Staff have not linked the migration to this afternoon's separate routines incident (1:52 to 4:29 PM ET).
  • Some users on other threads tonight report the computer screen or browser tools failing outright. Staff have not tied those reports to the migration, so treat them as separate until they do.

What to watch#

Whether Cursor posts a notice for future planned moves before they happen, and whether rebuilds start keeping the browser profile. If your computer still misbehaves after you reinstall, post on the forum thread so staff can check it.

Sources

  1. forum.cursor.com
  2. forum.cursor.com
  3. status.cursor.com
  4. cursor.com

Something wrong? Tell the bot