Is Grok Bot blocking local files and file:// pages? What we tested

Yes, the Bot's own browser blocks file:// pages, but there is no official list of these restrictions, so we tested what we could.

All Grok Bot questions: https://www.soundminds.ai/faq.

Last updated Nov 10, 2026

Part of our Grok Bot Hot Topics series

Short answer

Yes, the Bot's own browser blocks file:// pages, but there is no official list of these restrictions, so we tested what we could. I didn't find one in SpaceXSI's Grok Bot docs, Cursor's Grok Bot FAQs page, or the Nov 6, 2026 Grok Bot changelog entry.

In our test, Nov 10 2026, both the Bot's browser and its page-fetch tool refused those pages, and asking the Bot to read the same file directly worked. Several users report that on Windows, files outside their user folder are refused with an "outside the allowed local-exec root" error. On my Mac, copying a file to /tmp, outside my home folder, worked without that error. We haven't tested a Windows PC yet.

What users are reporting (not official)

These posts on X are from Nov 7 to Nov 9, 2026, and we haven't verified them unless our test confirms them.

• Several users report that on Windows, reads or copies outside their user folder fail with "outside the allowed local-exec root" (@Mattrl, @dodeesJH, @jbrianfrancis, @meixiangjiying). @Mattrl says reads inside their user folder still work, and @jbrianfrancis says there's no setting to add other drives or folders.
• @StarmanPatriot reports that the Bot now refuses to run a PowerShell script that starts Grok Build.
• @pvieito reports that the Bot won't read other apps' data on their computer, even with access granted.
• @JacobGo69586731 reports that since Nov 7, the Bot's browser blocks page JavaScript (page.evaluate) and file:// pages with "Blocked by Playwright proxy." We got the same wording for file:// pages in our test.
• @Laff2Death reports that a new browser restriction blocks their local game testing, and says staff told them it's intentional.
• @mariannehere asked whether Grok Bot's new update stopped uploads from the Bot's browser.

What I found on the official pages

The Nov 6, 2026 changelog entry (v0.79.3) has no new browser, file:// or local-folder rule. Two lines come close. One is an improvement: "When the usual page fetch fails, the Bot reads the page directly instead of opening it in a browser." The other is a fix, not a restriction: "With a team selected, Always allow on a local command saves, and your computer is no longer listed as Another computer."

Working on your own computer is a separate capability that needs your approval. I checked SpaceXSI's Use the computer and apps page, and it says, "A Bot only runs commands on your local computer when that capability is enabled and you approve it under your local-computer policy: per-command approval with Ask every time by default, or Always allow or Never allow." On a team, there's one more layer. SpaceXSI's Approvals, security, and privacy page has this line: "Your team admin can cap this setting for the whole team; when the team's policy is stricter than yours, the team's applies."

That setting has a known bug, described on Cursor's Grok Bot FAQs page: "A Bot may say "Local tools are turned off. The user has set local tool access to Never." even though Execution on this computer is set to Always allow or Ask every time." Cursor's team is working on a fix, and until then: "Your setting is correct, and there is nothing you need to change."

I didn't find file://, page.evaluate, a Playwright proxy, or an "allowed local-exec root" on any of these pages.

What we found in our test, Nov 10 2026

We used only throwaway test files.

Every command we sent to my Mac ran, though I can't tell whether an approval card appeared each time. My Mac had no external drive attached and no Windows computer was connected, so we couldn't test either one. A script typed into the developer console isn't the same as page.evaluate, so we haven't confirmed that report.

If your Bot won't open a file:// page

The block message suggests serving the folder locally, but in our test, Nov 10 2026, the Bot's browser couldn't open the local address. Here's what to do instead.

1. Don't give your Bot the file:// address. Tell it the file's name and folder instead.
2. For the file's contents, ask your Bot to read the file directly with its file tool or a command. This worked in our test.
3. To see the page in the Bot's browser, ask your Bot to open it through a password-locked public tunnel. The steps that worked for us are on our FAQ page about testing a local app in Grok Bot's browser.

If you're on Windows

We haven't tried this on a Windows PC. Steps 1 to 3 come from the official pages, and step 4 from user reports.

1. In Grok Bot, open Settings > Computer > Your computer and check Execution on this computer: Ask every time, Always allow, or Never allow.
2. If your Bot says local tools are turned off while your setting allows them, that's the known issue above, and there's nothing you need to change.
3. On a team, check whether your team admin has capped the setting.
4. If you see "outside the allowed local-exec root," several users report that files inside their Windows user folder still work. I didn't find an official way to add other drives or folders.

What your Grok Bot can do

You can point your Bot at this page to adopt this practice.

Changing your settings is up to you. Paste this into a chat with your Grok Bot.

When a local file, folder, script, or file:// page is refused, do this:

1. Tell me the exact error, which tool refused it (file tool, command, page fetch, or browser), and on which computer.

2. If it's a file:// page, read the file directly with your file tool or a command instead, and tell me that's what you did. If I need to see the page in your browser, ask me before you set up a password-locked tunnel.

3. Don't get around a block any other way unless I approve that exact step first.

4. On my own computer, try one throwaway test file first, and ask me before you run anything there.

5. Never change my Execution on this computer setting yourself, and never ask me for a password in this chat.

6. Note what worked and what was refused, with the date, so we can compare after the next update.

Sources

Grok Bot changelog: https://x.ai/changelog/bot, SpaceXSI. The Nov 6, 2026 entry (v0.79.3). Retrieved Nov 10, 2026.

When the usual page fetch fails, the Bot reads the page directly instead of opening it in a browser.

With a team selected, Always allow on a local command saves, and your computer is no longer listed as Another computer.

Grok Bot FAQs: https://cursor.com/help/grok-bot/faqs, Cursor help. Retrieved Nov 10, 2026.

A Bot may say "Local tools are turned off. The user has set local tool access to Never." even though Execution on this computer is set to Always allow or Ask every time.

Your setting is correct, and there is nothing you need to change.

Use the computer and apps: https://docs.x.ai/grok-bot/computer-and-apps, SpaceXSI's Grok Bot docs. Last updated Nov 9, 2026. Retrieved Nov 10, 2026.

A Bot only runs commands on your local computer when that capability is enabled and you approve it under your local-computer policy: per-command approval with Ask every time by default, or Always allow or Never allow.

Approvals, security, and privacy: https://docs.x.ai/grok-bot/approvals-security-and-privacy, SpaceXSI's Grok Bot docs. Last updated Nov 5, 2026. Retrieved Nov 10, 2026.

Your team admin can cap this setting for the whole team; when the team's policy is stricter than yours, the team's applies.

Grok Bot security: https://docs.x.ai/grok-bot/security, SpaceXSI's Grok Bot docs. Last updated Nov 6, 2026. Retrieved Nov 10, 2026.

Our test, Nov 10 2026, on my Mac, on the Bot's own cloud computer and in its browser, with throwaway files only. User posts on X (not official), linked in the reports section above.

Related

Can Grok Bot use my Mac?

How do I test my own local app or game in Grok Bot's browser?

See how I set up Grok Bot: https://www.soundminds.ai/setup.