Why does Grok Bot refuse files on my D: drive ("outside the allowed local-exec root")?
Last checked October 29, 2026 · Grok Bot changes often
Staff confirmed on October 29, 2026 that on a connected computer the file tools Read, CopyToBox and CopyFromBox only work inside your user folder (C:\Users\<you> on Windows), while Shell is not limited that way. Allowing local execution, even "Always allow", does not widen it, there is no setting to add other drives, and a junction pointing at D:\ is refused too. Workaround: read with Shell (Get-Content), or copy the file into your profile first.
The error
Path is outside the allowed local-exec root and was refused
It appears when a Bot on a registered Windows PC tries to read or copy a file under a second drive, for example D:\project\package.json, while the same path works through Shell.
What staff said
- Read, CopyToBox and CopyFromBox are limited to your user folder on a connected computer. Shell is not.
- Choosing Allow or Always allow for local execution does not change that, and no setting adds other folders or drives.
- A junction inside your profile that points to
D:\does not help, because the check follows links. - The team knows about it and the report was added to the request.
Workarounds from staff
- Reading: tell the Bot to use Shell for anything on D:, for example
Get-Content D:\project\package.json, which prints the file into the output. Ask it to remember this so it stops trying Read first. - To the Bot's computer:
Copy-Itemthe file into your profile, then CopyToBox it. - From the Bot's computer: CopyFromBox into your profile, then move it with Shell.
If the tools report that local tools are set to Never, that is a different problem: Grok Bot says local tools are set to "Never". For a Bot that cannot reach your PC at all, see Can't reach your computer.
Not tested by Boterly
We have not tried this on a live Bot. The report was for Windows; we found no staff statement about macOS or Linux behaviour, so do not assume the same limit applies there.