We find that on windows (2.6.12) if the user launches cursor through the vs code workspace file then there’s a chance that the root AGENTS.md does not get loaded into the context.
It works when launching cursor without a workspace then opening the project from within.
============================
To verify, ask the agent “list all the always_applied_workspace_rule by name, do not read any file“.
This is the only reliable way to verify because if the AGENTS.md is loaded, it’s represented as <always_applied_workspace_rule name={file path of AGENTS.md}>{file content}</always_applied_workspace_rule>in the context.
Do NOT trust the rules dashboard in cursor settings as those can be misleading (when the bug happens the AGENTS.md shows up there but not in the context).
macOS seems to be ok.
============================
I seriously don’t understand why cursor can’t get this simple thing right, these days you can vibe code stuff more reliable than this…
For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)
For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…
Additional Information
Add any other context about the problem here.
Does this stop you from using Cursor?
Yes - Cursor is unusable
Sometimes - I can sometimes use Cursor
No - Cursor works, but with this issue
The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!