Describe the Bug
With 1.2 when I open the .mdc files it opens in a normal text editor with markdown, and I can’t use @ links, and the existing links shows as markdown links.
Downloaded 1.1.7, it works normally.
Steps to Reproduce
Edit .mdc files.
Expected Behavior
It should use the special editor that correctly shows and creates @ links.
Screenshots / Screen Recordings
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
Version: 1.2.1 (Universal)
VSCode Version: 1.99.3
Commit: 031e7e0ff1e2eda9c1a0f5df67d44053b059c5d0
Date: 2025-07-03T06:08:06.355Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.5.0
Does this stop you from using Cursor
Sometimes - I can sometimes use Cursor
4 Likes
+1, cant use @ in rules files anymore.
and the rules content changed to xxx (mdc:xxxxx)
I’m experiencing the same problem. Only the text editor is available, whereas an MDC editor used to be an option here.
yep… impossible to tag files in rules now, making them 80% unusable
having the same issue for a few weeks. I have nested folders inside .cursor/rules
I also have this issue wih version 1.3.9. project rules are basically unusable
1 Like
Same issue on latest version. Tried creating manually, with the + rule in settings and using the generator (which by the way, its prompt is broken for me, it always puts the markdown in the middle of the header section.)
I think I narrowed down at least for me whats the link which im sure the mods might be happy to hear.
I am working on an external hard drive, an old one, formatted to EXFat.’
The rules seem to work on my c drive but not my L drive.
I suppose it could either be external, or exfat issues, or maybe just not the same drive as cursors installation? who knows.
Its possible one of the above things may be whats interfering.
Confirmed, formatted my drive and changed to nfts and rules now show as normal
