You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
ImprovementsKind: in v2.1.265,
ImprovementsSection of the release
What
When 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.
Why
This 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.
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed sinceAnthropic's documentation has since written up str_replace, on Batches.- `type: "text_editor_code_execution_str_replace_result"`api/messages/batchessee the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up str_replace, on Batches.
