{"version":"2.1.314","anchor":"staged-file-edits-skipped-in-diff-rendering","canonical_anchor":"staged-file-edits-skipped-in-diff-rendering","heading":"Staged edits are no longer treated as applied file edits","tier":"notice","area":"File Edits","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/staged-file-edits-skipped-in-diff-rendering","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Staged edits are no longer treated as applied file edits\n\nEdit results marked staged now show no diff and no longer count as completed file changes\n\n**What**\n\nWhen Claude edits a file, the result can now be marked as staged (`staged === true`). A staged edit has been prepared but is not treated as a finished change. Claude Code now handles staged results differently in two places:\n\n- Diff display: the function that renders an edit's diff, which is the before-and-after view of the changed lines, now returns nothing for a staged result. Before, it went straight to reading the edit's `structuredPatch`.\n\n- Applied-edit check: the check that decides whether a result counts as a completed file edit now returns false for a staged result. Before, it only looked for a `filePath` together with a `structuredPatch` or the content of a newly created file.\n\n**Why**\n\nIn practice, a staged edit shows no diff, and anything Claude Code normally does after a completed file edit does not run for it. If you see an edit with no diff shown, it may have been staged rather than applied.\n\n- Area: File Edits\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}