{"version":"2.1.275","anchor":"new-docs-unfillable-flag-surfaces-in-list-types-output","canonical_anchor":"artifact-type-listing-flags-unfillable-docs-connector-types","heading":"list_types flags Docs artifact types that can't be filled","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/new-docs-unfillable-flag-surfaces-in-list-types-output","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### list_types flags Docs artifact types that can't be filled\n\nArtifact type listings now note when a Docs-connector type can't be filled because Claude Docs isn't connected\n\n**What**\n\nThe artifact `list_types` output now includes a `docs_unfillable` field, set when the results include a Claude Docs-backed artifact type but the Claude Docs connector isn't attached to the current session. When this happens, the response appends an explanatory line to the type-list summary telling the user why that type can't be used.\n\n**Why**\n\nThis avoids confusion where a Docs-based artifact type shows up as available but silently fails, by explaining upfront that the Docs connector needs to be attached first.\n\n- Area: Artifacts\n- Names: `docs_unfillable`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}