Tool Call Error : Failed read the file

Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I was using sonnet and composer for my code work, i have run lot of prompts, all of sudden it stopped taking new prompts, i am on pro plan, i checked the tokens, they are still available, how to resolve this issue

Steps to Reproduce

run lot of prompts, commit the code to github in the middle of prompt running tasks

Screenshots / Screen Recordings

Screenshot 2025-11-17 140216.png
Screenshot 2025-11-17 140216.png468×541 11.3 KB

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.0.77 (user setup)
VSCode Version: 1.99.3
Commit: ba90f2f88e4911312761abab9492c42442117cf0
Date: 2025-11-13T23:10:43.113Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

all models

Does this stop you from using Cursor

No - Cursor works, but with this issue

2

Hey @Nagarjuna_Koduri, I’ve seen at least one other report with the same “Tool Call Error: Failed read the file”. I don’t know if it’s a broader issue yet, or just a configuration quirk on some setups. Could you try the following that a staff member advised on the other thread?

  1. Create a new chat and run a simple prompt. Does it complete successfully, and does it run successfully if you were to run a prompt that uses the same tool call?
  2. Check for MCP servers:
    • Open Cursor Settings → Tools & MCP.
    • If any MCP servers are listed, try disabling them and test again.
  3. Run Network Diagnostics: Cursor Settings → Network → Run Diagnostics and verify that all indicators are green.
  4. Grab the request ID for the failing tool call: in the current chat menu select Copy Request ID and paste it here.

If the issue persists after these steps, sharing the request ID could let a staff member dig into the details. Let me know what you find.

3

Hey, thanks for the report. This is a known issue with the read_file tool, and the team is actively investigating it.

Immediate workaround: start a new chat so you can keep working.

Important: please avoid reopening the failed chat, as some users have seen code rollbacks there. Make sure you use git to protect your changes.

To help the team look into your case, please:

  • Try a new chat and let me know if it works normally
  • Check MCP servers: Cursor Settings → Tools & MCP - disable any that are enabled and test again
  • Run network diagnostics: Cursor Settings → Network → Run Diagnostics
  • Share the Request ID: in the failed chat, open the menu (top right) → Copy Request ID

Let me know what you find.

4

Facing also the same issue…Any ETA when this blocking issue will be resolved? Thanks