# Disabled optional Team Rules remain injected into fresh Agent chats **URL:** \ **Category:** Bug Reports\ **Tags:** context, rules\ **Created:** [September 9, 2026, 7:39am UTC](https://forum.cursor.com/t/disabled-optional-team-rules-remain-injected-into-fresh-agent-chats/171139 "2026-09-09T07:39:29Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Guillaume1](https://avatars.discourse-cdn.com/v4/letter/g/c5a1d2/32.png) [@Guillaume1](https://forum.cursor.com/u/Guillaume1)\ **Post date:** [September 9, 2026, 7:39am UTC](https://forum.cursor.com/t/disabled-optional-team-rules-remain-injected-into-fresh-agent-chats/171139/1 "2026-09-09T07:39:29Z")
### 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: > [@Disabled team rules still loaded into context and reported as always applied workspace rules](https://forum.cursor.com/t/disabled-team-rules-still-loaded-into-context-and-reported-as-always-applied-workspace-rules/160899): > > Where does the bug appear (feature/product)? Cursor IDE Describe the Bug My entreprise ships 23 team rules, of which 3 are mandatory and 20 can be toggled off. Toggling off the 20 optional rules doesn’t change anything, these are still loaded into the agent context, we can see that from the context usage or from asking a fresh agent what rules it has loaded Steps to Reproduce Enable optional team rules Start a fresh agent and ask it to report the rules it currently have loaded based on its p… ### 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 ---
**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\ **Post date:** [September 9, 2026, 10:21am UTC](https://forum.cursor.com/t/disabled-optional-team-rules-remain-injected-into-fresh-agent-chats/171139/5 "2026-09-09T10:21:51Z")
Hey @Guillaume1, thanks for the detailed report,! I can reproduce what you are describing, and it comes down to the rule’s name. Team rules are matched against your local “disabled” list by the last segment of the name, so a rule called `foo/bar` is compared as `bar` and the match never lines up. Rules whose names contain a `/` cannot currently be switched off locally, which is why this one slips through while your other rules behave normally. I’ve flagged this to the team so the matching gets fixed. In the meantime, renaming the rule so it has no slash should make the toggle work. Could you try this and let me know? ---
**Author:** ![Guillaume1](https://avatars.discourse-cdn.com/v4/letter/g/c5a1d2/32.png) [@Guillaume1](https://forum.cursor.com/u/Guillaume1)\ **Post date:** [September 9, 2026, 10:49am UTC](https://forum.cursor.com/t/disabled-optional-team-rules-remain-injected-into-fresh-agent-chats/171139/11 "2026-09-09T10:49:34Z")
Yes, i am trying now, will let you know. ---
**Author:** ![Guillaume1](https://avatars.discourse-cdn.com/v4/letter/g/c5a1d2/32.png) [@Guillaume1](https://forum.cursor.com/u/Guillaume1)\ **Post date:** [September 10, 2026, 8:50am UTC](https://forum.cursor.com/t/disabled-optional-team-rules-remain-injected-into-fresh-agent-chats/171139/12 "2026-09-10T08:50:20Z")
Indeed fixed, thanks