Cursor's projectRules cannot recognize

[Drenayo]

cursor version: 0.51.2 1.0.0
Unity version: 2021.3.32
Cursor plugin version: 2.0.25

Issue encountered:
When I use any version of Cursor to open an empty folder project and write .mdc rules, in CursorSetting-Rules-ProjectRules, all the already created project rules are displayed normally.
When I use Cursor to open a Unity project and write .mdc rules, it works the first time, but after closing Cursor and reopening it, CursorSetting-Rules-ProjectRules shows "No Project Rules Yet".

[Drenayo]

"Additional clarification: When I open Cursor by double-clicking script files, there's also a chance that the project won't be recognized properly. This specifically manifests as showing 'Unable to open folder' where the script directory should normally be displayed. I have to go back to External Tools - External Script Editor dropdown, deselect Cursor, and then select it again. This issue cannot be accurately reproduced - sometimes it occurs, sometimes it doesn't.
Furthermore, when I open scripts by double-clicking them, the rule recognition issue mentioned above will definitely occur. However, if I open Cursor separately and then open the project folder through the 'Open Folder' method, the rules can be recognized normally."

[altynius]

Confirmed! I have the rule lost every time “open c# project” in Unity.
Cursor version: 1.0.0
Unity version: 6000.1.6f1
Cursor plugin version: 2.0.25

[TXINX]

Confirmed! I have the rule lost every time “open c# project” in Unity. Cursor version: 1.0.0 Unity version: 6000.1.6f1 Cursor plugin version: 2.0.25

Same thing happens.
Cursor:1.1.3
Unity:6000.1.5f1
Cursor plugin version: 2.0.25

[altynius]

Has anyone been able to solve the problem in any way?

[Drenayo]

Has anyone been able to solve the problem in any way?

"if I open Cursor separately and then open the project folder through the 'Open Folder' method, the rules can be recognized normally."

You can try this form. It works when opened this way, but it won't work when opened through unity

[boxqkrtm]

It appears that Cursor was launched by simply opening a file, rather than through the normal execution process.

When launched via the extension method, the folder is set and opened by default, which allows the Cursor rules to be recognized properly.

if "cursor" option below grey bar
it's wrong case

ps. It could also be a case that was fixed due to code changes made in the meantime.

@Drenayo