Remote-SSH Chat hangs due to agent sandbox preflight with network_access=false (DNS/TLS blocked)

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

In Remote-SSH sessions, Cursor Chat does not respond at all, even when sending a trivial message such as “hello”.
The UI may show DNS or SSL connection failures, but investigation shows the root cause is remote agent sandbox preflight execution with network_access=false, which blocks outbound networking (DNS/TLS) required for Chat.
This does not occur in local (non-Remote-SSH) sessions.

Steps to Reproduce

Connect to a remote Ubuntu host using Remote-SSH in Cursor
Open any workspace
Open Cursor Chat
Send a simple message (e.g. hello)
Observe that Chat never responds
ps -eo pid,lstart,cmd | grep cursor-sandbox | grep preflight

This shows repeated cursor-sandbox --preflight-only executions with “network_access”: false immediately after sending the chat message.

Expected Behavior

Chat should respond normally in Remote-SSH sessions
Chat / AI execution should not be blocked by agent sandbox network restrictions
A simple chat message should not fail due to sandboxed preflight with networking disabled

Operating System

Linux

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.2.20 (Universal)
VSCode Version: 1.105.1
Commit: b3573281c4775bfc6bba466bf6563d3d498d1070
Date: 2025-12-12T06:29:26.017Z (3 hrs ago)
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 25.1.0

Additional Information

Disabling HTTP/2 (forcing HTTP/1.1) does not resolve the issue
General outbound networking from the remote host works (e.g. curl)
Issue appears related to recent Cursor Server / agent execution changes
Likely caused by Chat invoking remote agent preflight under a sandbox that blocks network access

Does this stop you from using Cursor

Yes - Cursor is unusable

Hey, thanks for the report.

Try disabling HTTP/2 in your Remote-SSH session:

  1. In the remote session, open Settings with CTRL+,
  2. Search for “HTTP/2”
  3. Enable “Disable HTTP/2”
  4. Restart Cursor

Let me know if that helps.

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.