@Colin Just checking in to see if there is any update/ETA on when this might get fixed? Currently I am working around this in a hacky-fashion by having a sessionStart hook which finds all my rules from my kit that didn’t get inserted into context (in either list), and either including their full body (for always apply - which is the same amount of context that would be used if they had been inserted as they should have been), or their location/description and an instruction to cursor to search this set of rules as well when it scans the agent_requestable section).. Not ideal, and very much prone to the agent deciding not to do it anyway, but .. better than nothing in the interim.
@JT_Traub I’m told this should be fixed now, even without a client update (you may need to restart Cursor first).
I’ve tested on my side, and everything seems to be in order. Could you give it a try?
@Colin
This is still not behaving as it should.
Version: 3.8.24 (user setup)
VS Code Extension API: 1.105.1
Commit: cf80f4b937f3b9c48070d7085129a838ce7876a0
Date: 2026-06-24T06:55:08.142Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.256
OS: Windows_NT x64 10.0.26200
request id: d4834c06-a70e-42d2-970d-869848a22d32
In my ~/.cursor/rules, there is only one mdc, and it is set to always apply. There are no rules in the project. Another issue is that currently, it seems impossible to view or add user-level mdc rules in Cursor, you can only directly add a single rule.
Hey @jalenz!
This doesn’t sound like the same issue. Cursor doesn’t support storing user rules in ~/.cursor/rules
sorry, got it