Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
An optional Team Rule remains injected into the Agent context after it has been explicitly disabled in Cursor’s Customize → Rules interface.
The affected rule is General/coding-discipline. The team dashboard identifies it as Optional, and its local toggle is off. Nevertheless, a completely fresh Agent chat reports the rule as active and can reproduce its contents.
The test was performed in a fresh workspace connected to an empty folder. There is no local .cursor/rules directory, .cursorrules file, AGENTS.md, or coding-discipline.mdc file.
Cursor appears to ignore the local opt-out and inject the disabled Team Rule as an active workspace rule.
This resembles a previously confirmed issue that was reportedly fixed in v3.7.39:
Steps to Reproduce
Create an optional Team Rule in the Cursor team dashboard. In this reproduction, the rule is named General/coding-discipline.
Confirm in the dashboard that the rule is marked Optional, not required or enforced.
In Cursor IDE, open Customize → Rules.
Disable coding-discipline so its toggle is gray/off.
Run “Developer: Reload Window” or restart Cursor.
Open a new workspace connected to an empty folder.
Start a completely fresh Agent chat.
Ask: “List only the rules already active in your context. Do not search files or retrieve rules by name.”
Observe that General/coding-discipline is still listed as active.
The Agent can also reproduce the detailed contents of the rule despite finding no corresponding rule file locally.
Expected Behavior
An optional Team Rule that has been disabled locally should not be included in the Agent’s context.
General/coding-discipline should not be listed as active, influence Agent responses, or consume context after its local toggle has been switched off.
Required or enforced Team Rules may remain active, but optional rules should respect the user’s local opt-out.
Operating System
Linux
Version Information
Cursor IDE 3.19.13
For AI issues: which model did you use?
The behavior should be independent of the selected model because the rule appears to be injected by Cursor’s context-building system
Additional Information
The reproduction uses an empty folder and a fresh conversation, which rules out repository-level rules and previous chat context.
The repository and home directory were checked for local rule sources. No .cursor/rules, .cursorrules, AGENTS.md, or coding-discipline.mdc source was found.
Other optional Team Rules that remain locally enabled appear normally. The problem is specifically that General/coding-discipline remains active despite its local toggle being off.
The exact rule name and contents are available to the Agent without filesystem retrieval, indicating that the rule is still being supplied in the request context.
Does this stop you from using Cursor
No - Cursor works, but with this issue