Make a single parent folder for your workspace.
I have been having issues with Cursor not seeing my entire codebase.
This manifests issues like:
- creating files that already exist, but with slightly different names
- deleting files I am using in other contexts
- giving advise that I should create configs or settings that are already being used
- ignoring existing project configs and overwriting them for ‘an example of this…’
From reading all the issues in the forum that deal with ‘Cursor not seeing entire codebase’, the indexing process makes some false assumptions that 1 folder = 1 workspace.
It seems like cursor has no concept of a ‘workspace’ and assumes that the first folder it sees is the entire workspace.
So, indexing (embedding) never sees any files in sibling folders.
If you add a parent folder, and put all repos for the project in that single parent folder, you can then either open the folder, or define a workspace with that single parent folder.
Then, Cursor will index all contents of the ‘first’ folder, which will be the collection of all repos.
So, if you are working on projects that span muliple teams or repositories, there seems to be an extra nesting step needing to help Cursor ‘see’ the entire project.