Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
(Pro User here)
Cursor is consistently stripping UTF-8 BOM and messing up EOL (LF/CRLF) settings, regardless of .editorconfig or VS Code settings.
Why this is a deal-breaker:
Environment Requirements: I must use UTF-8 BOM for my specific environment. Cursor ignores this and forces a silent change to plain UTF-8.
Git Chaos: By stripping the BOM and changing line endings, Cursor creates “ghost diffs” where the entire file appears modified in Git. This makes code reviews a nightmare and ruins our commit history.
4 Months of Neglect: This bug has been reported for nearly 4 months. As a [Pro/Paying] user, it’s unacceptable that a “next-gen” IDE fails at basic file saving integrity.
Bottom line:
I’m paying for an AI tool to save time, not to spend my day manually reverting encoding and EOL changes that Cursor keeps breaking.
Fix the file-saving logic to respect existing encodings and EOL. Now.
Platform: [ Windows 11 ]
Cursor Version: [2.5.26]
Steps to Reproduce
Generate qt cpp code in Cursor’s agent mode, which must appear
Expected Behavior
keep original encoding and eol
Operating System
Windows 10/11
Version Information
Version:2.5.26(user setup)
For AI issues: which model did you use?
all
Does this stop you from using Cursor
No - Cursor works, but with this issue