{"version":"2.1.309","anchor":"artifact-permission-prompts-now-track-endpoint-connectors","canonical_anchor":"artifact-permission-prompts-now-track-endpoint-connectors","heading":"Artifact permission checks now track connectors","tier":"notice","area":"Artifacts","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/artifact-permission-prompts-now-track-endpoint-connectors","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Artifact permission checks now track connectors\n\nArtifact change detection now tracks which connectors an artifact can reach, and a related connectors_mark setting was added\n\n**Unclear.** It is not known what switches this connector check on, so it may not be active for everyone.\n\n**What**\n\nWhen an artifact changes, Claude Code compares some facts about it with what it saw before, to decide whether to ask your permission again. This release adds connectors to those facts:\n\n- A new `connectors` fact compares the artifact's `endpoint_connectors` with what was seen before. It reports the result as `unknown` or `wider`.\n\n- The check that decides whether a change needs a new prompt now runs separately for each kind of fact, so ownership and connectors are tracked independently.\n\n- A new optional true\/false key, `connectors_mark`, was added to a configuration schema that already has keys such as `watch_rail` and `inherited_type_grant`. Elsewhere it is set to true whenever a certain value is present. What makes that value present was not found.\n\nBefore, the facts were ownership, audience, shared-live, co-written, attested, type declaration and watch.\n\n**Why**\n\nIn practice, a change to which connectors an artifact can reach now feeds into whether you are asked again. You may see a new permission prompt when an artifact gains wider connector access.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}