Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.236 ·

Pinning artifacts in the picker, switched on by the server

The artifact picker gets a pinned tab and a p key to pin, if your server enables it.

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

The artifact list gained a fourth filter tab for pinned artifacts, a p key whose label flips between pin and unpin, and sorting that puts pinned artifacts first. The switch is not a local flag: the list response carries a starsEnabled boolean, and when the server omits it the tab is dropped, the pin action disappears, and a selected pinned filter is rewritten back to "all".

Details
  • Per-artifact list data gained a pinned marker, an audience (owner, users, org, or public) and a last-viewed timestamp; ordering is pinned first, then most recently viewed, updated, or created.
  • Pin state updates locally straight away and is reconciled against the server.
  • The pinned tab is only offered once you actually have something pinned, or are already on it, and the empty state reads "Nothing pinned yet. Press p on an artifact to pin it."
  • There is no environment variable or local flag to force it on; it stays invisible until the artifacts backend returns the field.
Evidence

Nothing pinned yet. Press p on an artifact to pin it., starsEnabled

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Read from
Names in the bundlep

See this entry in the whole of v2.1.236 →

Feedback