{"version":"2.1.259","anchor":"artifact-publish-gains-a-pin-action-to-pin-to-the-claudea","canonical_anchor":"artifact-publish-gains-a-pin-action-to-pin-to-the-claudea","heading":"Artifact publish gains a pin option","tier":"use","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.259\/e\/artifact-publish-gains-a-pin-action-to-pin-to-the-claudea","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.259","markdown":"### Artifact publish gains a `pin` option\n\nPublishing an artifact can now also pin it to your claude.ai sidebar, and the reply says whether the pin worked.\n\nThe artifacts\/files tool's publish action now accepts a `pin` boolean parameter; when true, publishing also pins the artifact to the user's claude.ai sidebar, where it shows up the next time the sidebar loads. On success the tool reply includes a note that it was pinned to the sidebar; if pinning fails, the publish itself still succeeds and the reply appends a note that the pin didn't go through. This is wired into the publish tool's response builder at two call sites, gated by the tool's Zod schema still exposing a `pin` literal in its `action` shape.\n\nWhether the field is even offered to the model is controlled by a check (`$Ot()`) that returns false outright for remote\/cloud sessions (unless `Jd()`), otherwise reads the `CLAUDE_CODE_ARTIFACT_PIN` env var or falls back to a gate.\n\n- Area: Artifacts\n- Names: `pin`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 4\/5"}