Cursor Agent used to work normally over Remote SSH with AI traffic going through my local machine.
Recently, Agent started staying on Reconnecting… for all models.
Local workspaces work normally.
My remote host has restricted outbound network access:
api5.cursor.sh → Could not resolve host
while agent.api5.cursor.sh and agentn.api5.cursor.sh resolve normally.
Downgrading Cursor to 3.14.27 did not help.
Your current documentation says:
“AI requests go from your local machine to Cursor’s servers, not from the remote host.”
This appears to have changed after the new cursor_agent_host rollout.
Could you please:
disable the cursor_agent_host feature gate for my account as a workaround, or
provide a way to route Agent traffic through the local Cursor client again?
I cannot change network/DNS/proxy configuration on the remote corporate server.
Same issue here after the cursor_agent_host rollout.
A local workspace on Windows works, and network diagnostics pass. In a Remote SSH window to a Linux host, every model, including Auto, sits on reconnect and then fails:
Until September 21, Agent in this SSH window sent traffic through my local machine and worked. I did not change network or proxy settings. Reinstalling cursor-server on the host did not help.
Please disable cursor_agent_host for my account, or restore Agent routing through the local client.
In recent versions, the Agent connection for a Remote SSH window is opened from the remote host rather than from the Cursor app on your Mac.
There is a setting to route Agent traffic through your local Cursor app again. It requires Cursor 3.21.16 or newer (check via Cursor > About Cursor), and it has to be set on the remote side:
Open your project in Cursor over Remote SSH as usual.
Open Settings (Cmd+,) and click the Remote [SSH: your-host] tab at the top of the settings page.
Search for remoteInferenceRoute.
Set Cursor Agent Host: Remote Inference Route to always.
Run Developer: Reload Window from the Command Palette (Cmd+Shift+P).