GPT 5.5 acted upon stale information/wrong message instead of latest message

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

GPT 5.5 acted upon stale information/wrong message instead of the latest message.

The issue that occurred:

  1. I told it to use Unity MCP to fix the fileID issue.
  2. It did so, and reported the fileID issue was fixed.
  3. I noticed it was misinterpreting my rules about using Unity MCP, so I tagged the rules file and asked how to reword it.
  4. It responded stating fileID is broken and is proceeding to fix them. This was already completed previously. I stopped the response.

Steps to Reproduce

Unclear how to reproduce, occurred during normal agent use. Hopefully request ID provides insight.

Expected Behavior

GPT 5.5 should act upon the latest message and not stale information/wrong message.

Screenshots / Screen Recordings

Cursor_hVd3HMqc5B.png
Cursor_hVd3HMqc5B.png1179×1733 323 KB

Cursore3BoTVJXBj
Cursore3BoTVJXBj1166×1405 151 KB

Operating System

Windows 10/11

Version Information

Version: 3.2.16
Commit: 3e548838cf824b70851dd3ef27d0c6aae371b3f0
Date: 2026-04-28T21:07:47.682Z
Layout: editor
Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Cursor/3.2.16 Chrome/142.0.7444.265 Electron/39.8.1 Safari/537.36

For AI issues: which model did you use?

GPT 5.5 High

For AI issues: add Request ID with privacy disabled

Request ID of thread: 4c360f1f-bc27-4cb4-ad8b-67bbbd4d9f2b
Request ID of AI message that exhibited the issue: 57d80ba0-191f-4fcf-b25c-ee566cdea3f8

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

The issue might be that before I told it to use the Unity MCP, it was trying to do it manually. I stopped its response early and told it to use the Unity MCP.

This might be related to another issue I noticed. For example, if I send a message and then immediately stop the response and edit the message, the AI responds as if it received the prior version of the message as well.

7

Hey @KamilTheDev!

It could be that! But there’s also a known bug around the cursor responding to a previous conversation. I actually just had this happen to me and escalated with the team.

I’ll pass your Request IDs on as well!

As a workaround, you may need to start a new chat or even restart Cursor.