Update or recover the Grok Bot computer

The Grok Bot app and the Agent Computer update separately. When the computer is unreachable, work from the least destructive option first. Official guide: Work with Grok Bot → Update, recover, or reset, and Settings and notifications → Updates.

Least destructive order

1. Retry from the error state, or reopen the conversation.
2. Restart the Grok Bot app and check for an app update (Check for Updates / Restart to Update in the Beta section of settings).
3. Choose Recover Agent Computer when the unreachable state offers it.
4. Use Update Agent Computer to rebuild on the latest image.
5. Use Reset Agent Computer only as a last resort.

Recover and Update preserve durable files and logins. Reset returns the computer to its synced durable state, and anything not yet synced does not come back. Conversations are stored outside the computer, so they survive even a Reset.

What stays durable

Keep durable project files under /workspace in clear project folders. Files, browser state, and supported sign-ins survive normal computer updates and recovery. Treat temporary directories, manually installed packages, and uncommitted application state as replaceable. Copy important results into the workspace or attach them to the conversation before you force a rebuild.

When client controls are not enough

If Update, Recover, and Reset all fail the same way on every device, stop looping the buttons and escalate for a backend restore. See When client Update, Recover, and Reset all fail.

Pitfalls

• Jumping straight to Reset — you lose unsynced recent work that Recover or Update would have kept.
• Treating temporary installs outside /workspace as durable across an Update.
• Looping Update / Recover / Reset when every client control already failed — collect version, OS, error text, and request IDs, then ask staff for a backend restore.
• Confusing an app update with an Agent Computer update — they are separate controls.