Grok Bot Computers / local-exec keeps dropping while Mac mini stays on

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Grok Bot

Describe the Bug

Grok Bot Computers / local-exec keeps dropping even though the Mac mini stays on and Computer settings look correct (Mac-mini.local, Always allow). Chat stays up, but the machine list flaps between connected and empty. Agents then fail mid-job with:

“Your computer Mac-mini.local is unavailable — it looks disconnected. Reconnect it (or focus the computer you want commands to run on) and try again.”

The local client is signed in when the link is up. This looks like a Grok Bot Computers-link bug.

Steps to Reproduce

  1. Pair a Mac mini with Grok Bot Computers (Always allow).
  2. Confirm the machine shows as connected.
  3. Leave the Mac mini powered on and keep the chat session open.
  4. Watch the machine list flap between connected and empty.
  5. Run an agent that needs local-exec.

Expected Behavior

The computer should stay connected while the Mac mini is on and Computer settings remain correct. The machine list should not flap empty, and local-exec should not drop mid-job.

Operating System

MacOS

Version Information

Grok Bot:
Version: 0.29.0
OS: darwin / macOS

Additional Information

Hostname redacted. Computer settings show the Bonjour .local name and Always allow. Chat remains up during the flap, so this looks like the Computers / local-exec link dropping rather than a full client sign-out.

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

5

Hey, thanks for the detailed report.

We tracked this down, and it is on our side, not your Mac mini. When the agent’s cloud environment goes idle, the helper process on your Mac could wrongly conclude the desktop app was gone and shut itself down, which is why the machine list flaps between connected and empty and jobs fail mid-run with the “unavailable” message even though the Mac stays on and your settings are correct.

A fix is already merged and will ship in the next Grok Bot release (after 0.29.0). Until then the drop usually heals on its own within a minute, so retrying the task shortly after the failure typically works. If a machine stays missing, quitting and reopening the Grok Bot desktop app reconnects it.

Sorry for the churn here, and thanks again for flagging it.