Connection Lost Error - Per Agent

[esch]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When in the Agent window I will periodically get the “Connection Error” / “Connection failed. If the problem persists, please check your internet connection or VPN”. - If I wait and hit “Try again” it will not work, no matter how many times I try or how long I wait. However, if I start a new agent, it works fine. At least for a while, then it too may error out in the same way. The fact that a new agent works and the fact that there is no other idication on my system of a connection issue says this this is likely a Cursor AI issue. I am on Version: 2.3.34 on Win11. - VSCode Version 1.105.1

Steps to Reproduce

Use Cursor AI Agent window - in this case using for coding operations. Use it for a period of time. At some point it will produce the above error and cease to work . This can take 10min to 90min to happen, but seems to always happen eventually.

Expected Behavior

Would normall expect Agent window to respond, but it only shows error. Note that this connection is to SSH session on a remote windows machine, but not sure if that is part of the problem or not. Remote SSH is Windows OpenSSH.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.3.34 (user setup)
VSCode Version: 1.105.1
Commit: 643ba67cd252e2888e296dd0cf34a0c5d7625b90
Date: 2026-01-10T21:17:10.428Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

Auto

Does this stop you from using Cursor

No - Cursor works, but with this issue

[deanrie]

Hey, thanks for the detailed report.

This looks like a known trouble area: Agent + Remote SSH. We’ve seen a few similar reports, especially when using SSH on Windows: Agent connection error - remote SSH - when console open

To help us diagnose this more accurately, could you share:

1. Logs from the Developer Tools console (when the error happens): Help > Toggle Developer Tools > Console, then copy the red errors
2. Your extension list: CTRL + Shift + P > Developer: Open Extension Monitor, screenshot it
3. Try disabling all extensions (cursor --disable-extensions from the command line) and check if the issue still happens

Also try running Network Diagnostics: Cursor Settings > Network > Run Diagnostics. The results can show connection issues to the backend.

The fact that a new agent works suggests this is more likely a backend issue with agent session expiration, not a local connection problem.