Frequent internal server error in agent chat window

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Internal server error in cursor IDE in agent chat window. I retried it still gets struck with a message saying internal server error. New chat also gets struck here

Steps to Reproduce

Internal server error in cursor IDE in agent chat window. I retried it still gets struck with a message saying internal server error. New chat also gets struck here

Expected Behavior

It should work without error

Screenshots / Screen Recordings

IMG_5808.png
IMG_5808.png2990×2070 808 KB

Operating System

MacOS

Version Information

Version: 3.4.17
VSCode Version: 1.105.1
Commit: 93e603f703cd553a6bb3644711a3379bbbb31180
Date: 2026-05-13T21:39:55.724Z
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: Darwin arm64 25.4.0

For AI issues: which model did you use?

Auto , Sonnet

For AI issues: add Request ID with privacy disabled

Request ID: 7356cd41-2ad9-4a2f-b151-21151629596b

Additional Information

Suggest me a stable version that I can use which doesn’t throw this error

Does this stop you from using Cursor

Yes - Cursor is unusable

5

The issue still persists with choosing specific models like sonnet. Repeatedly get error

6

Can someone help with some workround?

8

I traced your request ID and can see the specific failure: the model returned an empty response during the agent loop, causing a timeout on our side. That particular error was a transient server-side issue.

However, since you’re saying it persists, there’s likely a second problem. Looking at your screenshot, it appears you have both “Disable Http2” and “Disable Http1 SSE” enabled in your network settings. That combination can cause ongoing agent chat failures because it removes the streaming transport the agent relies on. Could you try this:

  1. Open Cursor Settings and search for “http” (as you already have)

  2. Keep “Disable Http2” checked (correct for your network)

  3. Uncheck “Disable Http1 SSE” — this re-enables streaming for agent chat

After making that change, fully quit and relaunch Cursor, then try a new agent chat.

If it still fails, could you share:

  • A new request ID from a recent failure (three dots menu in chat > Copy Request ID)

  • The results from Network Diagnostics (Cursor Settings > Network > Run Diagnostics > “Copy diagnostics”)

That will tell us exactly where the connection is dropping now.