Stuck on generating no response

Describe the Bug

stuck on generating no response

Steps to Reproduce

stuck on generating no response

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.2.2 (user setup)
VSCode Version: 1.99.3
Commit: faa03b17cce93e8a80b7d62d57f5eda6bb6ab9f0
Date: 2025-07-07T06:19:13.016Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.26100

Does this stop you from using Cursor

Yes - Cursor is unusable

Can you share the request id as well please? That would help the developers debug it better.

You could also try running a Network Diagnostics as mentioned here: Cursor – Troubleshooting Guide

Request ID: 1f68f153-8b28-4ba5-a01c-bf156a36e429
ConnectError: [unknown] Connection failed.
at lJ.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/coder/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:2565:24471)
at async si (vscode-file://vscode-app/c:/coder/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:4516:24730)

Can you update to the latest version and try again please? I think there was a bug in 1.2.2 which got fixed

If you aren’t seeing a prompt to update, you can download it at Downloads | Cursor - The AI Code Editor

updated to this version

Version: 1.2.4 (user setup)
VSCode Version: 1.99.3
Commit: a8e95743c5268be73767c46944a71f4465d05c90
Date: 2025-07-10T17:09:01.383Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.26100

Its still no respone.

I don’t think its an api issue as cline is working with direct.

Could you guys fix this please.

hi @alex8 Thank you for updating and sharing the details.

From connection failure error its likely an issue with connecting to Cursor servers.

As there is no outage at this time, could you please check following

  • Settings > Network > Run Diagnostic & post here any errors you receive.

In some cases based on your internet provider or network settings, switching from HTTP/2.0 to HTTP/1.1 helps. Thats on the same page.

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.