Thanks for reporting a bug you have found in Cursor!
Please add the following info to help us diagnose your issue:
Check the forum to ensure the issue hasn’t been reported already
Checked, no one reported yet
Provide a clear description of the bug
Cursor mixes what I assume is the communication between cursor and Claude Sonnet? or did it just fail to wrap it’s code? I don’t know. I just report to help developer know that there’s an issue like this. But I believe this is because Claude Sonnet 3.7 is still new, so yeah some bugs are expected.
Explain how to reproduce the bug (if known)
I don’t know, but on my first screenshot, I don’t know why it keeps repeating that for every tasks. The screenshot after that are produced after it continues to send me that message over and over, so I believe that’s what breaks the code or something.
Attach screenshots or recordings (e.g., .jpg, .png, .mp4).
Tell us your operating system and your Cursor version (e.g., Windows, 0.x.x).
Version: 0.46.4 (user setup)
VSCode Version: 1.96.2
Commit: db71624816f6d52f6e54f47c37cdc7df23e22620
Date: 2025-02-25T07:37:34.169Z
Electron: 32.2.6
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Windows 11
Tell us if the issue stops you from using Cursor.
Not really, but it drains my fast request a lot. I just bought Cursor this morning, and this whole thing costs me 160/500 fast requests. I assumed it was because it was the newest model, but then I hit the forum and found out it’s supposed to be the same as other premium models.
