I don’t think this is so much a bug, but just a design issue. The command palette, the little popup that appears after you type @ and start typing more. This seems to have a very significant limitation on the number of items that can be shown. It is just 16 most of the time, although occasionally I have observed it show up to 20. I’ve never observed more than 20.
When searching for things, I often don’t know the exact name, since a heck of a lot of code files are created by the agent. So I use the context palette to find what I need. This seemed to be easier to do before 2.0, maybe before 1.6. Particularly since the 2.0 release, the behavior of this palette has definitely changed, and it is not nearly as useful or flexible as it once was. Aside from the loss of commands in the palette, it seems to be very restrictive of how many items it will show. Despite the fact that the palette is scrollable, and could therefor show SIGNIFICANTLY more than 16 items at a time.
It would be very helpful if the palette showed more items, and would simply scroll allowing you to visually search through currently matching items for your search thus-far. Even when I do know what I’m looking for, due to the scope of my workspace, certain common terms often have a lot of items. This sometimes leads to one particular kind of item appearing in the palette, while all other items do not appear. For example, I can start a search, and only see directories, but no files, or any other kinds of context items. Or perhaps the opposite, only files, no directories (sometimes, I can type a / at the end to get the directory, however there seems to be a bug, or perhaps several, that cause other items to show up first that are not directories, which again also hampers usage of the palette.)
Perhaps an option to configure how many items the user wants to show in the command palette. At 16 or even 20, its just not much, and since it is scrollable, I’d probably increase the limit to 50 or even more so I can find items more easily. If the palette gets very restricted and stuck on a single item type (i.e. directories only), then I’m often forced to go manually hunting around the codebase to find what I need to attach to manually attach, which takes much longer (especially given how rapidly our projects are growing.)
I think overall, the command palette needs a lot of love in general. It lost a TON in the 2.0 update, and it just isn’t as useful as it once was. There is a bug report open about the inability to find code-level context items anymore…it only shows files, directories, and sometimes (often not) docs, and a couple other things. Mostly just files and directories, which is far less useful than pre-2.0 where we could attach code level items. But the palette in general has always bene a bit cramped, and searching has always had its…quirks. Often instead of showing the hierarchical folder structure for items, it will show a truncated item path instead, which also makes it hard to know if you are picking the right context item (we have many projects in our workspace, so the same file/directory names can be used across projects.) Most command palette commands like @Docs and often @Web are also broken.
Would be really great if the command palette and available commands were given some attention to improve DX with Cursor for agentic coding, since so much time is spent in the prompt and command palette.