This is probably a low-priority bug, but just in case no one has mentioned it: if you delete a folder and then accidentally select it as the context, the system won’t generate a response, and it won’t say that’s the reason.
Hi @Kiryll and welcome to Cursor Forum 
thats a very interesting find.
Could you provide more information to reproduce it?
- How can you select a folder if its deleted?
- Which model did you use?
- Which Cursor version do you have?
I totally get that it is strange someone would do this, in my actual instance of discovery, it kind of made sense, as I was iterating on a prompt with many different folders being called in via @
Its not the you can select deleted folders, its that selected folders that get deleted still have the representative icon in the element showing selected files/folders, if an ‘@’ is called for it in chat. I think this problem is aesthetic at most with my video example, this still appearing.
the other issue then being that you cant understand what’s breaking it after clicking run because it just kind of goes into a blank generate-looking state without errors.
Cursor About copy:
Version: 1.0.0 (user setup)
VSCode Version: 1.96.2
Commit: 53b99ce608cba35127ae3a050c1738a959750860
Date: 2025-06-04T19:44:25.253Z
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
Yeah, its clear now how it could happen. Definitely an edge case.
Will let the Cursor Team know. Thank you for reporting it and for all the details!