Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.281entry #34

Claude Code v2.1.281 ·

Groundwork for connectors on shared artifacts

Artifact share status gains three connector fields that nothing fills yet, cleared on account change, plus new connector-consent tracking

Group of 3 Nothing to try yet In Development
JSON All of v2.1.281
Nothing to try yetTier: how much it should matter to you
2Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
In DevelopmentKind: in v2.1.281,
What probably matters to youSection of the release

Unclear The finding does not say what these connector fields will be used for.

What

  • 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.
  • When the account changes, these three fields are removed from each artifact's stored share status (bySlug). Before, they were kept.
  • The check of saved state now also looks at these three fields.
  • The state that tracks consent questions gains inheritedTypeGrantLatch, askClassRequestShown and askConnectorsShown.

Why

This 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.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtThe finding does not say what these connector fields will be used for.

See this entry in the whole of v2.1.281 →

Feedback