After closing and re-opening Cursor, I see the problems like I would have expected when removing the class 
Still a problem. I have reported the issue via Cursor.
Version: 0.49.6
VSCode Version: 1.96.2
Commit: 0781e811de386a0c5bcb07ceb259df8ff8246a50
Date: 2025-04-25T04:44:33.500Z
Electron: 34.3.4
Chromium: 132.0.6834.210
Node.js: 20.18.3
V8: 13.2.152.41-electron.0
OS: Linux x64 6.8.8-1-default
This is still an issue, what is the cursor team doing??
1 Like
It’s happening on 0.50.3 too sadly
Alright so for the poor souls that still get this error, but are way too deep into cursor to give it up, I found this idea on reddit:
Basically, you can just save the file, delete all the code inside so that it doesn’t give more warnings and then delete the file again.
Probably the file will still live in cursor memory or something, but this should clean up all the annoying warnings.
1 Like
Restarting Cursor can also solve this problem.