{"version":"2.1.299","anchor":"git-status-parsing-fixed-for-crlf-and-leading-space-lines","canonical_anchor":"git-status-parsing-fixed-for-crlf-and-leading-space-lines","heading":"Git status is read correctly for the first file and Windows line endings","tier":"notice","area":"Git","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/git-status-parsing-fixed-for-crlf-and-leading-space-lines","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Git status is read correctly for the first file and Windows line endings\n\nClaude Code no longer misreads the first file in `git status` output and now handles Windows-style line endings\n\n**What**\n\nClaude Code reads the output of `git status` to learn which files have changed. It now handles that output more carefully:\n\n- Lines are split on both Unix and Windows line endings.\n\n- The first line keeps its leading status column, which was previously cut off when the whole output was trimmed first.\n\n- File paths are no longer trimmed of spaces at their ends.\n\n**Why**\n\nThe first changed file could be read wrongly, and output with Windows line endings could leave stray characters in paths. Both now come through as git reported them.\n\n- Area: Git\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}