Grok Bot (macOS): sign-out/sign-in loads an empty new environment while the iOS app still lists the same bots

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Grok Bot

Describe the Bug

After a connection drop mid-task on the macOS desktop app, signing out and back in with the same account left the app showing a brand-new environment: no bots, no conversation history, no /workspace files. I never ran a Reset on the Agent Computer - the only actions were quit, sign out, sign in.

The state does not appear to be gone server-side. The iOS app, still signed in from before the incident, continues to list the same bots and their conversations. So the same account renders a populated environment on iOS and an empty first-run environment on macOS.

Since then the macOS app has gotten worse: it now errors out during sign-in and will not load at all.

I have deliberately not created new bots or changed anything inside the empty environment, in case that would overwrite recoverable state.

Steps to Reproduce

  1. Be mid-task in the Grok Bot macOS app, with the bot showing as working.
  2. Lose the connection to Grok Bot while the rest of the network stays up. Outgoing messages stick on “Enviado sin conexion” / “Se enviara al reconectarse” (sent offline / will send on reconnect). Other services (Claude Code, Codex) kept working normally throughout, so this was not local connectivity.
  3. Fully quit the app.
  4. Sign out, then sign back in with the same account.
  5. The app loads the new-user home screen: no bots, no conversations, no files.
  6. Open the iOS app on the same account (still signed in from before the incident) - the bots and conversations are still listed there.

Happened once, on 31 Aug 2026 at roughly 18:35-18:45 UTC-3. I have not tried to reproduce it deliberately, for obvious reasons.

Expected Behavior

Signing out and back in on the desktop app should re-attach the existing Agent Computer to the account, not present an empty environment. At minimum, a client that cannot reach the existing environment should say so explicitly, rather than rendering a first-run state that is indistinguishable from data loss.

Operating System

MacOS

Version Information

macOS desktop: version unavailable - app fails at sign-in / never reaches About Grok Bot
iOS: Grok Bot 1.4.0 (6495)

Additional Information

The iOS app on the same account still listing the bots is the main clue: it suggests the state exists server-side and this is a desktop client / session-attachment problem rather than actual data loss.

Grok Bot desktop unusable; Cursor IDE unaffected.

Has anyone else seen a desktop client render an empty environment while another client on the same account still lists the bots? And is a sign-out/sign-in on macOS expected to detach the existing Agent Computer at all?

I can share screenshots of the offline-send state, the empty post-login screen and the current desktop sign-in error if that helps narrow it down.

Existing email ticket: T-F31917 (no Reset/Recover/Update Computer used; iPhone session left signed in).

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

Hey, thanks for the detailed report, and good call not touching anything in the empty environment.

Good news: your bots, chats, and files are still there. The fact that iOS on the same account still shows the bots confirms the state is still on the server, so this is a display issue in the desktop client, not data loss.

Signing out and back in on macOS shouldn’t unlink your Agent Computer. What you’re seeing is a known issue we’re tracking: when the client can’t reach an existing environment, the desktop app falls back to the new-user setup instead of clearly saying it can’t connect. That’s also why you get the “Can’t reach your computer” error when you try to go through setup.

For now, please leave everything as is: don’t complete the setup, don’t create a new bot, and don’t use Reset or Recover. Your instinct is right, this way nothing will get overwritten.

I’ve passed this to the team so they can restore access to your environment on our side. I’ll reply here as soon as I have an update. Once access is back, fully quit Grok Bot on both Mac and iPhone, then reopen the Mac app and sign in, your bots should show up.

If the Mac still shows the new-user screen after that, reply in the thread and send the version from Grok Bot > About Grok Bot.

8

Hey @Axelriveroc update: your computer is back up and your data is intact. You’re good to go now: fully quit Grok Bot on both your Mac and iPhone, then reopen the Mac app and sign in. Your bots, conversations, and files should be listed again.

If the Mac still shows the new-user screen after fully restarting both apps, reply here with the version from Grok Bot > About Grok Bot and I’ll take another look.

9

Hii, hace un ratito se volvio a desconectar.

image
image2130×1516 305 KB