Windows Grok Bot desktop can’t load an existing Walter conversation; sidebar and mobile still work

[John_Millard]

Where does the bug appear (feature/product)?

Grok Bot

Describe the Bug

On the Windows Grok Bot desktop app, one existing conversation with my bot “Walter” will not open. The main pane stays empty/dark, then after sign-out/sign-in it shows:

“Couldn’t load conversation”
“Couldn’t load this conversation. Check your connection and try again.”

The sidebar still lists Walter and shows live message previews (including new lines). I can still see the composer (“Message Walter”). The same conversation loads and works fully on mobile. New rooms on the same Windows app work normally.

I signed into Grok Bot with X. Sidebar account name is John Millard.

This does not look like “Can’t reach your computer.” I did not Reset or Recover the Agent Computer.

Steps to Reproduce

1. Open Grok Bot on Windows, signed in (X login). Bot “Walter” and other rooms appear.
2. Open the existing main Walter conversation.
3. Result: message pane is blank/dark. Sidebar previews for that bot still update. Sending from desktop previously worked; replies showed in the sidebar only.
4. Fully quit via Task Manager (no tray Quit option). Relaunch. Same room still blank.
5. Sign out and sign back in with the same account. Same room now shows “Couldn’t load conversation” with Retry. Retry does nothing.
6. Rename %APPDATA%\Roaming\Grok Bot to Grok Bot.bak, relaunch so a fresh Grok Bot folder is created. Same error on that room.
7. Open a new room on desktop: conversation loads and works.
8. Open the original Walter thread on mobile: full history and chat work.

Expected Behavior

The existing Walter conversation should load in the desktop message pane the same way it does on mobile, and the same way new rooms already do on this PC. Sidebar previews and the cloud conversation should match the open thread.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

Version: 0.43.0
Release Track: stable
OS: win32

Additional Information

Signed into Grok Bot with X. Sidebar account: John Millard.

Broken room: existing conversation with bot “Walter”.
Desktop: sidebar previews update; main pane “Couldn’t load conversation”.
Mobile: same thread loads and chat works.
New rooms on this Windows app work.

Already tried (no Reset/Recover of Agent Computer):

• Close window vs full Task Manager kill of Grok Bot
• Sign out / sign in
• Retry on the error screen
• Renamed %APPDATA%\Roaming\Grok Bot → Grok Bot.bak; app created a new Grok Bot folder; error remains

Please do not reset the Agent Computer unless you confirm it is required. Bots and other conversations are fine.

Does this stop you from using Cursor

No - Cursor works, but with this issue

[Bradley_Street]

Dont reset.

This is an issue affecting a lot of people. Dealing with the same problems on my account and my wifes account.

Just having to talk to it as normal on my computer and use my phone to see all replies.

[deanrie]

Hey, thanks for the detailed report, and especially for the comparison with mobile. That narrowed it down right away.

You read it correctly. This isn’t “Can’t reach your computer”, and Walter itself is fine. Your bot is receiving and replying to the messages you send from the Windows app, which is why the replies show up in the sidebar preview and on your phone.

The issue is on the desktop app side. It can’t render this specific existing conversation, which is why you see “Couldn’t load conversation”. New rooms open normally. This isn’t related to your PC, account, or settings.

Please don’t do Reset or Recover for Agent Computer, and don’t reinstall or clear app data again. None of those touch the root cause, and your conversations and bots are safe.

While we’re fixing this, the workaround is to keep using this Walter thread on mobile, or start a new room with Walter on desktop. Messages you send to Walter from the Windows app still reach it, even if the panel doesn’t refresh.

We’re tracking this issue and I’ve passed it to the team. I can’t share an exact timeline yet, but I’ll reply here as soon as I have an update.