# Agent not working - Connection Error

**URL:** <https://forum.cursor.com/t/agent-not-working-connection-error/157301>\
**Category:** Help\
**Created:** [April 10, 2026, 4:10pm UTC](https://forum.cursor.com/t/agent-not-working-connection-error/157301 "2026-04-10T16:10:56Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![venturas](https://avatars.discourse-cdn.com/v4/letter/v/f14d63/32.png) [@venturas](https://forum.cursor.com/u/venturas)\
**Post date:** [April 10, 2026, 4:10pm UTC](https://forum.cursor.com/t/agent-not-working-connection-error/157301/1 "2026-04-10T16:10:56Z")

</div>

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](https://us1.discourse-cdn.com/cursor1/original/3X/e/9/e925a838d9766c7e556de670d5d58fa3569ac9ab.png)

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

---

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [April 12, 2026, 4:27pm UTC](https://forum.cursor.com/t/agent-not-working-connection-error/157301/3 "2026-04-12T16:27:31Z")

</div>

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](https://forum.cursor.com/t/bug-getting-connection-failed-please-try-again-or-contact-support-if-the-issue-persists/155071). The cause was chat references to deleted or moved files.

Let me know if that helped.

---

<div class="post-metadata">

**Author:** ![venturas](https://avatars.discourse-cdn.com/v4/letter/v/f14d63/32.png) [@venturas](https://forum.cursor.com/u/venturas)\
**Post date:** [April 13, 2026, 12:35am UTC](https://forum.cursor.com/t/agent-not-working-connection-error/157301/4 "2026-04-13T00:35:26Z")

</div>

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 \<[notifications@cursor1.discoursemail.com](mailto:notifications@cursor1.discoursemail.com)\>:

---

<div class="post-metadata">

**Author:** ![JasonDHubbard](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/jasondhubbard/32/105566_2.png) [@JasonDHubbard](https://forum.cursor.com/u/JasonDHubbard)\
**Post date:** [April 15, 2026, 9:11pm UTC](https://forum.cursor.com/t/agent-not-working-connection-error/157301/5 "2026-04-15T21:11:57Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [April 19, 2026, 9:53am UTC](https://forum.cursor.com/t/agent-not-working-connection-error/157301/6 "2026-04-19T09:53:20Z")

</div>

@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.