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
- Open Grok Bot on Windows; confirm machine TIM-DESKTOP-2025 shows connected.
- Set Execution on Local Computer to Always Allow (also reproducible after trying Ask every time).
- Ask the bot to copy a file to the local PC (
CopyFromBox). - Observe failure: “Local tools are turned off. The user has set local tool access to Never…”
- Restart Grok Bot app, full PC reboot, delete
local-exec-daemon.jsonandlocal-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
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
SendFeedbackfailed: 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
