Source Intelligence

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

All of v2.1.236 Home All releases olderv2.1.235 v2.1.237newer
Claude Code v2.1.236

Pinning artifacts in the picker, switched on by the server

Use it now
Useful4 Signal3
Artifacts Notable

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

p
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.

See this entry in the whole of v2.1.236 →