Cursor's Apply Model Made No Changes to the File (or Mangled the Edit)

Symptoms

• The chat model proposes a correct-looking change, but the applied file is mangled: code lands in the wrong place, unrelated lines get deleted or duplicated.
• The edit goes into a completely different file, or a brand-new file is created instead of editing the target.
• You see 'The apply model made no changes to the file' over and over.
• In long threads, the agent reads and writes stale or corrupted versions of files.
• Repeated failed applies push the agent to delete and recreate files, nearly losing code.

Why it happens

A second, smaller model does the applying

Cursor uses a separate, smaller apply model to merge the chat model's proposed edit into the actual file. That merge step can misplace diffs, and large files are where it goes wrong most often.

Internal file state drifts from disk

In long threads, Cursor's internal view of a file falls out of sync with what is on disk (a state-synchronization issue between the LLM interface and the filesystem), so applies target stale or wrong content. Many successive edits to the same file make it worse.

How to fix it

1. Reject the mangled applyReview every diff before accepting, and reject a bad apply outright rather than letting the agent fix it with more applies. Repeated failed applies have pushed the agent into delete-and-recreate territory, which is how code nearly gets lost.
2. Restore the corrupted fileUse 'Restore Checkpoint' on the prompt in chat, the file's Timeline (local history), or 'git checkout -- <file>' if the file was committed. Pick whichever holds the most recent good copy.
3. Start a fresh chat with the file attachedWhen applies fail or loop with 'made no changes', long-thread state drift is the usual trigger. Open a new chat and re-request the edit with the target file explicitly attached via @file.
4. Restart Cursor to re-sync file stateIf edits keep targeting stale content or the wrong file, restart Cursor. That forces it to re-read file state from disk instead of its drifted internal copy.
5. Ask for smaller edits in smaller filesThe apply model misplaces hunks most often in giant files. Keep files small and request scoped edits, one concern at a time.

How to prevent it

• Commit before multi-file agent edit sessions so any mangled apply is one 'git checkout' away from recovery.
• Keep files small; giant files are where apply merges go wrong.
• Start fresh chats for new tasks instead of pushing long threads where file state drifts.
• Never accept a diff you have not read, especially in files you did not ask Cursor to touch.

Tools that actually fix this

Recommended because they address the failure mode above, not because of the payout. Some are affiliate links; see how we choose.

Frequently asked questions

Sources

• Cursor forum: File editing tools not functioning properly in Cursor IDE
• Cursor forum: Apply changes wrong file
• Cursor forum: Edit tool failure and broken apps
• Cursor forum: Corrupted file read/edit tools in long threads
• Cursor forum: Updated a different file than the one in the editor

Related errors