The string to replace was not found in the file.

I often observe that when the model tries to edit a file in the agent mode, it often attempts to do a string replace in the file and fails, and attempts again with a different tool, I assume, and succeeds. This is probably the first tool call that it always takes up, but it always ends up failing.

A good way to reproduce this bug is just to ask Cursor in an agent mode to edit a file. Don’t give it clear parameters on what needs to be edited. Let it come up with a plan to edit multiple files and see how it performs.

Version: 1.0.0
VSCode Version: 1.96.2
Commit: 53b99ce608cba35127ae3a050c1738a959750860
Date: 2025-06-04T19:21:22.523Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.5.0

1 Like

Yes this is very annoying.
It keeps doing that and then it fixes it, then does it again, then fixes it… and so on. Massive bug that probably costs immense redundant computing power.

I see this a lot also.
Just assumed it was a failed search.

I will have to watch more closely.