Hey, thanks for the detailed report and for gathering all the duplicates in one place.
This is a known bug. When creating new files on Windows, Cursor doesn’t respect files.eol, .editorconfig, or .gitattributes. Instead, it uses a heuristic based on existing files in the workspace or the OS default, which is CRLF on Windows. The team is aware, but there isn’t a specific ETA for a fix yet. Your report helps with prioritization since a lot of users have hit the same thing.
Unfortunately, there isn’t a good workaround specifically for creating new files. The only option is to manually change the line endings after the agent creates the file using the status bar in the bottom right. Click CRLF and switch it to LF.
Main thread to track: Cursor update changed line endings in entire codebase without consent
We’ll post an update there when there’s progress.