.cursor/rules are not found by the agent when using a multi-root workspace (with the root and, for example, a package of the monorepo selected).
When not using multi-root, it works.
Steps to Reproduce
Create a monorepo-like structure (root, packages/packageA, packages/packageB).
Add a .cursor/rules file to the root folder.
Using VS Code’s multi-root workspace (selecting both packageA and root), ask the agent to perform a task in packageA. The rules are not applied.
Expected Behavior
Rules from the root should be applied. Ideally, even without adding the root folder to the multi-root workspace, Cursor should recursively check parent folders for the existence of a .cursor/rules folder.
Currently, there is no solution. Using symlinks in each package completely breaks the context, since Cursor seems to include all rules from the root and its subdirectories by default.
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
Using Cursor rules in a monorepo is a nightmare if you want to work scoped on a package (either by opening Cursor directly on the package folder or by using the multi-root system).
WARNING: Using symlinks in each package is not a valid workaround and will exponentially increase token consumption.
Is the issue here that you have rules at a project root but are only opening subfolders, and not opening the actual root itself so the rules there don’t get picked up? Is the issue with multi-root or does it also reproduce if you just open a subfolder rather than the project root?
Yes, i only open subfolders when i’m working on monorepo. In multi root (include the root and a subfolder) the behavior seems also broken. It’s not easy to understand also what rules cursor can actually see and use
WARNING: Using symlinks in each package is not a valid workaround and will exponentially increase token consumption.