Grok Bot: host computer channel stays disconnected after app restart

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Grok Bot

Describe the Bug

Where: Grok Bot desktop (Mac), early beta.

Chat with the agent still works, but commands on my local machine fail with: “Your local machine isn’t connected right now (the Grok Bot desktop app must be open and online to run commands on it).” Sometimes also a message that my MacBook Pro host (name ending in “.local”) is unavailable.

Only the local-machine command channel is dead; chat/messaging keeps working the whole time. This is NOT the cloud “Grok Bot’s Computer” (box) failing — it’s the link to my own Mac.

Steps to Reproduce

  1. Agent is using my Mac (External/local machine) for git/file work.
  2. The host computer channel drops mid-session.
  3. I restart the Grok Bot desktop app and tell the agent it’s restarted.
  4. Agent retries immediately; still reports disconnected, for many minutes.
  5. Chat/messaging continues to work the whole time — only the local-machine command channel is dead.
  6. Sometimes a later retry or a second restart brings it back.

Expected Behavior

After the desktop app is open and online again, the host computer channel should reconnect promptly — without waiting a long time or needing a second restart.

Operating System

MacOS

Version Information

Grok Bot desktop app for macOS, early beta (current build as of 2026-08-19)

Additional Information

Observed twice on 2026-08-19 (afternoon and night, America/New_York) on macOS.

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

6

Thanks for flagging this @diaoguoliang!

This looks like the issue reported over here (Grok Bot local-exec-daemon on macOS dies after staying healthy; Mac unreachable until leftover processes are killed - #4), and we have some fixes in the pipe to improve this. Let us know if the behavior persists once we cut the next release.