Hey, thanks for the detailed report, your analysis is correct. Cursor’s Info.plist really doesn’t include NSLocalNetworkUsageDescription, so macOS silently blocks local network access and the app doesn’t show up in Privacy & Security > Local Network. This has been a long-running issue and it shows up in a few threads going back to macOS Sequoia, for example Cursor terminal unable to reach local network, Cant access local network on latest macOS version, Cursor not able to access local network.
Upstream VS Code added this key in early April, but the change hasn’t landed in Cursor yet. I’ve reported it internally as a build bug, no timeline for the fix yet.
A workaround that sometimes helps, but not for everyone, is to toggle the Local Network permission for any other app in System Settings > Privacy & Security > Local Network. macOS re-reads permissions and sometimes lets Cursor through. There’s no permanent solution yet, we need the plist key in a signed build.
Once the fix ships to stable, we’ll reply in this thread.