GrokBot Linux Execution on Local Computer not working

[Chen_Zhanfeng]

Where does the bug appear (feature/product)?

Grok Bot

Describe the Bug

Time: 2026-09-01 11:10 SGT / 03:10 UTC
ListMachines: {“machines”:} now, after restart, after full GUI kill, and on a new agent (LocalExec probe 74a73a1f-2903-4839-97eb-84286a2361a4)
This agent: Boss 186fb847-ca75-4e0a-ae8a-34fffd349bf9
Client: Linux, current computer name XPS-15, Execution = Always allow
Box hostname cursor, kernel 6.12.94+, uid box
Box exec-daemon: listening :1337, tracing off (hasTraceEndpoint: false, ghostMode: true), computerUseEnabled: true, workspace /workspace
Box-doctor: 10/10 pass (unrelated to laptop local-exec)

always allow already enabled

Steps to Reproduce

minimal session to produce this failure 74a73a1f-2903-4839-97eb-84286a2361a4

Screenshots / Screen Recordings

Operating System

Linux

Version Information

GrokBot LInux 0.30.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

[Colin]

Hey @Chen_Zhanfeng, thanks for the report!

This is a known issue on Grok Bot 0.30.0 on Linux and a fix is already merged. It ships in the next desktop update, so local execution should start working once you update.

If you want to try a workaround before the update:

1. Make sure a system keyring is installed and unlocked (gnome-keyring on GNOME/Ubuntu, KWallet on KDE). The helper needs it to store its machine identity.
2. Fully quit Grok Bot and check no leftover Grok Bot processes remain.
3. Relaunch Grok Bot