Grok Bot 0.71.2 cannot access local file system on Windows 11

Support Bug Reports
,
1

Hello,

Looking for some help with an issue I am having with Windows 11 Grok Bot. The app cannot access my local file system to place a file in my downloads folder. I am brand new to Grok Bot so please forgive me if I have missed something obvious to fix this. Any help is greatly appreciated! Thanks

Where does the bug appear (feature/product)?
Grok Bot Windows app / local computer tools (Execution on Local Computer, CopyFromBox / machine-targeted file access)

Describe the Bug
Local tools on my Windows desktop stay blocked as “Never” even though Settings → Execution on Local Computer is set to Always Allow. Grok Bot cannot copy files to my PC (CopyFromBox); every attempt fails with the backend saying local tool access is set to Never. UI and backend disagree.

Steps to Reproduce

  1. Open Grok Bot on Windows; confirm machine TIM-DESKTOP-2025 shows connected.
  2. Set Execution on Local Computer to Always Allow (also reproducible after trying Ask every time).
  3. Ask the bot to copy a file to the local PC (CopyFromBox).
  4. Observe failure: “Local tools are turned off. The user has set local tool access to Never…”
  5. Restart Grok Bot app, full PC reboot, delete local-exec-daemon.json and local-exec-daemon.log, log out and back in — retry; same error.

Expected Behavior
With Always Allow, local tools (CopyFromBox / Shell / Read with machineId) should work on the connected machine.

Screenshots / Screen Recordings

image
image966×772 29.5 KB

Operating System
Windows 11 Pro 25H2

Version Information
Grok Bot Windows app — Version 0.71.2. Grok Bot’s computer has been updated.

For AI issues: which model did you use?
N/A

For AI issues: add Request ID with privacy disabled
N/A

Additional Information

  • No Tailscale / extra VPN; no third-party firewall apps.
  • File Explorer open on Downloads does not affect it.
  • Upgraded from free account to X Premium / paid; previously used a different login.
  • Bot SendFeedback failed: unavailable in “privacy mode”.
  • I do not know what this “privacy mode” is, and neither does my bot.
  • Impact: cannot use local file access; chat attachments are the only workaround.

Does this stop you from using Cursor?
No - Cursor works, but with this issue

3

Hi there!

We detected that this may be a bug report, so we’ve moved your post to the Bug Reports category.

To help us investigate and fix this faster, could you edit your original post to include the details from the template below?

Bug Report Template - Click to expand

Where does the bug appear (feature/product)?

  • Editor, Tab & Chat (autocomplete, Composer, in-editor agent)
  • Terminal & commands
  • Models, pricing & API keys (availability, Auto/Max, BYOK/Bedrock)
  • MCP & tools
  • Cloud Agents & Automations (cursor.com/agents, scheduled/event)
  • BugBot & Code Review
  • Cursor CLI
  • Cursor Mobile
  • Remote (SSH / Dev Containers / WSL)
  • Account, billing & login
  • Something else…

Describe the Bug
A clear and concise description of what the bug is.

Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!

  1. …
  2. …
  3. …

Expected Behavior
What is meant to happen here that isn’t working correctly?

Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)

Operating System

  • Windows 10/11
  • MacOS
  • Linux

Version Information

  • For Cursor IDE: Menu → About Cursor → Copy
  • For Cursor CLI: Run agent about in your terminal
IDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......

CLI:
CLI Version 2026.01.17-d239e66

For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)

For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…

Additional Information
Add any other context about the problem here.

Does this stop you from using Cursor?

  • Yes - Cursor is unusable
  • Sometimes - I can sometimes use Cursor
  • No - Cursor works, but with this issue

The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!

12

The same issue is being reported on macOS here: forum.cursor.com/grok-bot-cant-run-local-tools-on-my-mac-setting-stuck-on-never-this-account-only-grok-bot-mac

I confirmed that my X, Grok, and Cursor are all on the same linked account. Since it happens on Windows and Mac, and only on one account, it looks like the problem is on the account or server side, not the local permission toggle. Restarting, rebooting, deleting the daemon files, logging out and back in, and updating didn’t fix it.