Hey, this is a known macOS issue: Cursor’s Info.plist is missing NSLocalNetworkUsageDescription. Without it, macOS silently blocks local network connections to 192.168.x.x and won’t show the prompt in System Settings > Privacy & Security > Local Network. Terminal ssh works because Terminal.app has its own entitlements. The non-standard port and -D for SOCKS aren’t related. The block happens at the TCP level before the SSH handshake, which is why it fails in about 10 ms.
Full breakdown and discussion: Integrated terminal cannot access local network devices on macOS — missing NSLocalNetworkUsageDescription
A workaround that sometimes helps: open System Settings > Privacy & Security > Local Network, then toggle Local Network permission for any other app. macOS sometimes re-reads permissions and may let Cursor through.
We’re tracking the bug, but there’s no exact ETA for a fix yet. I’ll close this thread as a duplicate so the discussion stays in one place.