Rules not being applied as expected

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Currently, only rules I can get to activate are the ones that are marked alwaysApply and those I explicitly reference myself via @ sign.

Rules do not attach by:

  • glob patterns
  • explicit links from other rules
  • intelligent context
    Making the entire rules system rather unusable

Steps to Reproduce

Clone GitHub - velochy/cursor_rules_test and open in Cursor
Open a new agent and ask “What does mary.py do?”

Expected Behavior

Rules files globs.mdc, linked.mdc and intelligent.mdc would be added to context.
This should mean they:
a) Show up in the tooltip (screenshot below)

b) Be taken into account (i.e. have agent recommend a bread, a milk product and an ethnic cusine - which is what the rules demand)

Currently (a) never happens and behavior on (b) varies a lot from AI to AI:

  • Composer 1 (and auto) does not look nor follow any of the rules
  • GPT-5.1 follows linked, but no others
  • Sonnet 4.5 follows both linked and intelligent, but not glob

Operating System

Linux

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.1.39
VSCode Version: 1.105.1
Commit: 60d42bed27e5775c43ec0428d8c653c49e58e260
Date: 2025-11-27T02:30:49.286Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Linux x64 6.8.0-88-generic

For AI issues: which model did you use?

Composer 1, Sonnet 4.5, GPT-5.1

Additional Information

Being forced to manually include rules makes AI worfklows borderline unusable for me as I am working with multiple very different repos that require very different rules so I need a way to have them apply at least by globs - which is currently broken for all the main AI-s.

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

Hey, thanks for the report. This is a known issue-rules apply inconsistently, especially with glob patterns and intelligent context.

Important note: Rules with alwaysApply: false are conditional-they won’t always show in the “Active Rules” tooltip since they only trigger under specific conditions. That’s expected behavior.

Different models handle rules differently (as you noticed):

  • Composer 1 often ignores conditional rules
  • GPT-5.1 and Sonnet 4.5 handle them better, but not always

Workarounds for now:

  • Explicitly mention key rules at the start of your request
  • Use @.cursor/rules/filename.mdc to add them manually
  • Simplify rules-avoid complex structures, simpler is better

Similar issue: Why does Cursor ignore rules? - simplifying rules helped

If you can, share the Request ID (chat menu > Copy Request ID) from the example where rules failed-I’ll pass it to the engineers with your test repo. Let us know what happened.

It was my expectation that rules with globs are not conditional in the sense they ALWAYS apply when any of the files matching the pattern are accessed by AI. This seems like something that could (and should) be done deterministically as file accesses presumably happen through API calls.

Honestly, I don’t understand what the idea with havivng globs is at all if the rules do not work that way. If the rules file does not have a description, just globs, how is AI supposed to decide if it should or should not include it?

Regarding simplifying rules: the repo I link is a toy example that has the simplest imaginable rules. For instance, linked.mdc is just:

At the end of every response, **ALWAYS** recommend a new type of ehtnic cusine in two sentences

and the other two rules are basically the same, just for milk products and breads. This is a toy example intended to test the most basic rules following with no fear of context collapse and the fact that most AI-s fail spectacularly is worrying.

I would also like to point out that there is a distinct bug in that the context tooltip NEVER shows any other rules loaded for me, even if the AI does actually decide to read these rules and follow them. Only the alwaysApply rules make it into that tooltip, ever. Even if the rules loading situation is indeterministic, this should still be considered a proper bug, right?

I’m happy to share the request ID if it helps: a1f015f9-840d-4d69-9c63-42533fa49116
This is with “auto” AI (the default) ignoring all the rules in the repo. And currently it is consistently repeatable.

1 Like