What version of Codex is running?
0.39.0
Which model were you using?
gpt5 (medium)
What platform is your computer?
Microsoft Windows NT 10.0.26120.0 x64
What steps can reproduce the bug?
When codex makes changes to files, it does not adhere to the line endings in the file but appears to alway use Unix-style LF. On Windows with files using CRLF, this leads to inconsistent line endings in the file. When opening these files in Visual Studio, for example, VS warns about this fact and asks whether line endings should be normalized.
What is the expected behavior?
codex should use LF line endings, if the file already uses LF line endings, and CRLF endings if the file already uses CRLF endings.
What do you see instead?
No response
Additional information
No response
What version of Codex is running?
0.39.0
Which model were you using?
gpt5 (medium)
What platform is your computer?
Microsoft Windows NT 10.0.26120.0 x64
What steps can reproduce the bug?
When codex makes changes to files, it does not adhere to the line endings in the file but appears to alway use Unix-style LF. On Windows with files using CRLF, this leads to inconsistent line endings in the file. When opening these files in Visual Studio, for example, VS warns about this fact and asks whether line endings should be normalized.
What is the expected behavior?
codex should use LF line endings, if the file already uses LF line endings, and CRLF endings if the file already uses CRLF endings.
What do you see instead?
No response
Additional information
No response