Grok Bot 0.20.0 Windows: local bridge 404 and stuck Working after Reset

Where does the bug appear (feature/product)?

Grok Bot

Describe the Bug

Grok Bot 0.20.0 Stable on Windows 11 cannot use ExternalRead on the local PC. The app and local-exec-daemon run, permission is Always allow, but the daemon drops responses after 3 failed POSTs (http_404). Reset and official reinstall did not fix it. Update Grok Bot’s Computer stays grey because an agent stays Working.

Steps to Reproduce

  1. Open Grok Bot 0.20.0 Stable on Windows 11. Set Execution on Local Computer to Always allow.
  2. Ask a Bot to ExternalRead a local file (not Read/Shell, not Grok Bot’s Computer, not Cursor Cloud).
  3. Watch %USERPROFILE%.grokbot\local-exec-daemon.log. Responses are dropped: Error (http_404). inflightCount stays 0 if the Bot only says it is testing.
  4. Tell the Bot to stop all agents. One stays Working. Agent Computer shows no approval.
  5. Settings → Updates: Update Grok Bot’s Computer stays grey. Reset, then reinstall from cursor.com/bot/onboarding. ExternalRead still fails.

Expected Behavior

ExternalRead returns the real local file and host id MARIA. A live daemon does not 404-drop responses. After agents stop, Working clears and Update Grok Bot’s Computer is enabled. Stale sessions repair without Reset. Reinstall is not required for a bridge bind failure.

Operating System

Windows 10/11

Version Information

Grok Bot 0.20.0 Stable on Windows 11 Home 10.0.26200 (hostname MARIA)

For AI issues: which model did you use?

Grok Bot built-in agents (Chief of Staff). Not a Cursor IDE model picker issue.

Additional Information

Hostname MARIA. localToolPermission=always. Live daemon log after Reset/reinstall: 24 starts, 8 http_404, 1 TypeError, 2 desktop-ownership-lost. inflightCount stays 0 during “Testing now”. Docs say Settings → Beta; 0.20.0 UI is Settings → Updates. I can attach a sanitized daemon log. No tokens, VNC URLs, or credential files.

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hi @Maria_Martins!

Thanks for the report, and sorry you’re running into this! I expect this issue will be resolved in the next version of Grok Bot to be pushed out.