New report, Windows, leftover daemon on 0.30.0

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Grok Bot

Describe the Bug

Grok Bot desktop on Windows loses the local-computer link after the app has been healthy. Same failure sequence as the macOS local-exec-daemon report. Still happening on 0.30.0 after @Colin said 19 Aug a fix was ready for the next release.

The PC is reached through a detached local-exec daemon:

%LOCALAPPDATA%\Programs\Grok Bot\Grok Bot.exe
%LOCALAPPDATA%\Programs\Grok Bot\resources\app.asar\dist\local-exec-daemon\main.cjs

Relaunching the app does not kill the previous daemon. Leftover local-exec-daemon and crashpad-handler processes keep running. Agents cannot recover this themselves because local Shell is that dead channel. Cloud/box side keeps working.

Failure sequence (same session, 31 Aug 2026, America/New_York):

Stale / dropped host while the provider is still registered: Your computer “Ian-PC” is unavailable — it looks disconnected. Reconnect it (or focus the computer you want commands to run on) and try again.
Then no providers: Your local machine isn’t connected right now (the Grok Bot desktop app must be open and online to run commands on it).
The registered-computer list then returned empty (machines: ) while the desktop app was still open.
Registered computer label is Ian-PC, not anonymous.

Steps to Reproduce

Steps to Reproduce
Open Grok Bot desktop 0.30.0 on Windows. Leave it running.
Confirm the PC is reachable from a Grok Bot agent (a trivial local command succeeds). Confirm a local-exec-daemon process is up. Command line looks like: Grok Bot.exe …\resources\app.asar\dist\local-exec-daemon\main.cjs
Quit/relaunch or otherwise start a second Grok Bot instance without killing leftover processes. In this session:
1:53pm first launch: local-exec-daemon pid 4744, crashpad-handler pid 51460
2:21pm second launch: main pid 24460, new local-exec-daemon pid 7284. The 1:53 daemon and crashpad were still running.
2:35-2:37pm: local commands on Ian-PC still succeeded (listed files, read a script).
2:39pm: computer list still reported Ian-PC connected: true. The next Shell on that machine failed with the disconnected error above, then the app-must-be-open error, then an empty computer list.
I did not quit the app. It came back later without me killing leftovers. After the drop, both daemons were still running (1:53 leftover + 2:21 current).

Expected Behavior

One local-exec-daemon. Leftovers cleaned on relaunch. While Grok Bot desktop is open, the PC stays reachable. A missed ping should not empty the computer list or require killing leftover processes by hand.

Operating System

Windows 10/11

Version Information

Grok Bot desktop 0.30.0 (Electron 42.1.0), Windows.
App path: %LOCALAPPDATA%\Programs\Grok Bot\Grok Bot.exe
This is Grok Bot desktop, not Cursor IDE / CLI / iOS.

For AI issues: which model did you use?

N/A. Local-exec daemon / Windows computer connection.

For AI issues: add Request ID with privacy disabled

N/A. No public Request ID.

Additional Information

Related: Grok Bot local-exec-daemon on macOS dies after staying healthy; Mac unreachable until leftover processes are killed (macOS; staff said a fix was coming 19 Aug). This is the Windows leftover-daemon case on 0.30.0.

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

5

My org recently started using GrokBot, pretty amazing honestly, way better than Claude garbage. Only issue is this “Ian-PC” disconnected, kinda flickers every once in a while even though I never close the app on my PC

This is my first bug ticket hopefully its okay

6

Hey @Ian_Herzing, thanks for the detailed report, and sorry for the trouble here.

To clarify the earlier message on the macOS thread: improvements did ship in 0.30.0, and they resolved one specific failure (the daemon exiting cleanly and never being respawned). What you’re hitting on Windows is a different failure path in the same area. It’s a known issue we’re actively tracking, and I’ve added your report (including the leftover process details, which are genuinely useful) to it.

In the meantime, when the machine becomes unreachable, this should recover it:

  1. Fully quit Grok Bot (right-click the tray icon and choose Quit, rather than just closing the window).
  2. Open Task Manager and end any remaining “Grok Bot” processes, including any local-exec-daemon entries.
  3. Relaunch Grok Bot and wait about a minute for your PC to re-register.

You shouldn’t need to do this, and cleaning up leftover processes on relaunch is part of what we’re working on!

9

Thanks, @Colin — Sorry for my AI-slop message. Great that this is being tracked, really love GrokBots.

Cheers!!!

10

Related, but not the leftover-daemon drop after it was working.

Grok Bot 0.36.0 / Windows. Settings → Execution on this computer = Always allow. Chat works.

I have never had a successful local command. Not after install, not after reboot, not after Sign out / Sign in, not with VPN off. The computer list often shows connected: true, then the next local command fails immediately with:

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

The helper process is running. Task Manager: 10x Grok Bot.exe (one Electron instance). One of them is:

…\Grok Bot\resources\app.asar\dist\local-exec-daemon\main.cjs

Only one daemon, no leftovers. Killing all Grok Bot processes and launching once still never lets a local Shell land.

So this is: daemon alive, UI says connected, local execution has never worked. I need the bot to read local disks.

11

@Jarri81 Instead of tagging onto this thread, please start a new one!