Grok Bot 0.30.0 — Agent Computer unreachable after Update, Recover, and Reset all failed

Where does the bug appear (feature/product)?

Grok Bot

Describe the Bug

All Grok Bots on this account are unreachable on Mac and iPhone.
Errors:
• iOS: “Can’t reach your computer. Your Bots are safe — they just can’t be loaded right now.”
• Mac: “Reconnecting to your compute…” / “Can’t reach [Bot]’s screen”
• Update failed: “The update couldn’t finish. Agent Computer is still on its previous image.”
• Recover failed: “The recovery couldn’t finish, so Grok Bot’s computer may still be unreachable.”
• Reset reached “Starting Grok Bot’s computer” at 50%, then “Taking longer than expected,” then fell back to Update failed again.
Started ~11:35 AM PDT on Sept 1, 2026. Still down as of 1:29 PM PDT.
Need the Agent Computer rebuilt on your side. Client-side Update / Recover / Reset did not attach.

Steps to Reproduce

  1. Open Grok Bot 0.30.0 Stable on Mac.
  2. Computer is unreachable.
  3. Settings → Updates → Update Grok Bot’s Computer. Sticks at 43% Transferring your data, then Update failed.
  4. Recover computer. Recover failed.
  5. Quit and reopen. Update retries and fails at 43% again.
  6. Settings → Updates → Reset Grok Bot’s Computer. Sticks at Starting 50% / taking longer than expected, then Update failed again.
  7. iOS on the same account shows the same “Can’t reach your computer” state.

Expected Behavior

Agent Computer becomes reachable. Bots and screens load on Mac and iPhone. Files and logins preserved.

Screenshots / Screen Recordings

Operating System

MacOS
iOS

Version Information

Grok Bot 0.30.0
Release track: Stable
App reports “You’re up to date”

For AI issues: which model did you use?

Built-in Grok Bot / Agent Computer (not a Cursor IDE model issue)

Additional Information

Bot involved: Ask Atlas - Grokbot Product
Timezone: PDT
In-app Send Feedback submitted with conversation ID and request-a-response checked.
Please restore the Agent Computer on the backend. Do not want another client-side Reset.

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hi @Van_West Sorry about the inconvenience here. I’ve performed a reset and update of your Grok Bot’s computer from our side. Everything looks good now from my side! Please check and let me know if you are facing any issues.

Hi @kevinn i have the same problem

Hey @Reiss, thanks for the screenshot.

Your situation looks different from Van’s. I checked your Grok Bot computer from our side and it’s up, reachable, and your data is intact. What your screenshot shows is Chrome crashing inside your bot’s computer (the “Aw, Snap!” page is the bot’s browser, not yours), which lines up with the computer waking up from idle a few minutes earlier.

A couple of things to try:

  1. Click Reload in that tab on the bot’s screen, or just ask the bot to reload the page. If the bot isn’t responding at all, fully quit Grok Bot (Cmd+Q) and reopen it.
  2. Please don’t run Update, Recover, or Reset from Settings. Nothing on your computer needs rebuilding, and those won’t help with this.

One thing worth knowing: your computer goes to sleep when it’s idle and takes a moment to wake up. A message sent right as it’s waking can occasionally not go through. If that happens, sending it again is safe.

If you’re still stuck after that, reply with exactly what you see (for example “Can’t reach your computer”, “Reconnecting”, or the bot just not answering) and the request ID from the error tray, and I’ll take another look.

Thanks Kevin - i did this and then now im getting this - Still no. Memory is just as tight (117 Chrome processes, ~450MB free), and Vente is back on the sign-in page. Another export run would crash the same way.

The 434 leads from earlier are still good. To finish the other 6 lists plus Unactioned, Update Grok Bot’s Computer then sign in once.

127 Chrome processes across all your agents are using about 16.5GB on a 15GB machine, with ~400MB free. That’s what’s throwing the Error Code 9 crashes, and the last crash knocked Vente back to the sign-in page.

Hi @Reiss I can try and update and reset from my side. Will push the update thru.

thanks kevin you’re a legend! loving grok btw

Hey @Reiss, your bot’s read is right: the computer was out of memory, not crashing on wake. All your agents share one computer with a fixed amount of RAM, and several of them running browser work at once was enough for the system to start shutting down Chrome. That’s the Error code 9, and it’s what kept logging you out of Vente. Nothing on your end caused it, and it’s an issue we’re tracking.

I’ve rebuilt your computer from our side. It’s on the latest version with memory back to normal, and your files, bots, and the 434 leads are intact. You’ll just need to sign in to Vente once more.

Let me know if this sorts everything out!

Thanks Kevin - could we increase the memory?