My enhanced Cursor AI is now able to create its own project rules from my instructions.
The latest release (0.46.9) seems to now prevent Cursor AI from editing files of any type in .cursor/rules. The edit tool is not able to generate edits ro *.txt as well as *.mdc files in the project rules folder. However, it works great everywhere else.
This is a breaking, unannounced change that completely destroys how I work with Cursor.
OK, the issue is more generalized. Any folder or files that starts with a dot (.) is no longer editable by Cursor AI. This is really problematic. Not only can’t my augmented Cursor AI edit project rules himself, configuration files that start with a . are no longer editable by the AI.
Oddly when I asked AI to check why the changes weren’t being added, it appeared to see the changes it expected, while to me checking the file in a text editor, they had not been made.
While this was done for other purposes, I use symlinks to map .cursor/rules and .cursorrules, to other parts of my project structure. Instructing the AI assistant to go through these symlinks solved the problem for me.
My comment that this was fixed was based on the latest release notes, not on actual testing on my part.
