I have been unable to use Agent Mode since yesterday.
Whenever I send a request in Agent Mode, the agent does not proceed and remains stuck under the chat box with the following statuses:
Planning next moves
Taking longer than expected…
Reconnecting
After waiting for a long time, I eventually receive the following error:
Internal Error
An unexpected error occurred on our servers. Please try again or contact support if the issue persists.
Request ID: 94c0240c-1d20-4528-9b4a-c3aa73153cce
Error details:
[internal] Cancellation token requested for stream 3e320669-197a-4925-948a-09b092c9c512
RetriableError: [internal] Cancellation token requested for stream 3e320669-197a-4925-948a-09b092c9c512
at z6f (vscode-file://vscode-app/c:/Users/HP/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:8346:137535)
at Pto (vscode-file://vscode-app/c:/Users/HP/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:8346:135961)
at g4f (vscode-file://vscode-app/c:/Users/HP/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:8347:13639)
at Object.classify (vscode-file://vscode-app/c:/Users/HP/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:8347:17861)
at l4f (vscode-file://vscode-app/c:/Users/HP/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:8347:5924)
at async Gto.run (vscode-file://vscode-app/c:/Users/HP/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:8347:17168)
at async Cle.runAgentLoop (vscode-file://vscode-app/c:/Users/HP/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:8447:30991)
at async rBo.streamFromAgentBackend (vscode-file://vscode-app/c:/Users/HP/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:17887:16374)
at async rBo.getAgentStreamResponse (vscode-file://vscode-app/c:/Users/HP/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:17887:37100)
at async CDe._submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users/HP/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:8425:4549)
I have already tried:
Switching to different Agents/models.
Starting a completely new chat/conversation.
Retrying the requests multiple times.
However, I experience exactly the same issue every time.
I noticed this occurred at approximately Sep 10, 08:20 PM (server time).
For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)
For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…
Additional Information
Add any other context about the problem here.
Does this stop you from using Cursor?
Yes - Cursor is unusable
Sometimes - I can sometimes use Cursor
No - Cursor works, but with this issue
The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!
Yes, I’ve had the same issue since yesterday, and Cursor has been absolutely unusable during that time.
Steps to Reproduce: Enter any question in the chat. Wait for the response. I see the following:
Planning next moves
Taking longer than expected…
Reconnecting
Then always say: After waiting for a long time, I eventually receive the following error: Internal Error An unexpected error occurred on our servers. Please try again, or contact support if the issue persists.
Request ID: ed35ce35-8e92-4522-98de-86a1d1ea23e7
[internal] Cancellation token requested for stream 33302507-e2ea-427f-9146-ce3427d8a9be
RetriableError: [internal] Cancellation token requested for stream 33302507-e2ea-427f-9146-ce3427d8a9be
at z6f (vscode-file://vscode-app/c:/Users/egore/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:8346:137535)
at Pto (vscode-file://vscode-app/c:/Users/egore/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:8346:135961)
at g4f (vscode-file://vscode-app/c:/Users/egore/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:8347:13639)
at Object.classify (vscode-file://vscode-app/c:/Users/egore/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:8347:17861)
at l4f (vscode-file://vscode-app/c:/Users/egore/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:8347:5924)
at async Gto.run (vscode-file://vscode-app/c:/Users/egore/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:8347:17168)
at async Cle.runAgentLoop (vscode-file://vscode-app/c:/Users/egore/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:8447:30991)
at async rBo.streamFromAgentBackend (vscode-file://vscode-app/c:/Users/egore/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:17887:16374)
at async rBo.getAgentStreamResponse (vscode-file://vscode-app/c:/Users/egore/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:17887:37100)
at async CDe._submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users/egore/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:8425:4549)
Your requests are reaching us and the model is replying, but the response stream isn’t making it back to your machine, so you get the endless “Planning next moves / Reconnecting” and then that error. That’s almost always a VPN, antivirus/“web protection”, proxy, or ISP holding back the streaming connection, not your setup.
Try in order:
Cursor Settings > Network > HTTP Compatibility Mode → HTTP/1.1, fully quit and reopen Cursor, then send a quick “hello” in a new Agent chat.
Still stuck? Set it to HTTP/1.0 (long-polling), quit/reopen, try again.
Still stuck? Temporarily disable any VPN/proxy/antivirus web protection, or try a phone hotspot.
If none of those work, run Cursor Settings > Network > Run Diagnostics and paste the output plus a fresh Request ID, and I’ll dig deeper. Network troubleshooting