Cursor IDE chat keeps renaming agent tabs "New Agent" after crash

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I had all the agent chats stop working, everything was met with the below notification (pic) after a few minutes, a reboot of that cursor window fixed it, but now all the agent chats keep being called “New Agent” though they sometimes come back after clicking around.

Steps to Reproduce

See above

Expected Behavior

No such reboot required
Agent tab names stay consistent

Screenshots / Screen Recordings

cursor_fail.jpg
cursor_fail.jpg1423×906 96.5 KB

Operating System

Windows 10/11

Version Information

Version: 3.21.9 (user setup)
VS Code Extension API: 1.128.0
Commit: 9998796a6096ce83d83a9332bfe7473b985db750
Date: 2026-09-17T02:16:48.732Z
Layout: IDE
Build Type: Stable
Release Track: Default
Electron: 42.10.0
Chromium: 148.0.7778.280
Node.js: 24.18.1
V8: 14.8.178.38-electron.0
xterm.js: 6.1.0-beta.291
OS: Windows_NT x64 10.0.26200

For AI issues: add Request ID with privacy disabled

f33d902c-5fde-441d-a1b3-799e31ca9339

Does this stop you from using Cursor

No - Cursor works, but with this issue

cursor_fail3
cursor_fail3855×162 24.8 KB

cursor_fail2
cursor_fail21232×249 47.8 KB

3

Here it is happening in more tabs

cursor_fail4
cursor_fail41160×147 38.3 KB

4

The latest updates have been breaking stuff, my agent plan mode also gets stuck at “Grepping…”, “Searching…”, “Reading…” and plan mode gets stuck at “Preparing…”. I also did a network diagnostic and got the following results
Cursor Network Diagnostic Results

FAILED (1): Authentication

DNS: Success
Logs:
[2026-09-18T20:07:35.603Z] Host: api2.cursor.sh
[2026-09-18T20:07:35.603Z] Servers: 127.0.0.1
[2026-09-18T20:07:35.603Z] Resolved to 107.23.2.227 in 29ms
[2026-09-18T20:07:35.665Z] Resolved to 107.23.2.227 in 56ms
[2026-09-18T20:07:35.669Z] Resolved to 107.23.2.227 in 1ms
[2026-09-18T20:07:35.686Z] Resolved to 107.23.2.227 in 3ms
[2026-09-18T20:07:35.701Z] Host: api2.cursor.sh
[2026-09-18T20:07:35.701Z] Servers: system
[2026-09-18T20:07:35.701Z] Resolved to 100.61.69.221, 44.194.208.64, 54.166.216.179, 44.209.238.104, 100.25.179.180, 52.201.87.18, 54.204.177.130, 100.60.208.30 in 14ms
[2026-09-18T20:07:35.703Z] Resolved to 100.61.69.221, 44.194.208.64, 54.166.216.179, 44.209.238.104, 100.25.179.180, 52.201.87.18, 54.204.177.130, 100.60.208.30 in 0ms
[2026-09-18T20:07:35.707Z] Resolved to 100.61.69.221, 44.194.208.64, 54.166.216.179, 44.209.238.104, 100.25.179.180, 52.201.87.18, 54.204.177.130, 100.60.208.30 in 2ms
[2026-09-18T20:07:35.709Z] Resolved to 100.61.69.221, 44.194.208.64, 54.166.216.179, 44.209.238.104, 100.25.179.180, 52.201.87.18, 54.204.177.130, 100.60.208.30 in 0ms
[2026-09-18T20:07:35.709Z] Result: true

HTTP/2: Running
Logs:
[2026-09-18T20:07:35.557Z] Start

SSL: Running
Logs:
[2026-09-18T20:07:35.557Z] Start

API: Success
Logs:
[2026-09-18T20:07:35.559Z] Start
[2026-09-18T20:07:37.185Z] Result: true

Ping: Success
Logs:
[2026-09-18T20:07:35.560Z] Sending ping 1
[2026-09-18T20:07:36.741Z] Response: ‘ping’ in 1181ms
[2026-09-18T20:07:36.741Z] Sending ping 2
[2026-09-18T20:07:37.314Z] Response: ‘ping’ in 573ms
[2026-09-18T20:07:37.314Z] Sending ping 3
[2026-09-18T20:07:37.549Z] Response: ‘ping’ in 235ms
[2026-09-18T20:07:37.549Z] Sending ping 4
[2026-09-18T20:07:37.951Z] Response: ‘ping’ in 402ms
[2026-09-18T20:07:37.951Z] Sending ping 5
[2026-09-18T20:07:38.158Z] Response: ‘ping’ in 207ms
[2026-09-18T20:07:38.158Z] Result: true

Chat: Success
Logs:
[2026-09-18T20:07:35.560Z] Starting stream
[2026-09-18T20:07:36.727Z] Response: ‘foo’ in 1152ms
[2026-09-18T20:07:37.773Z] Response: ‘foo’ in 1046ms
[2026-09-18T20:07:38.833Z] Response: ‘foo’ in 1060ms
[2026-09-18T20:07:39.819Z] Response: ‘foo’ in 986ms
[2026-09-18T20:07:40.814Z] Response: ‘foo’ in 995ms
[2026-09-18T20:07:41.798Z] Result: true

Agent: Success
Logs:
[2026-09-18T20:07:35.564Z] Starting stream
[2026-09-18T20:07:35.575Z] Pushing first message
[2026-09-18T20:07:36.677Z] Response: ‘foo’ in 1102ms
[2026-09-18T20:07:37.178Z] Pushing next message
[2026-09-18T20:07:37.398Z] Response: ‘foo’ in 721ms
[2026-09-18T20:07:37.899Z] Pushing next message
[2026-09-18T20:07:38.148Z] Response: ‘foo’ in 750ms
[2026-09-18T20:07:38.648Z] Pushing next message
[2026-09-18T20:07:38.879Z] Response: ‘foo’ in 731ms
[2026-09-18T20:07:39.381Z] Pushing next message
[2026-09-18T20:07:39.599Z] Response: ‘foo’ in 720ms
[2026-09-18T20:07:39.599Z] Result: true

Marketplace: Success
Logs:
[2026-09-18T20:07:35.522Z] Host: marketplace.cursorapi.com
[2026-09-18T20:07:36.548Z] Response in 1026ms
[2026-09-18T20:07:36.548Z] Response: 200
[2026-09-18T20:07:36.548Z] Response Type: cors
[2026-09-18T20:07:36.548Z] Server: null
[2026-09-18T20:07:36.548Z] Result: OK in 1026ms

Authentication: Error: Failed to fetch
Logs:
[2026-09-18T20:07:35.524Z] Host: prod.authentication.cursor.sh
[2026-09-18T20:08:05.881Z] Error: TypeError: Failed to fetch

Authentication UI: Success
Logs:
[2026-09-18T20:07:35.557Z] DNS lookup: authenticator.cursor.sh
[2026-09-18T20:07:35.663Z] Resolved authenticator.cursor.sh to 172.64.152.23 in 78ms

Cursor Tab: Success
Logs:
[2026-09-18T20:07:35.557Z] DNS lookup: api3.cursor.sh
[2026-09-18T20:07:35.659Z] Resolved api3.cursor.sh to 104.18.19.125 in 74ms

Agent Endpoint: Success
Logs:
[2026-09-18T20:07:35.557Z] DNS lookup: agent.api5.cursor.sh
[2026-09-18T20:07:35.753Z] Resolved agent.api5.cursor.sh to 54.163.65.150 in 160ms

Downloads: Success
Logs:
[2026-09-18T20:07:35.525Z] Host: downloads . cursor . com
[2026-09-18T20:07:36.737Z] Response: 403 in 1212ms

CDN: Success
Logs:
[2026-09-18T20:07:35.525Z] Host: cursor-cdn.com
[2026-09-18T20:07:39.869Z] Response: 404 in 4344ms

7

Hey, thanks for the detailed report. There are two separate things here.

  1. Agent Execution Timed Out and chats stopping. In 3.21.9 on Windows there’s an issue where the part of Cursor that starts agent tools can take a long time to start, and requests time out before they’re even sent. Reload Window works around it, which matches what you’re seeing. This is already fixed in 3.21.12 and newer.
  • Update: Help → Check for Updates or Cursor · Download
  • Fully quit Cursor, check Task Manager for any leftover Cursor processes, then start it again

One more quick step that helped for some users: open the command palette with Ctrl+Shift+P, run Developer: GC Agent KV Blobs, wait for the “done” notification, then Reload Window. This clears the local chat database without deleting any chats.

  1. New Agent tabs. The chats and their titles are still there. The tab bar just doesn’t pick up the saved name until the chat is opened. This is a separate issue we’re tracking. Opening each chat once brings the name back, and after a full restart they should stay saved.

After updating to 3.21.12, let me know:

  • whether the timeouts are gone
  • whether New Agent tabs still come back after a restart

If either issue is still happening, run Developer: Capture and Send Debugging Data from the command palette while the tab still shows New Agent, and post here.

@Ken_Lester getting stuck on Grepping / Searching / Preparing in 3.21.9 is likely the same as item 1. Updating to 3.21.12+ should help. If it doesn’t after updating, reply and we’ll dig in.

8

This part helped by other bug with the perma-stuck window, thank you!!!

New Agent titles do NOT persistt after clicking on them, they show the name, then when i’m not looking they go back to New Agent and restarting didn’t help. Super minor issue, obviously, but wanted to let you know…

9

Hey, great that GC Agent KV Blobs fixed the window freezing. That was the main issue.

About the “New Agent” names, what you’re describing (the name flashes and then rolls back to “New Agent”, and restarting doesn’t help) isn’t the behavior we expect. The chats themselves and their titles are still there, but the tab bar won’t keep them. That’s a separate issue we’re tracking.

To give the team a solid datapoint for your IDE, could you do this once while the tab still shows “New Agent”: open the command palette with Ctrl+Shift+P, run Developer: Capture and Send Debugging Data, then reply here to confirm you sent it? That’ll help us figure out why the names aren’t being saved in your case.

Even if it’s a small thing, thanks for flagging it. I’ll reply in the thread once there’s an update.

10

image

I take it back, it’s not a minor issue when it keeps happening ALL THE TIME and not just after a crash.
image

Literally every window of mine is always just New Agents

image

It’s a constant overhead of having to click dozens of tabs.

image

Can this be fixed plesase?

Version: 3.22.12 (user setup)
VS Code Extension API: 1.128.0
Commit: 3a92974361033b2051526321308c2740fe5912c0
Date: 2026-09-26T04:55:12.125Z
Layout: IDE
Build Type: Stable
Release Track: Default
Electron: 42.10.0
Chromium: 148.0.7778.280
Node.js: 24.18.1
V8: 14.8.178.38-electron.0
xterm.js: 6.1.0-beta.291
OS: Windows_NT x64 10.0.26200

11

Hey, thanks for coming back with an update, and good to hear the window freezing went away after GC Agent KV Blobs.

About “New Agent”, what you’re describing on 3.22.12, where the name appears when you open it, then switches back, and a restart doesn’t help, isn’t the behavior we expect. The chats themselves and their names are still there, the tab bar just isn’t keeping the name. I’ve passed this to the team separately from the timeout issue, and we’re tracking it. From your screenshots, I can see that almost all tabs are showing as “New Agent” right now, and I get that clicking through dozens of tabs is constant overhead.

To give the team a specific data point from your IDE on 3.22.12, please do this once while the tab is still showing “New Agent”:

  1. Ctrl+Shift+P → Developer: Capture and Send Debugging Data
  2. Reply here once you’ve sent it

This will help us understand why the names aren’t being kept in your case. I’ll post in the thread when there’s an update.