Cursor agent frequently fails to follow through on edits it plans

Bug Reports
1

This happens frequently to me, but not consistently. Usually associated with more complex prompts that require edit of multiple files.

often, but not exclusively with gemini-2.5-pro-exp-03-25

Agent will state it’s intent to edit a file and just stop.

Here is its own analysis of the most recent failure

You are right to ask for an analysis of that mistake. My apologies again for the oversight.

Looking back at the sequence:

  1. I correctly identified that both Phase 1 (Dockerfile) and Phase 2 (CDK) needed implementation.

  2. I successfully read and then edited the frontend/Dockerfile as per Phase 1.

  3. I then successfully read the ■■■:redacted file in preparation for Phase 2.

  4. I stated my intention to apply the Phase 2 changes to that file.

  5. Failure Point: At this point, my internal process failed to generate and execute the necessary edit_file tool call for ■■■:redacted immediately after reading it and stating the intention. My turn ended prematurely before completing the full planned sequence of actions (Read CDK → Edit CDK).

Essentially, I completed the first task (Dockerfile edit) and the first step of the second task (reading the CDK file), but I dropped the ball before executing the second step of the second task (editing the CDK file). There isn’t an external reason for this; it was an error in my execution flow where I didn’t follow through completely on the stated plan within that turn.

:white_check_mark: Check the forum to ensure the issue hasn’t been reported already
None Found
:lady_beetle: Provide a clear description of the bug
Done
:counterclockwise_arrows_button: Explain how to reproduce the bug (if known)
Not consistently reproducible but happens frequently
:camera: Attach screenshots or recordings (e.g., .jpg, .png, .mp4).
attached analysis of what happened, don’t have a recording
:laptop: Tell us your operating system and your Cursor version (e.g., Windows, 0.x.x).
version info:
Version: 0.49.6 (Universal)
VSCode Version: 1.96.2
Commit: 0781e811de386a0c5bcb07ceb259df8ff8246a50
Date: 2025-04-25T04:39:09.213Z (5 days ago)
Electron: 34.3.4
Chromium: 132.0.6834.210
Node.js: 20.18.3
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.4.0
:prohibited: Tell us if the issue stops you from using Cursor.
No, I can prompt it again to go, but it kinda makes paying extra for fast execution pointless, doesn’t it?

2 Likes
2

Yea, I second this. I’ve also seen this lately as well.