Follow Discord
Sweep 25 Sep 2026 · 19:33Z Build v2.1.283 504 read Stable v2.1.274 Latest v2.1.283 Next v2.1.283 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.283entry #26

Claude Code v2.1.283 ·

Artifacts can ask each viewer to approve connectors they did not list

An artifact's connector declaration can now be marked dynamic, so viewers approve unlisted connectors at first use instead of those calls failing

You'll notice New Features
JSON All of v2.1.283
You'll noticeTier: how much it should matter to you
4Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
New FeaturesKind: in v2.1.283,
What probably matters to youSection of the release
What

An artifact is a page Claude publishes. Its manifest can list MCP servers, also called connectors, which let the page reach outside tools and data. That list can now be marked dynamic.

With a dynamic declaration:

  • Publish checks no longer say that calls to connectors missing from the manifest fail for every viewer. They say each viewer is asked to approve the connector the first time it is used.
  • A name the viewer has no connector for is refused.
  • The publish result tells Claude to tell you which connectors the page calls and that those integrations are unverified.
  • The capability summary shows "any connector the viewer approves".
Why

Pages can now use connectors that were not declared ahead of time, with each viewer approving them. Because these integrations are unverified, Claude is told to point them out to you.

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 doubtIt is not clear whether the Artifacts feature itself is available to every account.

See this entry in the whole of v2.1.283 →

Feedback