I find that the ‘cd’ (change directory) command causes a lot of issues on bigger projects. The cursor agent loses track of where it is, it doesn’t reliably check ‘pwd’ to move around, and it starts applying changes that impact similarly named directories but in the wrong place.
So I set a rule to NEVER use ‘cd’ in my global cursor rules. However, at almost every next hour, it forgets the rule. Almost as if rules ONLY apply to code and not to CLI commands the agent can issue.
I remind it and have to pay super close attention on every command.
Thanks for reporting a bug you have found in Cursor!
Please add the following info to help us diagnose your issue:
I checked the forums and there’s nothing specific that I can find about rules applied to commands.
Above ^
Create a global rule “Do NOT use cd unless I specifically mention it. let’s run ALL commands from project root with full directory paths from project root.” Then start a new project with a create react app boilerplate (any framework including just python works, but react has a large directory footprint). You can even nest things for getting it to come up quickly…example nest a git submodule.
Attach screenshots or recordings (e.g., .jpg, .png, .mp4).
Tell us your operating system and your Cursor version (e.g., Windows, 0.x.x).
Mac OS 15.4.1
Version: 0.49.6
VSCode Version: 1.96.2
Commit: 0781e811de386a0c5bcb07ceb259df8ff8246a50
Date: 2025-04-25T05:07:16.071Z (1 wk ago)
Electron: 34.3.4
Chromium: 132.0.6834.210
Node.js: 20.18.3
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.4.0
Tell us if the issue stops you from using Cursor.
No, but it’s frustrating when I saved a rule.