Follow Discord
Sweep 01 Oct 2026 · 17:27Z Build v2.1.287 508 read Stable v2.1.285 Latest v2.1.287 Next v2.1.287 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.286 ·

New artifact sharing flow, plus proxy refusal and cache keepalive names

Code for sharing artifacts with other people appears, with outcomes such as consent and person checks, plus proxy refusal and cache keepalive names

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

What

An artifact is a piece of content Claude Code produces, such as a document. New code covers sharing artifacts with other people.

  • artifact_share is a new flow for reading and writing shared artifacts and working out which people they are shared with.
  • It has many possible outcomes, including read_ok_foreign, write_relay_unapproved, consent_gone, not_person and people_unresolved.
  • ccr_worker_proxy_refusal and api_cache_keepalive were added alongside it, pointing to handling for refused proxy requests from remote workers and to keeping a cache alive.
  • The memory rating writeback step no longer returns the values it cited.

Why

This points to a new way to share artifacts with other people, with checks on consent, approval and whether a real person is involved. Nothing here shows that the feature is available to you yet.

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 doubtIt is not known what the list is used for, so whether these features are live is unclear.

See this entry in the whole of v2.1.286 →

Feedback