Tool call error. Failed to read file

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

No matter what prompt I give it, composer1 always replies with:

“Tool call error. Failed to read file.”

Cursor in unusable at this point.

Steps to Reproduce

No idea how you can reproduce this bug. Everything was working fine before this happened.

Expected Behavior

composer1 is supposed to respond to prompt, even prompts not requiring accessing files. but it keeps on saying ‘Tool call error. Failed to read file’ even if my prompt does not require reading files.

Screenshots / Screen Recordings

tool error.png

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.1.47 (Universal)
VSCode Version: 1.105.1
Commit: 2d3ce3499c15efd55b6b8538ea255eb7ba4266b0
Date: 2025-12-04T02:31:50.567Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 25.0.0

For AI issues: which model did you use?

composer1

For AI issues: add Request ID with privacy disabled

Request ID: eeea8be9-0593-4f31-b88f-3716c2cfe40e
{“error”:“ERROR_BAD_REQUEST”,“details”:{“title”:“Tool call error”,“detail”:“Failed to read file.”,“additionalInfo”:{},“buttons”:,“planChoices”:},“isExpected”:true}
ConnectError: [invalid_argument] Error
at isu.$endAiConnectTransportReportError (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:6409:408775)
at rMo._doInvokeHandler (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:7026:21873)
at rMo._invokeHandler (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:7026:21615)
at rMo._receiveRequest (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:7026:20377)
at rMo._receiveOneMessage (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:7026:19194)
at zPt.value (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:7026:17286)
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 Lpt.fire (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:6394:12156)
at MessagePort. (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:8973:18439)

Does this stop you from using Cursor

Yes - Cursor is unusable

I’m on the Ultra plan. This is the first time I’ve had to hunt down tech support for Cursor. For a top AI company, I thought tech support would be smoother than this, to be honest.

Hey, thanks for the report. This looks like a regression in Composer 1, and we’re already investigating it.

Meanwhile, please run these quick checks and share the results:

  • Settings → Network → Run Diagnostics, and send a screenshot of the result
  • In app settings Cmd+,, search for “HTTP/2”, enable “Disable HTTP/2”, restart Cursor, and test again
  • In agent, switch the model and check if the error persists
  • Open an empty project folder and try the same request there
  • Open Help → Toggle Developer Tools and send Console errors
  • Repeat the request 2-3 times and share the new Request IDs from the chat menu (how to get them: Getting a Request ID | Cursor Docs)

I’ve already escalated the case to the team. Let me know if any of the steps above helps.

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