Follow Discord
Sweep 22 Sep 2026 · 17:19Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.265 ·

str_replace edits to artifact live-file data are now checked as an 'update' permission rule

Editing artifact live data with str_replace is now checked and can be denied as an 'update' permission rule

TierYou'll noticehow much it should matter to you
Useful2my rating, 1 to 5
Signal1worth watching, 1 to 5
AreaArtifactswhat it touches
KindImprovementsin v2.1.265,
You'll notice

Editing artifact live data with str_replace is now checked and can be denied as an 'update' permission rule

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.

Read from
Names in the bundlestr_replace
What the documentation says
Since it was published

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 since Anthropic's documentation has since written up str_replace, on Batches. - `type: "text_editor_code_execution_str_replace_result"` api/messages/batches see 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.

See this entry in the whole of v2.1.265 →

Feedback