Cursor terminal unable to reach local network

[joe_schmoe]

Where does the bug appear (feature/product)?

Cursor CLI

Describe the Bug

this popped up immediately following the update to v2.4.21, and affects both the local cli and the llm. the model reports its sandbox is unable to connect to hosts on the local network, and i’ve verified that, using the onboard cli, i am unable to ssh or ping hosts on my local network. i can still reach hosts outside the local network.

from ifconfig:

en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        options=6460<TSO4,TSO6,CHANNEL_IO,PARTIAL_CSUM,ZEROINVERT_CSUM>
        ether <REDACTED>
        inet6 fe80::8f1:5b35:6c39:bc08%en0 prefixlen 64 secured scopeid 0xe 
        inet6 fdfd:8f4d:f913:4c8f:c34:cacf:ed88:4e59 prefixlen 64 autoconf secured 
        inet 10.17.1.100 netmask 0xfffffe00 broadcast 10.17.1.255

and some pings - again, from the cursor cli:

❯ ping 10.17.1.1  # local router
PING 10.17.1.1 (10.17.1.1): 56 data bytes
ping: sendto: No route to host
ping: sendto: No route to host
Request timeout for icmp_seq 0
ping: sendto: No route to host
Request timeout for icmp_seq 1
ping: sendto: No route to host
Request timeout for icmp_seq 2
^C
--- 10.17.1.1 ping statistics ---
4 packets transmitted, 0 packets received, 100.0% packet loss
❯ ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: icmp_seq=0 ttl=119 time=14.031 ms
64 bytes from 8.8.8.8: icmp_seq=1 ttl=119 time=13.880 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=119 time=13.812 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=119 time=15.647 ms
^C
--- 8.8.8.8 ping statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 13.812/14.342/15.647/0.757 ms

meanwhile, from my terminal on the same machine:

❯ ping 10.17.1.1
PING 10.17.1.1 (10.17.1.1): 56 data bytes
64 bytes from 10.17.1.1: icmp_seq=0 ttl=64 time=5.831 ms
64 bytes from 10.17.1.1: icmp_seq=1 ttl=64 time=6.103 ms
64 bytes from 10.17.1.1: icmp_seq=2 ttl=64 time=5.796 ms
^C
--- 10.17.1.1 ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 5.796/5.910/6.103/0.137 ms
❯ ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: icmp_seq=0 ttl=119 time=14.081 ms
64 bytes from 8.8.8.8: icmp_seq=1 ttl=119 time=14.797 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=119 time=14.444 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=119 time=17.973 ms
^C
--- 8.8.8.8 ping statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 14.081/15.324/17.973/1.550 ms

Steps to Reproduce

1. open cursor’s built-in terminal
   2a. ping anything on the local network - OR
   2b. ssh to any host on the local network

Expected Behavior

before this most recent update, pings went through, and ssh connections succeeded

Operating System

MacOS

Version Information

Version: 2.4.21 (Universal)
VSCode Version: 1.105.1
Commit: dc8361355d709f306d5159635a677a571b277bc0
Date: 2026-01-22T16:57:59.675Z
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 arm64 25.2.0

For AI issues: which model did you use?

Auto

For AI issues: add Request ID with privacy disabled

Request ID: 11320074-0fb4-4000-b31c-e30a7a7f76b7

Additional Information

i selected ‘sometimes’ below because, technically, i can still use the app - in practical terms, though, literally everything i’m working on at the moment is on my local network, which means i’m functionally unable to use it.

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

[deanrie]

Hey, thanks for the report. This looks like a macOS Local Network permissions issue. Updating to v2.4.21 may have triggered new permissions.

Try this:

1. System Settings > Privacy & Security > Local Network: Check if Cursor is listed there and if the permission is enabled.

2. If Cursor isn’t there or the permission is off, turn it on and restart Cursor.

3. Important detail: sometimes macOS shows Cursor under a different app name in that list (like this). Try enabling all apps in the list one by one to narrow it down.

4. If Cursor never shows up, try running a ping from Cursor’s normal terminal (not the agent terminal), like ping 10.17.1.1. That should trigger the system permission prompt.

5. If nothing helps, try removing Cursor from the Local Network list and restart the app. macOS should ask for permission again.

Let me know if it worked.

[joe_schmoe]

of all the silly things…

welp, that totally worked - and you’re right, toggling cursor wasn’t the answer. in my case, it was flipping on permission for notion, which, in case anyone hadn’t noticed, is a completely different app from cursor.

for the benefit of anyone else who might need to troubleshoot this, i was able to start the ping, flip over to system settings, and start turning things on one at a time - as soon as i got to the right one, packets started coming through. for whatever it’s worth, i never got a prompt asking if cursor (or anything else) should be allowed to find devices on the local network - it just started working when i hit the right switch. i toggled it a few times just to be sure i had the right one, and it was like flipping a light switch: on was on, and off was off - it’s just that the switch for my living room lights was controlling the garage door, is all.

i’m a mac guy & always have been - and while this kinda stuff can be frustrating, it’s kinda nice to see that goofy errors like this still pop up from time to time.

thanks!