{"version":"2.1.265","anchor":"str-replace-edits-to-artifact-live-file-data-are-now-checked","canonical_anchor":"str-replace-edits-to-artifact-live-file-data-are-now-checked","heading":"str_replace edits to artifact live-file data are now checked as an 'update' permission rule","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/str-replace-edits-to-artifact-live-file-data-are-now-checked","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### str_replace edits to artifact live-file data are now checked as an 'update' permission rule\n\nEditing artifact live data with str_replace is now checked and can be denied as an 'update' permission rule\n\n**What**\n\nWhen a `str_replace` operation is used to edit artifact files or live-document data, Claude Code now treats it the same as a database 'update' operation for the purposes of matching your permission rules. If a rule denies it, you'll see a message explaining that a str_replace counts as an update and that nothing was written.\n\n**Why**\n\nThis closes a gap where editing artifact live data via str_replace might not have been checked against 'update' permission rules the same way other update operations are, so your existing rules for controlling updates now apply consistently to this kind of edit too.\n\n- Area: Artifacts\n- Names: `str_replace`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}