Cursor AI response time and deleting old chats

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Ai responses are extremely slow, plus can’t delete old chats as they keep reappearing

Steps to Reproduce

Ask a question in the editor chat window and see the response time, also try deleting old chats.

Operating System

Windows 10/11

Version Information

Version: 3.0.9 (user setup)
VSCode Version: 1.105.1
Commit: 93e276db8a03af947eafb2d10241e2de17806c20
Date: 2026-04-03T02:06:46.446Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26200

Does this stop you from using Cursor

No - Cursor works, but with this issue

1 Like
5

Hey, thanks for the report. On both issues:

Chat deletion: This was a known bug with zombie drafts, deleted chat drafts could come back. The fix is already in 3.0.9, which you are on now. Please fully restart Cursor, close it and open it again, then check if the issue is gone. If chats still come back after a restart, let me know and we will dig in more.

Slow AI replies: I will need a bit more context to figure it out:

  1. Which model are you using?
  2. Can you share the Request ID for a slow request? Right top of the chat > context menu > Copy Request ID
  3. Please go to Cursor Settings > Network > Run Diagnostics and share the results.

Let me know how it goes.

7

Thank you for the answer

I mainly use Opus 4.6, The issue with deleting chats still persists even though I closed and reopeend Cursor. This started happening after todays update, that was not the issue yesterday.

here is the results for diagnostics

Cursor Network Diagnostic Results

DNS: Success
Logs:
[2026-04-03T08:26:19.449Z] Host: api2.cursor.sh
[2026-04-03T08:26:19.449Z] Servers: 127.0.0.1
[2026-04-03T08:26:19.449Z] Resolved to 52.1.166.58 in 8ms
[2026-04-03T08:26:19.520Z] Resolved to 52.1.166.58 in 35ms
[2026-04-03T08:26:19.532Z] Resolved to 52.1.166.58 in 1ms
[2026-04-03T08:26:19.534Z] Resolved to 52.1.166.58 in 1ms
[2026-04-03T08:26:19.541Z] Host: api2.cursor.sh
[2026-04-03T08:26:19.541Z] Servers: system
[2026-04-03T08:26:19.541Z] Resolved to 44.199.25.3, 98.90.236.42, 98.94.122.138, 13.222.92.77, 100.50.135.67, 54.157.75.46, 3.216.212.206, 18.235.84.112 in 6ms
[2026-04-03T08:26:19.542Z] Resolved to 44.199.25.3, 98.90.236.42, 98.94.122.138, 13.222.92.77, 100.50.135.67, 54.157.75.46, 3.216.212.206, 18.235.84.112 in 0ms
[2026-04-03T08:26:19.542Z] Resolved to 44.199.25.3, 98.90.236.42, 98.94.122.138, 13.222.92.77, 100.50.135.67, 54.157.75.46, 3.216.212.206, 18.235.84.112 in 0ms
[2026-04-03T08:26:19.543Z] Resolved to 44.199.25.3, 98.90.236.42, 98.94.122.138, 13.222.92.77, 100.50.135.67, 54.157.75.46, 3.216.212.206, 18.235.84.112 in 0ms
[2026-04-03T08:26:19.543Z] Result: true

HTTP/2: Success
Logs:
[2026-04-03T08:26:19.424Z] Start
[2026-04-03T08:26:19.724Z] Host: api2.cursor.sh
[2026-04-03T08:26:19.724Z] Protocol: h2
[2026-04-03T08:26:19.724Z] Result: true in 300ms

SSL: Success
Logs:
[2026-04-03T08:26:19.424Z] Start
[2026-04-03T08:26:19.878Z] URL: https://api2.cursor.sh/
[2026-04-03T08:26:19.878Z] Status: 200
[2026-04-03T08:26:19.878Z] IP: 52.1.166.58
[2026-04-03T08:26:19.878Z] Issuer: C=US; O=Amazon; CN=Amazon RSA 2048 M01
[2026-04-03T08:26:19.878Z] Name: api2.cursor.sh
[2026-04-03T08:26:19.878Z] AltName: DNS:api2.cursor.sh, DNS:prod.authentication.cursor.sh, DNS:*.api2.cursor.sh
[2026-04-03T08:26:19.878Z] DNS Time: 6ms
[2026-04-03T08:26:19.878Z] Connect Time: 145ms
[2026-04-03T08:26:19.878Z] TLS Time: 146ms
[2026-04-03T08:26:19.878Z] Result: true in 454ms

API: Success
Logs:
[2026-04-03T08:26:19.425Z] Start
[2026-04-03T08:26:20.437Z] Result: true

Ping: Success
Logs:
[2026-04-03T08:26:19.426Z] Sending ping 1
[2026-04-03T08:26:20.460Z] Response: ‘ping’ in 1034ms
[2026-04-03T08:26:20.460Z] Sending ping 2
[2026-04-03T08:26:20.865Z] Response: ‘ping’ in 405ms
[2026-04-03T08:26:20.865Z] Sending ping 3
[2026-04-03T08:26:21.237Z] Response: ‘ping’ in 372ms
[2026-04-03T08:26:21.237Z] Sending ping 4
[2026-04-03T08:26:21.403Z] Response: ‘ping’ in 166ms
[2026-04-03T08:26:21.403Z] Sending ping 5
[2026-04-03T08:26:21.890Z] Response: ‘ping’ in 487ms
[2026-04-03T08:26:21.890Z] Result: true

Chat: Success
Logs:
[2026-04-03T08:26:19.427Z] Starting stream
[2026-04-03T08:26:20.375Z] Response: ‘foo’ in 946ms
[2026-04-03T08:26:21.387Z] Response: ‘foo’ in 1012ms
[2026-04-03T08:26:22.386Z] Response: ‘foo’ in 998ms
[2026-04-03T08:26:23.397Z] Response: ‘foo’ in 1011ms
[2026-04-03T08:26:24.395Z] Response: ‘foo’ in 998ms
[2026-04-03T08:26:25.386Z] Result: true

Agent: Success
Logs:
[2026-04-03T08:26:19.428Z] Starting stream
[2026-04-03T08:26:19.429Z] Pushing first message
[2026-04-03T08:26:20.452Z] Response: ‘foo’ in 1023ms
[2026-04-03T08:26:20.954Z] Pushing next message
[2026-04-03T08:26:21.030Z] Response: ‘foo’ in 578ms
[2026-04-03T08:26:21.531Z] Pushing next message
[2026-04-03T08:26:21.620Z] Response: ‘foo’ in 590ms
[2026-04-03T08:26:22.125Z] Pushing next message
[2026-04-03T08:26:22.213Z] Response: ‘foo’ in 593ms
[2026-04-03T08:26:22.719Z] Pushing next message
[2026-04-03T08:26:22.805Z] Response: ‘foo’ in 592ms
[2026-04-03T08:26:22.805Z] Result: true

Marketplace: Success
Logs:
[2026-04-03T08:26:19.417Z] Host: marketplace.cursorapi.com
[2026-04-03T08:26:19.869Z] Response in 452ms
[2026-04-03T08:26:19.869Z] Response: 200
[2026-04-03T08:26:19.869Z] Response Type: cors
[2026-04-03T08:26:19.869Z] Server: null
[2026-04-03T08:26:19.869Z] Result: OK in 452ms

Authentication: Success
Logs:
[2026-04-03T08:26:19.418Z] Host: prod.authentication.cursor.sh
[2026-04-03T08:26:19.916Z] Response: 200 in 498ms

Authentication UI: Success
Logs:
[2026-04-03T08:26:19.424Z] DNS lookup: authenticator.cursor.sh
[2026-04-03T08:26:19.493Z] Resolved authenticator.cursor.sh to 172.64.152.23 in 55ms

Cursor Tab: Success
Logs:
[2026-04-03T08:26:19.424Z] DNS lookup: api3.cursor.sh
[2026-04-03T08:26:19.471Z] Resolved api3.cursor.sh to 104.18.19.125 in 39ms

Agent Endpoint: Success
Logs:
[2026-04-03T08:26:19.424Z] DNS lookup: agent.api5.cursor.sh
[2026-04-03T08:26:19.519Z] Resolved agent.api5.cursor.sh to 44.197.141.31 in 65ms

Codebase Indexing: Success
Logs:
[2026-04-03T08:26:19.425Z] DNS lookup: repo42.cursor.sh
[2026-04-03T08:26:19.507Z] Resolved repo42.cursor.sh to 54.225.232.80 in 65ms

Downloads: Success
Logs:
[2026-04-03T08:26:19.423Z] Host: downloads.cursor.com
[2026-04-03T08:26:19.903Z] Response: 403 in 480ms

CDN: Success
Logs:
[2026-04-03T08:26:19.424Z] Host: cursor-cdn.com
[2026-04-03T08:26:19.738Z] Response: 404 in 314ms

I know that Opus 4.6 can be slow but after this update Composer 2.0 fast also became slow. It used to bu rather quick

8

On deleting chats: I can see the issue is still there after a restart. The fix in 3.0.9 didn’t cover every case, other users confirmed this today too. The team knows about it, and your report helps us prioritize it.

One question: are the chats that come back unfinished drafts that weren’t sent, or normal completed chats with history? This will help narrow it down.

On slow responses: diagnostics look normal and the network seems fine. Opus 4.6 can be slower than other models, but the fact that Composer 2.0 Fast also got slower after the update is worth checking. Can you send the Request ID for a slow request? It’s in the top right of the chat, context menu > Copy Request ID.

9

I have an incurring invoice. Can it be because of this? Perpahps I am getting slow responses due to my unpaid invoice?

Here is the request id for the chat: 396f1867-a1e8-4eaa-af4d-88ed2ac7d77a

10

Yes, an unpaid invoice can definitely be the reason. If your subscription was canceled due to non-payment, your account moves to the Free tier, which can mean lower priority and, as a result, slower responses.

Try going to cursor.com/settings > Manage Subscription and sorting out the invoice. After you pay (or if you decide to stay on Free), the speed should go back to normal.

And about deleting chats, you didn’t answer my earlier question: are the chats that come back unsent drafts or normal finished chats with history? That’ll help narrow down the bug.

11

Screenshot (184)
Screenshot (184)2560×1440 356 KB

12

It looks just like this and when trying to delete them, they are gone on the UI but when creating a new chat and start interaction they reappear