Grok Bot: backup transfers refused on D: and E: despite successful folder creation

I need help backing up project work from the bot’s computer onto my two Windows PCs, using supported tools and narrowly scoped permissions.

Before the newest update, we were able to transfer project files to these PCs. This restriction appeared afterward. Could support confirm whether this is a regression, an intentional permissions change, or a configuration issue?

On November 8, 2026, the recorded results showed:

  • Folder creation through Shell reported exit code 0 on each PC.
  • The first CopyFromBox transfer on each PC failed with: “Path is outside the allowed local-exec root and was refused.”
  • Zero transferred bytes are confirmed. Partial-file existence is unknown because no inspection was attempted after the refusals.
  • Both sequences stopped immediately. No retries, alternate transports, or security bypasses were attempted.

The attempted destinations were on E: and D:, nested under an existing project’s backup directory. Redacted examples are E:\OtherProject\backups\CurrentProject\<checkpoint>\ and the equivalent on D:. These attempts do not establish whether separate project-root destinations would be permitted.

A checkpoint remains on the bot’s computer, but I need recovery copies physically on my own PCs. Successful folder creation clearly did not establish permission for the transfer tool.

Could support clarify:

  1. What is the documented way to authorize specific project backup folders for CopyFromBox and related read/transfer tools?
  2. Do Shell and file-transfer tools intentionally enforce different path restrictions? Where can I inspect their effective permissions?
  3. Is this expected configuration behavior or a known issue? If a fix is needed, could you provide a tracking reference?

Separately, I’ve encountered chat attachments readable in the original conversation but unavailable at their supplied paths to other workers. What is the supported way to make those original files available for verification? I’m not claiming this caused the backup failures.

I’m asking for supported, project-scoped access—not disabling security checks. I can provide redacted execution receipts if needed.

1 Like

4 posts were merged into an existing topic: Grok Bot CopyToBox/Read refuse D:\ paths (“outside the allowed local-exec root”) while Shell works