Bad Request Since Updating to 2.0.38

Bug Reports
1

Describe the Bug

Cant send any messages on the editor or agent since updating to Version: 2.0.38 (Universal)

Any message content is unsendable

Steps to Reproduce

No messages are sending for me on any agent on any model. Restarted cursor and the Mac.

Expected Behavior

Chat to work.

Screenshots / Screen Recordings

Screenshot 2025-10-30 at 09.47.19.png
Screenshot 2025-10-30 at 09.47.19.png1039×354 18.2 KB

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.0.38 (Universal)
VSCode Version: 1.99.3
Commit: 3fa438a81d579067162dd8767025b788454e6f90

For AI issues: which model did you use?

Sonnet 4.5 and all others

For AI issues: add Request ID with privacy disabled

Request ID: bc3d8646-b8df-48b9-8b51-8b2647f5c2a8
{“error”:“ERROR_BAD_REQUEST”,“details”:{“title”:“Bad request.”,“detail”:“Bad Request”,“isRetryable”:false,“additionalInfo”:{},“buttons”:,“planChoices”:},“isExpected”:true}
ConnectError: [invalid_argument] Error
at Iqc.$endAiConnectTransportReportError (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:7337:399337)
at nwo._doInvokeHandler (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:490:36007)
at nwo._invokeHandler (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:490:35749)
at nwo._receiveRequest (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:490:34514)
at nwo._receiveOneMessage (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:490:33336)
at WDt.value (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:490:31429)
at _e._deliver (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:49:2962)
at _e.fire (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:49:3283)
at agt.fire (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:7322:12156)
at MessagePort. (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9845:18403)

Does this stop you from using Cursor

Yes - Cursor is unusable

2

Hey, thanks for the report. The “Bad Request” error may be related to context limits. Please try:

Reduce context:

  • In Chat settings, lower the context window size or disable sources (Files, Folders, Docs, MCP servers, etc.)

Clear chat history:

  • Start a new chat

Check token usage:

  • See if you’re hitting any limits

Also try:

  • Settings → Network → Run Diagnostics
  • Disable HTTP/2 if you’re on a VPN

When this happens, are you using a large codebase or pulling many files into context?

3

Ah yes - nothing worked until I disabled contentful MCP?! Weird