Tool call error Failed to read file

Support Bug Reports
1

Request ID: 2f4abbbe-f00f-4e28-93ac-24f918ad5506
{“error”:“ERROR_BAD_REQUEST”,“details”:{“title”:“Tool call error”,“detail”:“Failed to read file.”,“additionalInfo”:{},“buttons”:,“planChoices”:},“isExpected”:true}

2

Hi there!

We detected that this may be a bug report, so we’ve moved your post to the Bug Reports category.

To help us investigate and fix this faster, could you edit your original post to include the details from the template below?

Bug Report Template - Click to expand

Where does the bug appear (feature/product)?

  • Cursor IDE
  • Cursor CLI
  • Background Agent (GitHub, Slack, Web, Linear)
  • BugBot
  • Somewhere else…

Describe the Bug
A clear and concise description of what the bug is.

Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!

  1. …
  2. …
  3. …

Expected Behavior
What is meant to happen here that isn’t working correctly?

Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)

Operating System

  • Windows 10/11
  • MacOS
  • Linux

Version Information

  • For Cursor IDE: Menu → About Cursor → Copy
  • For Cursor CLI: Run agent about in your terminal
IDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......

CLI:
CLI Version 2026.01.17-d239e66

For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)

For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…

Additional Information
Add any other context about the problem here.

Does this stop you from using Cursor?

  • Yes - Cursor is unusable
  • Sometimes - I can sometimes use Cursor
  • No - Cursor works, but with this issue

The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!

4

I have run lot of prompts, all of sudden it stopped taking new prompts.Creating a new session can resolve the issue.

6

Hey, thanks for the report.

This is a known issue. The “Failed to read file” error can sometimes show up after a lot of prompts in a single session. Glad starting a new session fixed it.

If it happens again, it’d help to know:

  • Your Cursor version (Menu → About Cursor → Copy)
  • About how many prompts you send before the error shows up
  • What types of files you’re working with (large files, binaries, etc.)

For now, the workaround is to start a new session when it gets stuck.