How can I request a refund if the current issues are severely impacting my usage and preventing me from completing tasks?
me too ，long time
me too. It’s completely unusable.
This happens to me a lot. I hit the stop button and then tell it to coninue and it usually comes back.
my main issue is HOW SLOW it is now, it smashes my cpu 100% (one core only) every time the agent is doing anything, even thinking, and i can’t use the rest of the program while it’s doing that. My state.vscdb file is like ~10GB though and it might have to do with that but there’s no docs on how to clean it up anywhere, vacuuming it does nothing.
same issue, why?
This issue very serious, but nobody can resolve it……
已解决，中国大陆用梯子的，用verge，开tun和http2就行
Sharing a reproducible workaround from mainland China:
Environment:
- macOS
- Proxy client: Verge
- Issue: Cursor stuck on “Taking longer than expected”
Workaround:
- Turn on TUN mode.
- Ensure Cursor domains are routed through the proxy.
- Include
*.cursor.shin addition tocursor.com. - Leave HTTP/2 enabled.
Result:
- Without this, requests often hang.
- With this, requests may still be slow for a moment, but they eventually go through.
This may help narrow the issue down to network routing / HTTP2 / regional connectivity.
I had the same issue, and disabling HTTP/2 fixed it.
I’m experiencing the same issue. HTTP/2 is already disabled, and the network diagnostics pass, but the problem still occurs. When I use Visual Studio Code under the same network conditions, everything works fine.
Im also facing same issue. Not Taking too longer than expected. But Performance of Agent Coding are very slow than normal.
Hey, here’s a fresh update for everyone in this thread.
We made a few improvements that should help with this issue. If you’re on a version below 2.6.20, please update and check if it’s better. The next release will also include additional improvements.
A few notes from the thread that might help as a temporary workaround:
- Long chats: @vince and others noticed this happens more often in long chat sessions. If everything freezes, try starting a new chat with the same prompt.
- Reindexing: this helped some users. File > Preferences > Cursor Settings > Indexing & Docs > Delete and Reindex.
- Cursor Skills: @Johannes_Claesson found that incorrectly formatted files in
.cursor/skillscan cause freezes. Please check the format of your skills files. - Switch models: instead of Auto, try selecting a specific model.
Note: if you previously tried switching to HTTP/1.1 and it didn’t help, that can be expected in some cases. The improvements in 2.6.20 fix the issue at a different level.
If this is still happening after updating to 2.6.20 or newer, please send:
- Your Request ID (chat menu in the top right > Copy Request ID)
- Your Cursor version (Help > About)
- Whether it happens in all projects or only one
This will help us narrow it down and understand what class of issue your case fits into.
@Graham_Dawe, @jtreminio, @Bikram_Agarwal, @Cormac1, @Mark_Ledwich, @houshanren, @fring_zhao, @Sean_Ahern, @b1ncer, @touchair, @vince, @dabing, @dvv101111, please try updating if you haven’t already, and let us know how it goes.
@Wesley_Diogo, if Cursor is completely unusable and the standard steps don’t help, you can email [email protected].
I’ll post here when there are more updates.
RequestId:f6b72961-0d05-47e0-b19a-60a9891a0610
Version: 2.6.22 (user setup)
VSCode Version: 1.105.1
Commit: c6285feaba0ad62603f7c22e72f0a170dc8415a0
Date: 2026-03-27T15:59:31.561Z
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.19045
I am a new user, and this phenomenon has only occurred in one project so far
I have tried all the solutions you listed earlier, but they have been ineffective. The probability of this malfunction occurring is high, which greatly affects the efficiency of research and development
The same issue persists. I’ve been unable to connect for the past two days, and it always takes longer than expected
Version: 2.6.22 (user setup)
VSCode Version: 1.105.1
Commit: c6285feaba0ad62603f7c22e72f0a170dc8415a0
Date: 2026-03-27T15:59:31.561Z
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.19045
Request ID: 4e7dec94-6ffe-4d1a-af5d-026ded9efe25
{“error”:“ERROR_NETWORK_ERROR”,“details”:{“title”:“Network Error”,“detail”:“Unexpected seqno: 2 != 1. Please try again, or contact support if the issue persists.”,“isRetryable”:true,“additionalInfo”:{},“buttons”:,“planChoices”:},“isExpected”:false}
[unavailable] Unexpected seqno: 2 != 1. Please try again, or contact support if the issue persists.
die: [unavailable] Unexpected seqno: 2 != 1. Please try again, or contact support if the issue persists.
at e9A (vscode-file://vscode-app/d:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34265:23755)
at Z5A (vscode-file://vscode-app/d:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34265:22658)
at a9A (vscode-file://vscode-app/d:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34266:6285)
at Xou.run (vscode-file://vscode-app/d:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34266:10400)
at async qOa.runAgentLoop (vscode-file://vscode-app/d:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:46830:10206)
at async b5u.streamFromAgentBackend (vscode-file://vscode-app/d:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:46884:9277)
at async b5u.getAgentStreamResponse (vscode-file://vscode-app/d:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:46884:13663)
at async vMe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/d:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34327:17597)
at async Object.Ea [as onSubmit] (vscode-file://vscode-app/d:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:45811:4826)
at async vscode-file://vscode-app/d:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:45785:57069
try again
Request ID: ffe2c88d-9255-4c72-8535-b2cacd6fc751
[internal] Failed to establish a socket connection to proxies: PROXY 127.0.0.1:7890
die: [internal] Failed to establish a socket connection to proxies: PROXY 127.0.0.1:7890
at e9A (vscode-file://vscode-app/d:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34265:23755)
at Z5A (vscode-file://vscode-app/d:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34265:22658)
at a9A (vscode-file://vscode-app/d:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34266:6285)
at Xou.run (vscode-file://vscode-app/d:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34266:10400)
at async qOa.runAgentLoop (vscode-file://vscode-app/d:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:46830:10206)
at async b5u.streamFromAgentBackend (vscode-file://vscode-app/d:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:46884:9277)
at async b5u.getAgentStreamResponse (vscode-file://vscode-app/d:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:46884:13663)
at async vMe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/d:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34327:17597)
My issue was resolved by adjusting my Windows PATH environment variable. Even though I had specified an absolute path to my shell in my configuration C:\foo\bar\zsh.exe, Cursor was often unable to run the shell. The problem manifested itself by Cursor failing to run any agent (even down in WSL, where the shell is entirely different). Once I added C:\foo\bar to my Windows PATH env variable, Cursor became happy again.
Though I’m happy that the problem is resolved, I’m surprised by 1) that this problem was intermittent and didn’t always fail and 2) that setting the PATH would affect running a shell defined with an absolute path.
@deanrie none of those are solutions.
1: If i start a new chat i loose all context
2: Can’t do that every 15 mins (average my chat get stuck)|
3: i dont use skills
4: i always use opus 4.6, never use the Auto mode.
Sometimes restarting cursor help unstuck, but most of the time a stuck session is dead and will never ever work again. Happens when context is charged by 20% or more.
This happens since cursor 2
Version: 2.6.20
VSCode Version: 1.105.1
Commit: b29eb4ee5f9f6d1cb2afbc09070198d3ea6ad760
Date: 2026-03-17T01:50:02.404Z
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: Darwin arm64 23.4.0
ee144cf2-2e27-46b4-8c4f-ae8330fd49e8 The issue still persists.
