# Grok Bot computer (box) migrated/reset almost daily — installed tools and logins wiped

**URL:** <https://forum.cursor.com/t/grok-bot-computer-box-migrated-reset-almost-daily-installed-tools-and-logins-wiped/175756>\
**Category:** Bug Reports\
**Tags:** grok-bot\
**Created:** [October 22, 2026, 11:26am UTC](https://forum.cursor.com/t/grok-bot-computer-box-migrated-reset-almost-daily-installed-tools-and-logins-wiped/175756 "2026-10-22T11:26:41Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\
**Post date:** [October 22, 2026, 12:08pm UTC](https://forum.cursor.com/t/grok-bot-computer-box-migrated-reset-almost-daily-installed-tools-and-logins-wiped/175756/8 "2026-10-22T12:08:49Z")

</div>

Hey @Korbi,

There are a few separate things going on here!

When a new version of the Bot’s computer ships (often for browser security fixes), computers on older versions are replaced with a fresh one the next time they’re used. Oct 17 and Oct 21 were updates like that, rolled out to every computer, and Oct 22 was a similar replacement. A replacement restores your bots, saved files and logins, but apps and packages installed outside the saved folders (apt packages, tools in /usr/local/bin, compiled binaries) are not carried over. This is how [computer updates, Recover and Reset](https://cursor.com/help/grok-bot/computer-recovery) work today. Keeping installed software across rebuilds is a known gap the team is tracking, and I’ve added your report to it.

On Oct 21 and Oct 22 a timing problem during the replacement als removed your old computer before the new one was ready. Your bots were left without a computer for a while and then landed on a fresh one that was still copying your files back, which is why repos looked broken and bot folders were missing for those ~20 minutes. That’s also tracked, and I’ve added your report there too. The older config copies (like the Proton Bridge vault) are most likely changes made after the last save that didn’t carry over.

When nothing is using the computer it’s paused, and it resumes when a bot needs it. With ~25 bots and routines that happens many times a day. This is expected, and it is likely what `who -b` is picking up as a new boot.

The computer’s browser takes its time zone from the location its traffic exits from, so after the rebuild it most likely picked up a US exit and now reports America/New\_York.

Sends from Grok Bot’s mail to that address being refused is a known issue. Please use this thread or in-app feedback in the meantime.

To cut the re-setup time until installed software survives rebuilds:

1. Keep a setup script in /workspace that reinstalls what you need (Proton Mail Bridge, gh, glab and so on), and have a bot run it after a rebuild.
2. Where you can, put single-file tools and your compiled binaries under a folder you’ve seen survive rebuilds, rather than /usr/local/bin.

You’ll still need to sign in to Proton Bridge again with 2FA after a rebuild for now.

---

_[View the full topic](https://forum.cursor.com/t/grok-bot-computer-box-migrated-reset-almost-daily-installed-tools-and-logins-wiped/175756)._