Agent ignores prompt

Describe the Bug

Today agent started to answer to previous prompt, ignoring current prompt. I have to copy-paste 1-2 time to make agent switch to new prompt.

Edit:
True for both 4-sonnet and thinking 4-sonnet.

Steps to Reproduce

Were referencing terminal logs while explaining the bugs

Expected Behavior

Agent should answer the most recent prompt

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.1.3
VSCode Version: 1.96.2
Commit: 979ba33804ac150108481c14e0b5cb970bda3260
Date: 2025-06-15T06:35:49.230Z
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

Does this stop you from using Cursor

No - Cursor works, but with this issue

7 Likes

Same problem here, the cursor ignores new prompts when I stop him and say to make changes.

1 Like

Been seeing similar results since yesterday afternoon.

Version: 1.1.3 (user setup)
VSCode Version: 1.96.2
Commit: 979ba33804ac150108481c14e0b5cb970bda3260
Date: 2025-06-15T06:55:04.603Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.26100

Also seeing this. When you stop the agent, provide feedback and then send, it continues its last stopped effort - blithely ignoring your feedback.

Same here. I can’t get the model to properly “stop” its current line of thought. Even if I “stop” the model several times, or provide explicit instructions to stop, it wont field any new requests unless it’s finished it’s line of thinking. After it finishes thinking/edits it accepts new requests.
To be clear, the stop button still “stops” the model from literally generating text, but it is acting more like a “pause” button. Started behaving like this today for me.

3 Likes

I have noticed this too, and have flagged the issue to the Cursor team.

If you have any examples, please reply to this chat with:

  • Request IDs
  • Your current Cursor version (CursorAbout CursorCopy)
  • What model you are using (this will be in the request ID, but I’d be good to know here so we can observe at a quick glance whether this is specific to Claude)

Personally, I noticed when swapping from Claude → o3 that it followed instructions.

So this is the reason

:warning: Ongoing Service Degradation

Exactly the same for me. Stop is acting like a pause, as summarised above. I created a separate report before seeing this thread. But problem also exist if you try to override whats going on while Cursor awaits for tool invocation confirmation.

Very painful. have to wait for the whole think-cycle which may include editing, trying to commit etc. And only then Cursor is willing to hand over, and I have to rollback everything

I’m using Claude 4 models, and Cursor 1.1.3

Same bug. And I see a lot of similar bug posts in the forum in the past 2 days

Hey team, think we had a bad backend change here, but should be resolved now!
Can anyone confirm this is working again on their end?

1 Like

TBH I kinda got used to start new chat when I need to interrupt the agent :grinning_face:

Better for now, models got noticeably faster for me

1 Like

Better for me - I’m able to stop it, provide feedback, and have it respond to that feedback rather than plowing ahead with its last effort before recognizing the input.

1 Like

Looks like this is resolved now.

Root cause seems to have been a mistake on the backend.

Thank you to everyone for your feedback.

1 Like