Cursor agent on Windows creates new files with CRLF line endings no matter what, even though LF line ending was specified in all settings (i.e., files.eol, .editorconfig, and .gitattributes), git config --global core.autocrlf is not set, and the whole project uses LF (not CRLF).
Steps to Reproduce
Set files.eol (editor setting) to \n (LF).
Create an .editorconfig in the project root with end_of_line = lf.
Create .gitattributes with * text=auto eol=lf (and no mention of crlf).
Open new chat with any model (tested with Composer 2 and Opus 4.6) and execute this prompt:
❝Create a new test file called hello_world.js that prints “Hello World” to the console when run with Node.❞
This is causing headaches for our team. I’m guessing developers at Cursor are Mac-centric, but we would really appreciate if you could give this some attention. Fancy new features are not valuable if editor basics are broken.
This bug report is a DUPLICATE of the first one below (151096). I am re-reporting because that one no longer allows comments, and Cursor’s bug reporting guidelines say that bugs affecting more users will get more attention. I see no other way to let the Cursor team know that this is still an issue affecting Windows users.
Issues with Cursor converting LF to CRLF or creating files with CRLF despite LF settings have been reported repeatedly for the past 2 months.