{"version":"2.1.267","anchor":"contextcheckpoint-diffing-extended-to-cover-file-writes-no","canonical_anchor":"contextcheckpoint-diffing-extended-to-cover-file-writes-no","heading":"Context\/checkpoint diffing extended to cover file writes, not just artifacts","tier":"notice","area":"Checkpoints","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/contextcheckpoint-diffing-extended-to-cover-file-writes-no","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### Context\/checkpoint diffing extended to cover file writes, not just artifacts\n\nClaude Code's checkpoint diffing now tracks file writes and edits, not just artifacts\n\n**What**\n\nThe internal system that tracks changes across a conversation's checkpoints used to only follow artifact tool calls. It now also follows file write and edit tool calls, and reports a `kind` of either 'artifact' or 'file' for each tracked change. It also counts failed edits (an edit that tried to replace text that didn't match) in a new `editsFailed` counter, and returns a `kept` list showing which artifacts are still the final version at the point in the conversation being examined.\n\n**Why**\n\nThis extends the diffing and checkpoint machinery so it can account for direct file edits alongside artifact publishing, which should make version tracking and rollback more accurate when a session mixes both kinds of changes.\n\n- Area: Checkpoints\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}