Terminal cannot access local network on MacOS (192.168.x.x) - missing network entitlements in app signature

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Problem
Cursor’s terminal cannot reach any local network host (192.168.x.x) while internet connectivity works fine. Error returned:
nc: connectx to 192.168.1.55 port 22 (tcp) failed: No route to host
ping: sendto: No route to host
SSH to the same host works perfectly from macOS native Terminal.app.
Root Cause (confirmed)
Running codesign -d --entitlements - /Applications/Cursor.app reveals the app is missing critical network entitlements:
[Key] com.apple.security.automation.apple-events → true
[Key] com.apple.security.cs.allow-jit → true
[Key] com.apple.security.device.audio-input → true
[Key] com.apple.security.device.camera → true
Absent:
• com.apple.security.network.client — required for outbound TCP
• NSLocalNetworkUsageDescription — required for macOS Sequoia Local Network privacy prompt
Without NSLocalNetworkUsageDescription , macOS silently blocks all RFC-1918 traffic and never shows the permission dialog. The app never appears in System Settings → Privacy & Security → Local Network, making it impossible for the user to grant access manually. tccutil reset LocalNetwork also fails because there is no TCC entry to reset.

Steps to Reproduce

1.	Open Cursor terminal (not agent, regular terminal)
2.	Run  ping -c 3 192.168.1.x  to any local machine
3.	Observe:  No route to host  — no permission dialog appears
4.	Run  ping github.com  — works fine
5.	Check System Settings → Privacy & Security → Local Network — Cursor is absent from the list

Expected Behavior

On first local network access attempt, macOS should display a permission dialog. After granting, local network hosts should be reachable from Cursor’s terminal.

Fix Required
Add to Cursor.app entitlements and Info.plist :
• com.apple.security.network.client = true
• NSLocalNetworkUsageDescription with a usage description string

Operating System

MacOS

Version Information

Version: 3.2.11
VSCode Version: 1.105.1
Commit: e9ee1339915a927dfb2df4a836dd9c8337e17cc0
Date: 2026-04-24T14:36:47.933Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.4.0

MacOS: 26.4.1 (25E253)
Machine: Apple Silicon MacBook M5 Pro
Model Number: Z1KH0007LZE/A
Network: Wi-Fi, standard home/office LAN

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

Hey, thanks for the detailed write-up. The root cause looks right. Missing NSLocalNetworkUsageDescription in Info.plist and com.apple.security.network.client in the entitlements does break access to RFC-1918 addresses on Sequoia.

This is a known issue. We already have a fresh thread with the same report from today: Integrated terminal cannot access local network devices on macOS — missing NSLocalNetworkUsageDescription. We’ve filed it internally. The upstream fix in VS Code (PR #308457) landed in 1.116.0, and Cursor is currently on 1.105.1. We’ll pull it in after our next base update. I can’t share an ETA for the fix yet.

I’m going to close this thread as a duplicate. Please follow that other thread and I’ll post there when we have an update.