# Cursor ignores rules

**URL:** <https://forum.cursor.com/t/cursor-ignores-rules/153998>\
**Category:** Bug Reports\
**Tags:** openai, rules\
**Created:** [March 7, 2026, 8:32pm UTC](https://forum.cursor.com/t/cursor-ignores-rules/153998 "2026-03-07T20:32:15Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![KES](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/kes/32/88659_2.png) [@KES](https://forum.cursor.com/u/KES)\
**Post date:** [March 7, 2026, 8:32pm UTC](https://forum.cursor.com/t/cursor-ignores-rules/153998/1 "2026-03-07T20:32:15Z")

</div>

### Describe the Bug

I started to use 2.5/2.6/2.7 versions. What I noticed cursor stops to follow defined rules. The AI agent is the same Chat GPT-5.2.

### Steps to Reproduce

Create rules, upgrade from 2.3 to 2.5, try to implement some feature.

### Expected Behavior

on 2.3 version I see that cursor follow all rules. Yes, it works more slowly 30-60 mins, it takes much tokens, but solutions worth that. On 2.5 and 2.7 versions it does faster, but it ignores my rules and finally I spent even more time. In other words Cursor requires from me more interactions with it and spent more time without achieving results I got on 2.3 version.

I hope you will create cursor version which will follow the rules as accurate as as 2.3.

### Operating System

Linux

### Version Information

Version: 2.3.21  
VSCode Version: 1.105.1  
Commit: 68e0a0385b87408d050869ea543e3778ad53f780  
Date: 2026-01-02T23:46:13.381Z  
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.17.0-14-generic

### For AI issues: which model did you use?

ChatGPT5.2high thinking.

### Does this stop you from using Cursor

Yes - Cursor is unusable

---

<div class="post-metadata">

**Author:** ![KES](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/kes/32/88659_2.png) [@KES](https://forum.cursor.com/u/KES)\
**Post date:** [March 7, 2026, 8:35pm UTC](https://forum.cursor.com/t/cursor-ignores-rules/153998/3 "2026-03-07T20:35:45Z")

</div>

![_5](https://us1.discourse-cdn.com/cursor1/original/3X/b/2/b20d7f7646129baa202a13068b685040ad24391f.png)  
Here you can see how older and newer versions implement features.  
The cursor on newer versions ignores that branches should be named as `feature/*`.  
This is the only issue I can show visually. Though is a small part of many other issues regarding rules.

---

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [March 8, 2026, 6:36am UTC](https://forum.cursor.com/t/cursor-ignores-rules/153998/4 "2026-03-08T06:36:21Z")

</div>

Hey, thanks for the report. I can see from the screenshot that branches are being created as `tmp/*` instead of `feature/*` based on your rules.

A few things changed in how rules work between 2.3 and 2.5+. To help narrow this down, could you share:

1. The contents of your `.cursor/rules` directory, especially the rule file(s) related to branch naming. Are you using `.mdc` files with frontmatter like `alwaysApply: true`, or plain `.md` files?
2. Which Cursor version are you currently on? The version info in your report shows 2.3.21. Is that the version where it still worked, or is that your current version?

If your rules are in the older format, plain `.md` without frontmatter, make sure they include frontmatter with `alwaysApply: true` so they’re always included in context:

```plaintext
---
alwaysApply: true
---

your rule content here

```

Let me know the details above and we can dig deeper.

---

<div class="post-metadata">

**Author:** ![KES](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/kes/32/88659_2.png) [@KES](https://forum.cursor.com/u/KES)\
**Post date:** [March 10, 2026, 1:56am UTC](https://forum.cursor.com/t/cursor-ignores-rules/153998/5 "2026-03-10T01:56:00Z")

</div>

I have only `.cursor/rules` file. Nothing else here.

Ok. So format was changed, then it would be nice to warn user about that and suggest to convert it automatically using AI agent to the new format. (I suppose autoconvertion could broke something, but that is fine. At least other parts still work, instead of just turned off silently).

Eg. I suppose you can prepend by this template whole `.cursor/rules` file.

2.3 is the version I downgraded to and where rules are working.

---

<div class="post-metadata">

**Author:** ![johnnyboi91](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/johnnyboi91/32/101000_2.png) [@johnnyboi91](https://forum.cursor.com/u/johnnyboi91)\
**Post date:** [March 10, 2026, 3:24am UTC](https://forum.cursor.com/t/cursor-ignores-rules/153998/7 "2026-03-10T03:24:01Z")

</div>

so just to make sure, you have ‘rules’ file inside your ‘.cursor’ folder, is that right? if so, then i guess that is the problem why your rules are not being loaded because ‘rules’ should be the folder (subfolder of pre-mentioned ‘.cursor’ folder, inside project root) where each rule should be defined in separate .mdc file each. so for example if you have 3 rules (just example), like ‘rule-1’, ‘rule2’ and ‘this-rule’, they should all be in this format (see Dean’s comment for proper formatting):

```markdown
–--
alwaysApply: true
---

your rule content here

```

and they should be in (each):

- project\_root/.cursor/rules/rule-1.mdc
- project\_root/.cursor/rules/rule2.mdc
- project\_root/.cursor/rules/this-rule.mdc

this is just an example and should be adopted per your needs/requirements.. hopefully this helps a bit

---

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [March 10, 2026, 9:38am UTC](https://forum.cursor.com/t/cursor-ignores-rules/153998/9 "2026-03-10T09:38:27Z")

</div>

@KES Hey, yep, that’s exactly the issue. `.cursor/rules` should be a folder, not a file. @johnnyboi91 explained it well in the post above.

Fastest way to migrate: rename your current file, then use the Command Palette (`Ctrl+Shift+P` \> “New Cursor Rule”). It’ll create the folder and files in the correct format automatically.

On your point about warning users during the upgrade and offering auto-conversion, that’s valid feedback. I’ll flag it with the team.

Let me know if rules start working after the migration.

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\
**Post date:** [April 1, 2026, 9:39am UTC](https://forum.cursor.com/t/cursor-ignores-rules/153998/10 "2026-04-01T09:39:09Z")

</div>

Closed on April 1, 2026, 9:39am UTC

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.
