Grok Bot local-exec flaps between Windows and Mac when both desktop apps are open

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When Grok Bot desktop is open on Windows and macOS at the same time, local-exec does not stay on the machine the user is chatting from. There is no way to pin ExternalShell / local tools to one computer.

What happens:

  • Consecutive local commands in the same turn hit different machines (one Windows, one Mac)
  • After the target changes, later commands fail with “That action was not approved on the user’s computer”
  • This happens even with Settings → Bot → Execution on Local Computer = Always allow on both machines (localToolPermission: “always” in each machine’s settings.json, no team ceiling)
  • Host-side, approval is bound to a target-computer hash. If the target changes between review and execution, the host rejects with “The reviewed shell target changed before execution”
  • On Windows the local-exec daemon logged: discovery publish failed (previous record stands): Error (EPERM) — so the other machine’s daemon stayed the default discovery record
  • Closing the other Grok Bot session made both commands hit the intended machine and succeed

Expected:

  • Pin local-exec to the computer the user is chatting from, or keep a stable default for the turn
  • Do not fail later commands when two desktop sessions are open
  • Always allow should not be defeated by a host flap
  • The Windows daemon should be able to publish discovery without EPERM leaving a stale Mac record

Not a duplicate of:

OS: Windows 10/11 and macOS
Product: Grok Bot desktop

Steps to Reproduce

  1. Open Grok Bot desktop on a Windows machine and on a macOS machine at the same time, signed in to the same account.
  2. Set Settings → Bot → Execution on Local Computer = Always allow on both machines.
  3. From one chat, run two consecutive local shell commands in the same turn.
  4. Observe that the commands can land on different machines, and that later commands then fail with the not-approved error.
  5. Close the other Grok Bot session and re-run: both commands hit the intended machine and succeed.

Expected Behavior

Local-exec should stay pinned to the computer the user is chatting from (or keep a stable default for the turn), later commands should not fail when two desktop sessions are open, and Always allow should not be defeated by a host flap.

Operating System

Windows 10/11
MacOS

Version Information

Grok Bot desktop (latest), Windows 10/11 and macOS

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

6

Hi @evgbtrk!

Thanks fo reporting this!

This is a known behavior that can occur when a user has multiple desktop sessions open simultaneously. We’re aware of it and are actively tracking related reports, so I’ve gone ahead and added yours to the list.

In the meantime, keeping one desktop open (their workaround) is currently the only reliable mitigation.