Where does the bug appear (feature/product)?
Grok Bot
Describe the Bug
Two related problems on Windows:
My project was on E:. Read fails there with “Path is outside the allowed local-exec root and was refused”. I understand from this thread that Read, CopyFromBox and CopyToBox are limited to C:\Users, while Shell is not. This worked for me before, and it stopped around Nov 4.
My C: drive was full, so I freed space and copied the project into C:\Users\hp. Grok Bot can now read the source files there. But when I explicitly authorize a small bug fix, it refuses to edit the code directly and says coding has to go through a Cursor Cloud Agent.
Execution on Local Computer is set to Always allow.
Steps to Reproduce
Register a Windows PC in Grok Bot 0.79.3, set Execution on Local Computer to Always allow.
Ask the bot to read a file in a project on E:\ and it is refused (outside allowed local-exec root).
Copy the project into C:\Users\hp\ and ask it to read a file, and it works.
Ask it to apply a small authorized bug fix in that project, and it refuses and points to a Cursor Cloud Agent.
Expected Behavior
Read/Copy tools should reach the same locations that Shell can (or the bot should use Shell automatically).
With explicit permission and Always allow, the bot should be able to apply a small edit to a local project, or clearly document that direct local edits are not supported
Operating System
Windows 10/11
Version Information
Version Information
Grok Bot 0.79.3 (Windows desktop)
Additional Information
Support ticket: T-J58264. The support bot could not say whether direct local edits are supported or what triggers the Cloud Agent redirect.
A junction from my profile to E: is not an option, since the check uses the real path (per Dean Rie in the thread above).
Related: Read/CopyToBox refuse D:\ paths while Shell works
Does this stop you from using Cursor
Sometimes - I can sometimes use Cursor