Cursor Responds to Ghost Messages Which Were Never Sent

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Starting from around a week ago, many of my chats have odd responses at the end. The model often suggests I sent a follow up message when I did not. In this example, it thinks I sent an empty message. In other cases it thinks I sent it instructions to do something I did not. For example, it will often say I told it to implement a plan or make a change, when I did not. In these cases it ends up making changes I need to revert, and wastes tokens.

Steps to Reproduce

I don’t do anything special other than start chatting. It happens in both the Cursor Editor and Agents window. Happens on Composer 2, Opus, Sonnet, so it is not model specific. It does not occur on every message. I used to think it only happened on long chats, but this example here happened after only one message.

Expected Behavior

Cursor should not act like I sent it blank messages, and it definitely should not act like I asked it to do things I did not.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

Version: 3.1.15 (system setup)
VSCode Version: 1.105.1
Commit: 3a67af7b780e0bfc8d32aefa96b8ff1cb8817f80
Date: 2026-04-15T01:46:06.515Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.17763

For AI issues: which model did you use?

Verified on Composer 2, Opus 4.6, Opus 4.7, Sonnet 4.6.

For AI issues: add Request ID with privacy disabled

The request ID is 3669740a-bfbf-48ab-8125-d5db822e79c3, and I have also attached a screenshot of the chat in case this is not visible on your end.

Additional Information

This bug makes the model highly unpredictable since it refuses to follow directions.

I am using HTTP Compatibility Mode 1.1 and Network Diagnostics all pass.

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

Hi @MikePendo,

Thanks for the report! This looks to be in the same class of bug as the one reported here:

I’ve linked your report to our internal tracking ticket for that issue.

Thanks again for the detailed repro info (request ID, version, models tried). That’s really helpful!