Agent not working - Connection Error

Support Help
1

Hi there,

At one point, I moved the folder from which I’ve been working within Cursor to another location on my laptop and now to any query the agent gives an error:

image
image1032×226 50.2 KB

I am not even sure where the Support is but it looks like people mostly get help on the forum from each other. How do I resolve this?

Thanks in advance

3

Hey, it’s most likely because older chats still point to files using the old folder path. After you moved the project, Cursor tries to load those resources, can’t find them, and shows a misleading “Connection failed” instead of a proper error message.

Try this:

  • Open a new chat, don’t continue the old ones. This should fix it right away.
  • If a new chat still doesn’t work, go to Cursor Settings (gear icon in the top right) > Network > Run Diagnostics and check if all tests pass.
  • If diagnostics are OK but the error stays, try disabling HTTP/2. Open App Settings Cmd+, / Ctrl+,, search for “HTTP/2”, enable “Disable HTTP/2”, then restart Cursor.

A similar case was solved here: Bug: Getting -> Connection failed. Please try again, or contact support if the issue persists. The cause was chat references to deleted or moved files.

Let me know if that helped.

4

Thanks Dean. Indeed opening up a new chat did help, although only when I had closed and reopened cursor from scratch.

Appreciate your advice.

вс, 12 апр. 2026 г., 17:37 Dean Rie <[email protected]>:

5

Starting a new chat sometimes works.

Most of my issues I believe stem from my sketchy connection to work. The fix required is to restart my machine AND start a new chat window.

6

@JasonDHubbard, if restarting your machine reliably fixes it, that often points to a network issue like a corporate proxy, VPN, or Zscaler. A couple things to try:

  • Cursor Settings (gear icon top right) > Network > Run Diagnostics. Check if all tests pass.
  • If diagnostics look OK but the errors come back, open App Settings Cmd+, or Ctrl+, search for HTTP/2, enable Disable HTTP/2, then restart Cursor. This can help a lot on flaky or corporate networks.

If that doesn’t help, tell me the exact error you’re seeing (screenshot or text), your Cursor version, and whether you’re using a VPN or proxy. Then we can dig deeper.