We need an “describe” function in app
“describe @codebase” and it should spit it out. What it knows.
There wassa funny point when Agent revealed too much behind the BlackBox… However, when I am asking MY agent (I own its awareness) I should be able to ask it anything about how its interacting with my codebase.
Well this is interesting:
1 Like
That would be awesome. Mostly I just want it to be better about figuring out which files are relevant and related (figuring out where functions/classes are called/defined etc.)
OK so it finally got out of the rut of always looking in these files, I think after I explicitly asked it to show me anything from any file that was not a pre.yaml file.
However, it still seems really terrible at determining which files to look in. Even if I give it hints or clues about what files it should probably look in, or tell it to check everywhere, the shortlist of files in the codebase it tends to look in is not fruitful. It’s generally very bad at answering questions that require it to find files in the codebase.
For example asking things like “What is the chain of events after this form gets submitted and what files does it happen in?” or the like often results in it saying it can’t find that info and that it must be outside of the codebase which it is not. It even specifically called out one of our own modules which was imported in the node_modules folder and said it was an external library that it didn’t have access to, despite the name of that folder being identical to the name of the main codebase root folder and having the same name as a directory within that root folder.
Getting answers to the codebase is my top feature from Cursor since I’m newer to this project and the large codebase is difficult and time-consuming to search through manually.
Funny, now I’m having the opposite issue. I’m asking chat a question about our backend which is all generated using cloudformation so the info I need would be in a .yaml file but chat won’t look in a single yaml file even if I specifically tell it to only look in files that end in .yaml. I’m also giving it clues about what types of directories to avoid. Now it refuses to look in any yaml files, and is only looking at angular files.
We have seen that the codebase-wide context feature can seemingly ‘ignore’ when you mention a specific file type, and are working to improve that at the moment.
For these kinds of issues with context and file searching, I’d really recommend trying out Composer - we’ve recently added our auto-context feature, which should do a similar job but be more intelligent regarding what files it pulls in.
You can access it with Cmd/Ctrl + I, and it’ll automatically find relevant context based on your prompt. Plus you can always explicitly tell it which files to look at using @ symbols
Check out the docs here for more details: Cursor – Welcome to Cursor
Checked, don’t see any posts about this
Whenever I use @codebase or cmd enter to ask questions, Curosor always only looks at the same yaml files and nothing else
Ask any question using @codebase
Attached screen snip showing the files it’s looking at
Versions:
Yes, if I can’t find an answer to this I am definitely going to end my premium Cursor subscription and probably stop using Cursor altogether
