Follow Discord
Sweep 06 Nov 2026 · 01:32Z Build v2.1.319 537 read Stable v2.1.311 Latest v2.1.318 Next v2.1.319 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.265 ·

Artifact db_read/db_write gain an as_level run-as parameter with server-confirmed enforcement

Artifact database calls can now request a different access level, and results say whether the server actually enforced it

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

Unclear What as_level and as_level_confirmed actually represent or enable is not established by this finding.

What

  • db_read and db_write calls can now include an asLevel parameter (returned as as_level), letting a call ask to run as if at a different access level.
  • Results now include as_level_confirmed (from the server's levelConfirmed field), reporting whether the server actually enforced the requested level; when unconfirmed, a caveat message is added.
  • The batch-write fallback path also tracks this confirmation across a sequence of writes, and appends a warning to error messages when a requested level wasn't confirmed, noting the writes may have run at the caller's own level instead.
  • The db_write validation schema was updated to accept the new as_level (max 16 characters) and as_level_confirmed fields.

Why This makes it clear when an artifact database operation requesting an elevated or different access level actually got that treatment from the server, instead of silently succeeding or failing under the wrong permissions.

Read from
Names in the bundleas_levelas_level_confirmed
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 as_level, on Claude Code changelog. * Fixed artifact database write results telling Claude that every viewer sees a write to a viewer's private `data/users/` subtree, and added a "view" level to `as_level` changelog see the edit
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhat as_level and as_level_confirmed actually represent or enable is not established by this finding.
Anthropic's documentation agreesAnthropic's documentation has since written up as_level, on Claude Code changelog.

See this entry in the whole of v2.1.265 →

Feedback