Best hidden function on cursor

Today I found an option that was not in the documentation that for me is working better than code indexing itself and absurd
It’s great for composer
I’ll send a photo and answer me, did you know about this function?

13 Likes

That’s a sneaky feature. Thanks for letting us know!

What have been your use-cases / experiences with it so far?

For future readers who are also wondering what the function does, and don’t have Cursor at hand right at this moment:

It adds all search hits to the Composer context.

4 Likes

open all the relevant files in the editor, then go to composer and do this to quickly add all of them to the composer:

5 Likes

I found that last night and even still the overall workflow is still kinda wonkey.

It’s great that cursor is vscode fork, but that also limits it.

Working with chat, compare as now MCPs which have agentic, multi model, and live access to code base is a vastly different workflow than a contained up that vscode six provides to cursors scaffolding.

It would be cool to have a composer challenge to break the entire hi/up of the cursor environment into fully separate windows for each workflows interface:

Meaning;

Make all “panels” floating objects- I want to drag my chat and composer and terminal and etc wherever I want.

I know there are billions of super experienced devs used to the historic ide, but there are the new billions “Young Domesticated Apes” (ai called humans that see JRE)…

Or maybe I’m a dumb domesticated ape who doesn’t know shAIt.

Interesting point of view.
I’d like to add to it by giving a perspective that oposes it.

I like the way cursor is currently integrated with this “old” vscode IDE.
Because in a market where we have many “AI driven coding” platforms, cursor remains true to its purpose which is providing the fine detailed control over your code base, control provided by vscode which in itself is feature rich, while aided by AI.

In summary what I mean is I don’t want any cursor updates that would simplify the interface by abstracting what is going on while it changes my code, I like having a detailed view and control of whats going on in the code base and this is provided by this vscode features.

About floating detached panels, IMHO they are bad, they hover over the editor and block code view, I like side panels better as they never block the view by hovering over code or other interfaces. You can quickly open/close side panels using keyboard shortcuts, it is refreshing pressing esc a few times and see all panels gone, only the editor at view, reduces my cognitive overload, and then just call the side panel pack, or terminal, etc, by just hiting the keyboard.

Also, separating cursor itself too much from the interface could break the “flow” state of coding sessions because of context shifting (user interface wise), I like being as close to the editor as possible.

Anyway, its just another pov, it was great reflecting on these points. I appreciate the opportunity.
Best regards.

Tested this by refactoring a user flow with by opening 3 repositories in a vscode workspace, FE - GQL and BE. Searched for the flow name, added all to composer.

Worked so good as it should not be that much.
thanks

1 Like

It’s becoming increasingly useful in many ways.

Excellent observation you have. Reason

this is not a feature it’s a shortcut to get around an unbelievably clunky workflow that cursor could spend its time on rebuilding instead of updating ctrl K