{"version":"2.1.273","anchor":"artifacts-list-default-scope-wording-tightened-for-type-scop","canonical_anchor":"artifacts-list-default-scope-wording-tightened-for-type-scop","heading":"Artifacts list default scope wording tightened for type-scoped listings","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/artifacts-list-default-scope-wording-tightened-for-type-scop","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### Artifacts list default scope wording tightened for type-scoped listings\n\nArtifacts list tool now describes the default listing scope as owned, org-owned, and shared-with-you separately\n\n**What**\n\nThe `list` tool's description of its default scope, when filtering artifacts by `type` or `type_url`, now spells out three categories instead of two: artifacts the user owns, artifacts their organization owns, and artifacts shared with them. Previously the wording lumped the latter two together as everything \"shared across their organization.\"\n\n**Why**\n\nThe change clarifies, in the tool's own documentation, that organization-owned artifacts and artifacts merely shared with the user are distinct categories, which affects how Claude reasons about what a default listing will include.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}