Follow Discord
Sweep 25 Sep 2026 · 19:33Z Build v2.1.283 504 read Stable v2.1.274 Latest v2.1.283 Next v2.1.283 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.281entry #342

Claude Code v2.1.281 ·

Shared artifacts get a first-party type check and a new type-declaration mark

Artifact shares now record type_first_party and caps_read_not_found and are flagged when a first-party type claim cannot be confirmed

Group of 2 Under the hood Internal Changes
JSON All of v2.1.281
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
ElsewhereArea: what it touches
Internal ChangesKind: in v2.1.281,
Internal ChangesSection of the release

What

Artifacts are items that can be shared with you. Claude Code attaches risk marks to an artifact share, which are warnings about what it could not verify. It now checks more carefully whether a shared artifact really comes from a first-party type.

  • The share details gain two optional yes/no fields. type_first_party is set when the type is "first_party_type". caps_read_not_found is set when the capabilities lookup came back not found. Both are read when deciding how to treat a share.
  • The attested mark is now also added when a share claims type_first_party but the local record does not show a first_party_type.
  • A new type-declaration mark is added when a share that is type-locked, first-party and has an observed grant disagrees with, or cannot be checked against, the locally known capabilities or type lock.

Why

A share that claims to come from a first-party type, when Claude Code cannot confirm that on your machine, now gets flagged instead of being taken at its word.

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 doubtThe finding does not say how the handling of a share differs when these fields are set.

See this entry in the whole of v2.1.281 →

Feedback