Agents keep restarting and the window closes over and over (Windows)

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Hello,

I am on Windows (build 10.0.26200). Cursor version: [paste from Cursor → About Cursor].

Two problems keep coming back during normal agent chats:

Agents restart on their own and reappear after I have already been working in the chat. The agent panel comes back and the session starts over, so I lose the thread I was in.
The window closes by itself, repeatedly, every few minutes. It is not a one-time crash. It drops again and again while I am using the app.
Request ID from the chat where this happened: [paste Copy Request ID].

This makes the editor hard to use, because the chat and the window do not stay open. Please let me know if you need a screen recording.

Thank you.

Steps to Reproduce

Steps to Reproduce

Open Cursor on Windows.
Start an agent chat in a local project and keep working in it.
After a few minutes the agent restarts, the old agent panel reappears, and the window closes by itself.
I reopen Cursor and the same thing happens again in the next chat. there is 9 agents restarting everytime.Cursor also keeps warning me that memory use is too high, and it asks me to send a snapshot. These warnings show up again and again while the agents are restarting and the window is closing.

Expected Behavior

Expected Behavior:

The agent chat and the window stay open for the whole session. Agents do not restart or come back on their own.

Operating System

Windows 10/11

Version Information

Cursor IDE 3.22.7
Commit: d5c0e77a0214208f36b56d42e8e787de88d02ea4
OS: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

Grok 4.7

Does this stop you from using Cursor

No - Cursor works, but with this issue

12

Hey @M11, this should break the loop without losing your history:

  1. Cursor Settings → General → Startup, turn off Continue Interrupted Agents.

  2. Fully quit Cursor (close every window), then reopen.

  3. Start a new chat instead of continuing your longest-running ones. To carry the context over, type @, pick Past Chats, and select the old chat.

  4. Archive the old chat rather than deleting it (you can unarchive it later).

If the memory warning pops up, dismiss it instead of clicking Capture Snapshot.

This is an issue we’re tracking. If the window still closes after these steps, paste the lines around renderer process gone from the newest main.log under %APPDATA%\Cursor\logs.