Where does the bug appear (feature/product)?
Grok Bot
Describe the Bug
Grok Bot’s built-in file reader on my Windows laptop refuses E: paths with:
“Path is outside the allowed local-exec root and was refused.”
This affects both an existing ordinary file on E: outside the workspace mount and a file under E:\projects\app. Both failed after an app update on 7 November. Restarting did not resolve it either.
A Shell-based workaround was also refused by the assistant. Separately, our teammate reports successful E: file access through Codex’s approved local terminal—not Grok Bot’s built-in reader. This points toward a Grok Bot access-scope difference, but does not establish the exact cause.
Has anyone found a supported way to make the built-in reader accept E: paths, or to view and adjust its allowed local-exec root? Is a documented scope grant or reauthorization available?
We checked these two existing discussions and found no confirmed fix as of 7 November, 2:50 PM IST:
Read and Copy refusal outside the user profile
Other-drive paths refused while Shell works
We’re looking for a supported solution, not a way to bypass the restriction.
Steps to Reproduce
Ask Grok Bot’s built-in reader to read a file inside the mounted workspace; it succeeds. 2. Ask it to read an existing E: file outside that workspace. 3. It refuses with ‘Path is outside the allowed local-exec root and was refused.’
Expected Behavior
Grok Bot’s built-in reader should read approved E: files outside the mounted workspace, just as it reads files inside the mounted workspace, or explain how to grant the required access. This affects all agents — each has its own workspace on the E: and F: drives, and all have stopped working.
Operating System
Windows 10/11
Version Information
Grok Bot desktop app: 0.79.3
Operating system: Windows 11 Home Single Language (10.0.26300)
The issue occurred after updating Grok Bot on 7 November 2026.
For AI issues: which model did you use?
Grokbot default
Additional Information
This affects all agents with workspaces on E: and F:, blocking their normal work. Codex’s approved local terminal can read the same files. Support ticket: T-J43592. Restarting did not resolve it.
Does this stop you from using Cursor
Sometimes - I can sometimes use Cursor