If you can't find the code in the Cursor multi-repository workspace, check whether the correct root directory is opened. Many people open the parent directory, soft link directory, or individual subpackages, causing Cursor to index only a part of the file, and the agent naturally can't find the implementation in another repository.
Look where you open it first
Look at the top-level directory in the Explorer on the left side of Cursor. If you want to change a monorepo, you should open the monorepo root directory; If you only open 'packages/web', the Agent may not see 'packages/api', shared components, and root configurations.
Conversely, if you open an oversized parent directory, such as '~/work' with a dozen items, the index will be slower and it will be easier to mix extraneous code into the context.
Multiple workspaces should be clear in scope
Multi-warehouse workspaces aren't always better. You can add frontend, backend, and public libraries to the workspace, but be clear when asking: "Only search in the web and API roots, don't look at archived projects." ”
If the Cursor index results are unstable, first use a file search to confirm whether the target file is visible, and then let the agent search it. Documents cannot be found, and it is impossible for agents to know out of thin air.
Check for Ignore Rules
.cursorignore, .cursorindexingignore, and .gitignore can all affect reads and indexes at different levels. A common problem in large repositories is to ignore 'dist' and 'build', but they also ignore the build type, schema, and client SDK, resulting in the agent lacking key context.
It is recommended to evaluate files that are "generizable but affect understanding" separately and not ignore them across the board.
Resolution Order
The first step is to reopen the correct project root. The second step is to make sure that the target file can be found in the normal search. The third step is to check the Cursor index status. The fourth step is to clean up the ignoring rules. The fifth step is to name the path in the question.
The most reliable way to ask is: "Please first search for the order interface in 'packages/api', then find the call in 'packages/web', and finally only modify the plan." This is much higher than the hit rate of "help me fix the order bug".
