[2.6.19] Request ends early with Auto and must paste prompt in new chat

[MidnightOak]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Intermittently, the response seems to end early and only run for a second or so after submitting.

Steps to Reproduce

Use Auto, submit prompt, wait and after a second the response ends with nothing to show, copying the prompt into a new chat and submitting, works.

Expected Behavior

Should give a full response

Operating System

Windows 10/11

Version Information

Version: 2.6.19 (user setup)
VSCode Version: 1.105.1
Commit: 224838f96445be37e3db643a163a817c15b36060
Date: 2026-03-12T04:07:27.435Z
Build Type: Stable
Release Track: Default
Electron: 39.4.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.19045

For AI issues: add Request ID with privacy disabled

Request IDs:
8e304820-7e6a-440c-9d19-13171f052514
12dc9724-efee-4626-b416-18614c1ca242

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

[deanrie]

Hey, thanks for the report.

A couple things to try so we can narrow this down:

1. Does this happen with a specific model, or does it also happen when you manually pick one like Claude Sonnet or GPT-4o instead of Auto?
2. Please run network diagnostics: Cursor Settings > Network > Run Diagnostics, then share the results here.
3. Are you using a VPN or a corporate proxy? If yes, try turning it off and see if the issue still happens.
4. Please also try turning off HTTP/2: App Settings Ctrl+, > search HTTP/2 > turn on Disable HTTP/2, then restart Cursor.

Since pasting the same prompt into a new chat works, it sounds like it could be a connection drop or something context-related in longer sessions. Let me know if any of this helps, or share a bit more detail.

[MidnightOak]

It hasn’t happened again, but it was happening in new chats. It would just respond after thinking for a second with nothing. Then I copied the prompt and pasted it into the bottom of the chat instead of resubmitting the above (previous) prompt. This it would work. It only happened with Auto (several times in a row), and has not happened since, but I will try your solutions next time it happens, and also try different models.