Monorepo correct support and rules deduplication

[Moumouls (Antoine Cormouls)]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

In a monorepo, we are forced to use symlinks, so when we work in specific packages (open vs code directly into the package), the rules are included in the correct context.

However, when working with extensions like folke.vscode-monorepo-workspace, which create VS Code workspaces on the fly, and you select multiple packages to work on, the behavior changes.

The symlinked rules are included X times in the context once per package, so the context gets bloated and becomes very expensive.

This is a bug. As a safety net, I expect Cursor to avoid duplicating rules in the context. A simple strict equality check before including a new rule would prevent this. I believe this is easily shippable and would avoid unnecessary token usage.

I already opened a thread about this here but was closed, and still no fix

Mono repo and cursor rules

Where does the bug appear (feature/product)? Cursor IDE Describe the Bug We use a symlink trick in our monorepo to share certain rules between the root and the sub-packages. We have a postinstall script that symlinks the root .cursor folder into each package, allowing our developers to work either from the root or within a sub-package independently (without requiring the root to be in scope). This technique currently works, and it seems you’ve implemented (please confirm) a system that preven…

Steps to Reproduce

• Create a monorepo
• Create some rules at the root
• Symlink the root rules into each package
• Create packages A, B, and C
• Install the folke.vscode-monorepo-workspace extension or create a VS Code workspace manually
• Select 1 package
• Say “hello” to the agent → context usage is X%
• Add another package to the context
• Say “hello” to the agent → context usage is 2×X%
• And so on…

Expected Behavior

Cursor SHOULD ensure that there are no duplicated rules in the context.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.3.29
VSCode Version: 1.105.1
Commit: 4ca9b38c6c97d4243bf0c61e51426667cb964bd0
Date: 2026-01-08T00:34:49.798Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 25.2.0

Additional Information

For a billion-dollar company, I hope a simple strict equality check is doable. (Sorry for the tone, but this issue is really annoying it can waste a lot of tokens and degrade AI capabilities, which is the worst of both worlds.)

Does this stop you from using Cursor

Yes - Cursor is unusable

[deanrie]

Hey, thanks for reopening this request.

This is a known issue. Cursor doesn’t deduplicate rules yet when working with multi-root workspaces. The team is already working on a fix to deduplicate rules on the backend.

There’s no exact ETA yet, but it’s a priority. Once the fix ships, it should automatically resolve the symlink situation in a monorepo.