Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.265entry #4

Claude Code v2.1.265 ·

Artifact database gains in-place edits, version checks, and access simulation

Artifact database writes can now edit a field in place, check document versions, and simulate lower access levels

Group of 6 Use it now Notable Nothing to try yet In Development
JSON All of v2.1.265
Use it nowTier: how much it should matter to you
4Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
In DevelopmentKind: in v2.1.265,
What probably matters to youSection of the release

What

  • The artifact database's write tool gained a str_replace operation for editing a string field in place by exact old-text/new-text match, instead of resending the whole document. It supports replace_all to replace every match, and reports clear errors when the match can't be made: edit_no_match, edit_ambiguous, edit_field_missing, edit_field_not_string.
  • Writes can now use optimistic concurrency: passing if_version (ifVersion) rejects the write with a version_mismatch error if the document changed since it was last read, and write results can report the document's new version number.
  • A new as_level parameter on read_db/write_db lets the caller simulate reading or writing as a lower access level (interact or admin), to check what a less-privileged user would be allowed to do, without actually lowering the caller's own access.
  • str_replace is threaded through both the single-write and batch (write_db/batch) code paths, and is currently gated off by default behind a feature flag (requiring both the artifact database and a dedicated str-replace flag to be enabled).

Why

These changes let Claude make small, precise edits to artifact database records instead of rewriting entire documents, avoid clobbering concurrent changes via version checks, and preview permission outcomes for other access levels before acting.

Read from
Names in the bundlestr_replaceif_version
Feature flag
tengu_umber_stile Not enough to say

Nothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.

This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.265: off

Read once, for one account on one subscription tier, against v2.1.265. It isn't a statement about your account. What a flag value here can and cannot tell you

What the documentation says
Documented inapi/about-claude/models/migration-guide
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
What has happened since
Flag reading moved The flag server now returns on for tengu_umber_stile, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns off for tengu_umber_stile, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns on for tengu_umber_stile, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns off for tengu_umber_stile, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns on for tengu_umber_stile, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns off for tengu_umber_stile, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns on for tengu_umber_stile, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns off for tengu_umber_stile, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.

See this across every release →

How sure we are
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up str_replace, on Batches.
The name it cites is new in this buildNew in this build: tengu_umber_stile

See this entry in the whole of v2.1.265 →

Feedback