Sandbox Network access: Blocked issue

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Can no longer test run builds of my next.js project because it defaults to sandbox and i sandbox it cannot access fonts.googleapis.com.

cd [redacted] && npm run build

> [email protected] build
> next build

   ▲ Next.js 15.5.7
   - Environments: .env.local, .env.production

   Creating an optimized production build ...
getaddrinfo ENOTFOUND fonts.googleapis.com

Retrying 1/3...
getaddrinfo ENOTFOUND fonts.googleapis.com

Retrying 1/3...
getaddrinfo ENOTFOUND fonts.googleapis.com

Retrying 2/3...
getaddrinfo ENOTFOUND fonts.googleapis.com

Retrying 2/3...
getaddrinfo ENOTFOUND fonts.googleapis.com

Retrying 3/3...
getaddrinfo ENOTFOUND fonts.googleapis.com

Retrying 3/3...
[Error: getaddrinfo ENOTFOUND fonts.googleapis.com] {
  errno: -3008,
  code: 'ENOTFOUND',
  syscall: 'getaddrinfo',
  hostname: 'fonts.googleapis.com'
}
[Error: getaddrinfo ENOTFOUND fonts.googleapis.com] {
  errno: -3008,
  code: 'ENOTFOUND',
  syscall: 'getaddrinfo',
  hostname: 'fonts.googleapis.com'
}
Failed to compile.

config/fonts.ts
`next/font` error:
Failed to fetch `Fira Code` from Google Fonts.

config/fonts.ts
`next/font` error:
Failed to fetch `Inter` from Google Fonts.


> Build failed because of webpack errors

Turning on ‘Legacy Terminal Tool’ in ‘Settings / Agents’ reverts me to the older behaviour which works fine.

Steps to Reproduce

Prompt" ‘run a build for testing’

Expected Behavior

Previously it would run a build and fix errors, now it fails.

Operating System

MacOS

Version Information

Version: 2.4.22 (Universal)
VSCode Version: 1.105.1
Commit: 618c607a249dd7fd2ffc662c6531143833bebd40
Date: 2026-01-26T22:51:47.692Z (2 days ago)
Build Type: Stable
Release Track: Default
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Darwin x64 25.2.0

For AI issues: which model did you use?

Auto

Does this stop you from using Cursor

No - Cursor works, but with this issue

3

Hey, thanks for the report. This is a known sandbox behavior. By default, it blocks network access, including external APIs like fonts.googleapis.com.

You’ve got 2 options:

  1. Switch Auto-Run Mode
  • Go to Settings > Cursor Settings > Agents > Auto-Run
  • In Auto-Run Mode, pick Ask Every Time instead of Run in Sandbox
  • Cursor will ask before running commands
  1. Legacy Terminal Tool (your current workaround)
  • It works, but it’s a temporary option and may be removed in future versions

Option 1 is usually more convenient. Sandbox stays on, but it can still fetch external resources for builds.

Here’s a similar case with the same pattern and fix: Cursor AI Agent Cannot Access localhost via curl

Let me know if none of this helps.

4

I have tried all of it as I have seen those previous reports. It still does not work. I don’t even have Run in Sandbox option there. I tried both Ask every time and Run everything. It doesn’t work.

5

Capture
Capture1221×657 65 KB

6

Thanks for the screenshot of the agent settings. This looks like a different issue: on Windows, the agent doesn’t receive command output in versions 2.4.21 to 2.4.27. That’s a known bug.

I replied to your other post here: AI agent is sandboxed, cannot run tests or work with GitHub - #3 by deanrie

Let’s continue the discussion there so we don’t spread it across different threads. We’ll need DevTools logs, the instructions are in that reply.