There is a bug where i can't use cursor

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

everytime when i ask a question it will jump up and thought, but after some time it came back to where it was, but with no warnings or errors. Sometimes it can give answers but it is obviously not complete, i dont know what is wrong, just feels like the api is stuck

Steps to Reproduce

just ask question in agent window

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

Version: 3.5.17 (user setup)
VSCode Version: 1.105.1
Commit: d5b2fc092e16007956c9e5047f76097b9e626ca0
Date: 2026-05-20T02:43:31.559Z
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

For AI issues: which model did you use?

Sonnet 4.6, but this problem is on all the models

For AI issues: add Request ID with privacy disabled

Request ID: b7beffec-3028-47ef-8c97-d50bf33b5c1d

Additional Information

look at the picture i give, the answer is not complete, but the model stopped

Does this stop you from using Cursor

Yes - Cursor is unusable

We checked the request ID you shared. On our side, the model actually generated a complete response (the full Python overview you asked for). The issue is that the streaming connection to your Cursor client appears to be dropping during delivery, so you’re only seeing a partial response before it cuts off.

This is a connection-layer issue rather than a model problem. A few things to try:

  1. Disable HTTP/2: Open App Settings (Ctrl+,), search for “HTTP/2”, and enable Disable HTTP/2. This often fixes cut-off responses when the connection is unstable.

  2. Run Network Diagnostics: Go to Cursor Settings > Network > Run Diagnostics and copy the results here. This will help us see the connection quality between your machine and our servers.

  3. Check your network setup: If you’re behind a corporate proxy, firewall, or any network restrictions, those can interrupt the streaming connection. Trying a different network is a good test.

If the issue persists after disabling HTTP/2, please share:

  • The Network Diagnostics results

  • A Request ID from a new attempt where the response was still cut off