{"version":"2.1.281","anchor":"three-new-artifact-share-status-fields-are-copied-and-remove","canonical_anchor":"three-new-artifact-share-status-fields-are-copied-and-remove","heading":"Groundwork for connectors on shared artifacts","tier":"soon","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/three-new-artifact-share-status-fields-are-copied-and-remove","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Groundwork for connectors on shared artifacts\n\nArtifact share status gains three connector fields that nothing fills yet, cleared on account change, plus new connector-consent tracking\n\n**Unclear.** The finding does not say what these connector fields will be used for.\n\n**What**\n\n- The share-status record for artifacts (shareable outputs Claude Code creates) gains `endpointConnectors`, `connectorsIssuedAt` and `lastConnectorsReadToolUseId`. The copy step passes them through when present. No code in this build sets them.\n\n- When the account changes, these three fields are removed from each artifact's stored share status (`bySlug`). Before, they were kept.\n\n- The check of saved state now also looks at these three fields.\n\n- The state that tracks consent questions gains `inheritedTypeGrantLatch`, `askClassRequestShown` and `askConnectorsShown`.\n\n**Why**\n\nThis is groundwork for connectors attached to artifacts, with nothing using it yet. One effect is already in place: connector details stored under one account do not carry over when you switch to another.\n\n- Area: Artifacts\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}