Grok Bot 0.57.1 Windows — app quits under local Shell/CopyFromBox + Chrome UI; idle stays up

Support Bug Reports
, , ,
1

Where does the bug appear (feature/product)?

Grok Bot

Describe the Bug

Describe the Bug

Registered local computer shows connected. Light Shell works for hours when idle. When agents run heavier local work — especially CopyFromBox of a PowerShell script into %TEMP% then Shell that focuses Chrome (Win32 SetForegroundWindow + F5 for Mindbody keep-alive) or QBP browser automation — ListMachines flips to disconnected and the Grok Bot window vanishes. No Application Error / WER crash dump. Sentry queue empty. Full uninstall + delete install folder + fresh install from x.ai/bot did not fix. Over-the-top reinstall of 0.57.1 did not fix.

Steps to Reproduce

Pattern

  1. Idle / light hostname Shell: OK (observed 3+ hour continuous session after clean reinstall)
  2. CopyFromBox + longer Shell / Chrome UI automation: dies within seconds; window gone
  3. Startup relaunches app → open→die loop until full reboot + reinstall calmed idle path
  4. Chrome itself briefly flashed then closed once when app died mid-automation

Expected Behavior

Light Shell should remain stable for hours when idle, and heavier local work—especially CopyFromBox followed by Shell and Chrome UI automation—should complete without ListMachines disconnecting or the Grok Bot window vanishing. Chrome should remain available for the requested automation.

Operating System

Windows 10/11

Version Information

Version: Grok Bot 0.57.1 x64 — C:\Users\greshfit\AppData\Local\Programs\Grok Bot\

Additional Information

Title: Grok Bot 0.57.1 Windows — app quits under local Shell/CopyFromBox + Chrome UI; idle stays up

Where: Grok Bot desktop (Windows)

OS: Windows 11 (10.0.26200), machine hostname SERVICE, Intel i5-8500T, ~16GB RAM, Wi-Fi only, Windows Defender only (no third-party AV)

What we already tried

  • Confirmed Windows sleep/hibernate/display Never on AC (not a PC power issue; last OS reboot was Windows Update Sep 16 before today’s reboot)
  • Clean uninstall + delete Programs\Grok Bot + reinstall 0.57.1
  • Paused Mindbody keep-alive that CopyFromBox’d scripts to Temp
  • Redirected user TMP/TEMP to %LOCALAPPDATA%\\Grok Bot\\tmp
  • Defender ExclusionPath add failed (non-admin shell)
  • Filed Help → Send Feedback from the app (privacy mode blocked agent SendFeedback)

Related reports we found

  • forum.cursor.com: “temporarily unreachable” on Windows (AV scanning Temp ps-scripts, 10s timeout)
  • forum.cursor.com: leftover local-exec-daemon after quit/relaunch
  • forum.cursor.com: connected but file I/O unusable; timeout removes machine ~1 min
  • X: users hitting Windows tray Quit vs X-close leaving daemons (Grok replied with Task Manager cleanup)

Ask

Please treat Windows local-exec under CopyFromBox + UI automation as a P0 shop-floor case. Happy to attach daemon logs / timings if you tell us the path.

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

6

Hey @Timothy_Gresh,

Since the idle path is stable for hours and it only dies during the CopyFromBox + PowerShell + Chrome automation, the most likely cause is your endpoint security ending the Grok Bot process (on Windows there’s no tray, so ending the process closes the app and drops the connected computer - which matches “no crash, goes disconnected”). Quick way to confirm and unblock: from an admin account, add a process exclusion for Grok Bot.exe plus a temporary folder exclusion for your Temp path in Windows Security, then run the same automation once. If it stays up, that’s it.

Two things that pin it down if it still dies:

  1. The moment the window vanishes, check Task Manager → Details for any Grok Bot.exe still running (tells us “quit” vs “lost its window”).
  2. Windows Security → Virus & threat protection → Protection history - any entry from that same minute naming a script or Grok Bot.

Reply back with what you see and I’ll take it from there. This isn’t intended behavior and it’s not something you’ve misconfigured.