{"version":"2.1.236","anchor":"pinning-artifacts-in-the-picker-switched-on-by-the-server","canonical_anchor":"pinning-artifacts-in-the-picker-switched-on-by-the-server","heading":"Pinning artifacts in the picker, switched on by the server","tier":"use","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236\/e\/pinning-artifacts-in-the-picker-switched-on-by-the-server","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236","markdown":"### Pinning artifacts in the picker, switched on by the server\n\nThe artifact picker gets a pinned tab and a `p` key to pin, if your server enables it.\n\n**What**\n\nThe 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\".\n\n**Details**\n\n- 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.\n- Pin state updates locally straight away and is reconciled against the server.\n- 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.\"\n- There is no environment variable or local flag to force it on; it stays invisible until the artifacts backend returns the field.\n\n**Evidence**\n\n`Nothing pinned yet. Press p on an artifact to pin it.`, `starsEnabled`\n\n- Area: Artifacts\n- Names: `p`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 3\/5"}