Fix Grok Bot when chat works but local Shell is dead

The Bot’s computer is a cloud computer. Files and commands on the Mac or Windows PC in front of you run only when Execution on Local Computer is enabled and you approve the card. Chat can look fine while that local helper is dead.

Check the local-execution policy

1. Open Grok Bot.
2. Go to Settings → General → Agent → Execution on Local Computer.
3. Set Ask every time (docs also name this as the default). Use Are always allowed only if you accept that risk. Are never allowed blocks local Shell and local files.
4. Approve the Auto-review card. It shows the exact command.

Official troubleshooting for Local computer work is refused is this policy review. Cloud work does not use the toggle.

Leftover helper after an update (Windows)

Cursor staff (Sep 1, 2026) documented a leftover local-exec-daemon on Windows after 0.30.0. 0.30.0 cleaned one macOS path. The Windows leftover is a different failure, still tracked.

1. Fully quit Grok Bot: right-click the tray icon → Quit. Closing the window leaves the helper running.
2. Open Task Manager. End remaining Grok Bot processes, including local-exec-daemon.
3. Relaunch Grok Bot. Wait about one minute for the PC to re-register.
4. If local access is still missing: sign out and sign back in (staff: this recreates the helper). Check for an app update. Staff mentioned 0.31.0 rolling out as of Aug 29.

Staff described this as the helper reconnecting after an update.

Mac: helper timeout

Cursor staff: a timeout on a command or file copy can drop the machine from the agent list for about one minute. Settings can still show connected. “No registered machines were available when this turn started” is expected. The machine set is fixed at turn start. Send a new message.

If it stays stuck:

1. Quit with Cmd+Q.
2. In Terminal: pkill -f local-exec-daemon
3. Reopen Grok Bot.

Pitfalls

• The first local action asks for consent. Every local action still goes through Auto-review.
• Team-admin ceiling for local execution is documented as Coming soon.
• A Settings “connected” row can lag a dead helper. After a timeout, wait a minute, then send a new message.
• Blank, black, or “Can’t reach your computer” is the cloud computer. See Fix Grok Bot “Can’t reach your computer”.