Cursor 3.2.16 Agents Window gets stuck on “Reconnecting...” after a few messages

Support Bug Reports
1

Where does the bug appear (feature/product)?

Somewhere else…

Describe the Bug

I am experiencing a serious issue with the Agents Window. Previously, the problem happened when I left an Agent window idle for some time and then came back to continue the conversation: the existing Agent session would get stuck on “Reconnecting…”.
Now the issue has become worse. The Agent window can get stuck on “Reconnecting…” after only two or three messages in the same conversation. Once this happens, the current Agent session can no longer continue working.
However, if I open a new Agent window, the new Agent works normally. This makes me think the issue is not a general network, account, or model availability problem, but something related to the existing Agent session, session restoration, or the Agents Window state.
I have already tried the following:

  • I am on Cursor 3.2.16
  • Network diagnostics pass successfully
  • I have restarted Cursor multiple times
  • New Agent windows work normally
  • The problem happens with existing Agent sessions that get stuck on “Reconnecting…”
    The current workaround is very inconvenient:
  1. I have to open a new Agent window.
  2. Export or copy the transcript from the previous stuck conversation.
  3. Put the transcript into my workspace as a file.
  4. Ask the new Agent to read that transcript and reconstruct the context.
    This works to some extent, but it is very cumbersome and disrupts the workflow. It also means the new Agent does not truly inherit the previous session state, and I have to manually manage context transfer.
    This feels like a regression or bug introduced in a recent Cursor update, especially around the Agents Window and session reconnection behavior.
    Questions:
  5. Is this a known issue in Cursor 3.2.16?
  6. Why does an existing Agent session get stuck on “Reconnecting…” while a newly opened Agent window works normally?
  7. Is there a way to recover or force-refresh the stuck Agent session?
  8. Is there a supported way for a new Agent to directly continue from a previous Agent session without manually exporting and re-importing the transcript?
  9. Are there any logs, Request IDs, or diagnostics I should provide to help debug this?
    Thanks.

Steps to Reproduce

The Agent window can get stuck on “Reconnecting…” after only two or three messages in the same conversation

Operating System

Windows 10/11

Version Information

I am on Cursor 3.2.16

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

Hey, thanks for the detailed report. The stuck Reconnecting… issue on existing sessions is a known one. We have a few similar reports already:

We’re tracking it on our side. No exact ETA for a fix yet.

On your questions:

  1. Yes, it’s a known regression around session reconnection.
  2. An existing session keeps state that can’t recover correctly after a transient network event. A new window starts fresh, so it works.
  3. There isn’t a direct way to force-refresh a stuck session right now. Your workaround of moving the transcript is the best option for now.
  4. There isn’t a native continue from previous agent session feature yet.
  5. To help with debugging, please send the Request ID from the stuck session: top-right of the chat > menu > Copy Request ID. Also share the approximate time it got stuck, with your timezone.

Also, does this happen more often after being idle, or during active use? And is it consistently reproducible, or random?

If we have an update on the fix, we’ll reply in the thread.