Where does the bug appear (feature/product)?
Grok Bot
Describe the Bug
Summary
On a Mac that stays on but is unattended, the local-exec daemon is stopped and never comes back. Chat keeps working; anything that needs my Mac fails until the desktop app is fully quit and reopened, and often a reopen does not bring the daemon back either.
Environment
- Grok Bot desktop 0.66.0, stable track, Apple Silicon
- macOS 27.0.1
- Mac never sleeps (sleep is prevented), Wi-Fi, no VPN or proxy
- Local tool permission: Always allow
- I work remotely from this Mac, so the screen is locked and there is no keyboard or mouse input for long stretches (about 21 hours at the time of writing)
What happens
- The app starts with two Node utility processes: the supervisor and the local-exec daemon.
- After some time the daemon exits. The main process, the window and the supervisor keep running.
~/.grokbot/local-exec-daemon.logshows a clean stop each time:
[sand-local-exec-daemon] received SIGTERM, shutting down- The daemon is not started again, including when I later message the bot and it needs the machine.
- A full quit and reopen sometimes restores it. Often the relaunched app also comes up with no daemon.
Daemon stop times (PDT)
- Oct 2, 10:25 AM, after about 15.5 hours up
- Oct 2, 6:42 PM, after about 6.5 hours
- Oct 2, 9:42 PM, 13 minutes after launch (the Mac had just rebooted)
- Oct 3, 8:30 PM, after about 11.5 hours
- Oct 4, 12:44 AM
- Oct 4, 3:06 AM
Restart behaviour
I run a small watchdog that quits and reopens the app when the daemon process is missing. Overnight on Oct 3 to 4 it restarted the app 69 times. Most relaunches came up with only the supervisor. The daemon did return after relaunches at 12:45 AM, 3:07 AM and 7:43 AM.
What I ruled out
- Network: 0% packet loss to router and internet at failure time, DNS fine, and the main process keeps making outbound connections
- Sleep: the Mac did not sleep
- Crashes: no crash reports, and the reliability session file shows
childDeaths: {} - Sign-in:
desktop-status.jsonshowssignedIn: true
Other lines in the daemon log
[user-computer-provider] poll failed: ConnectError[user-computer-provider] watch stream failed: ConnectError (ECONNRESET)[shell-exec] Close event did not fire within 5000ms after exit ... Killing detached process group.
My guess
This looks tied to the away or park state: the screen is locked and the window is unfocused, the daemon is retired, and it is not brought back when the bot next needs the computer.
Questions
- Is the daemon being stopped on a locked, unattended Mac intended?
- If so, should it restart on its own when the bot needs the machine? It does not for me.
- Is there a supported way to keep local exec available on an unattended Mac with the screen locked?
I can share the full daemon log and before/after snapshots from each restart (processes, connections, lock and idle state, network).
Possibly related: Grok Bot local-exec-daemon on macOS dies after staying healthy; Mac unreachable until leftover processes are killed (0.20.0, marked as fixed in a later release). I’m seeing similar behaviour on 0.66.0, but with a SIGTERM in the daemon log and a locked, unattended Mac.
Steps to Reproduce
- On a Mac that never sleeps, open Grok Bot desktop 0.66.0 and sign in. Set local tool permission to “Always allow”.
- Confirm local exec works: ask the bot to run a shell command on the Mac. Activity Monitor shows two “Grok Bot Helper” Node utility processes (supervisor and local-exec daemon).
- Lock the screen and leave the Mac unattended, with no keyboard or mouse input.
- Keep using the bot from another device. Let it finish its work and go idle.
- Wait. On my Mac the daemon stopped between 13 minutes and about 15 hours after launch.
- Check ~/.grokbot/local-exec-daemon.log. The last line is:
[sand-local-exec-daemon] received SIGTERM, shutting down
Only one Node utility process (the supervisor) is left. The main app and window are still running. - From the other device, ask the bot to run a command on the Mac.
Expected: the daemon starts again and the command runs.
Actual: the Mac stays unavailable. The daemon is not restarted.
- Fully quit and reopen the app while the Mac is still locked.
Expected: the daemon starts.
Actual: most relaunches come up with only the supervisor. Out of 69 automated relaunches overnight, only a few restored the daemon.
Frequency: 6 daemon stops in about 48 hours. I have not reproduced it on demand; the timing varies.
Operating System
MacOS
Version Information
Grok Bot Version: 0.66.0
Release Track: stable
Build date: 2026-10-01
Bundle ID: com.anysphere.sand
Electron: 42.1.0
Chromium: 148.0.7778.97
Node.js: 24.15.0
OS: macOS 27.0.1 (26A434), Darwin 27.0.0 arm64
Hardware: Mac16,5, Apple M4 Max, 128 GB RAM
Does this stop you from using Cursor
Sometimes - I can sometimes use Cursor