Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.238 Home All releases ←olderv2.1.237 v2.1.239newer→
Claude Code v2.1.238

Artifact publishing rejects connector names reserved for the viewer's own servers

You'll notice
Useful2 Signal2
Artifacts

Publishing an artifact with a reserved connector name now tells you exactly what to rename.

What

If a published artifact declares a connector whose name is reserved for the viewer's local servers, publishing is now refused with a specific error telling you to rename it in claude.ai Settings, Connectors, rather than the older generic "unresolved" complaint. Publishing also retries when the server reports a rate limit that is not a recognised reset.

Details
  • The error class is reserved_mcp_server_name and the report carries a count of reserved names; it is checked before the existing unresolved and over-cap classes.
  • A recognised reset condition produces a message telling the model the publish did not finish and to republish to the same slug after the reset, instead of sleeping and retrying.
  • Oversize, unobserved and merged-entry messages now say "connector" or "local server" depending on the entry.
  • The capability schema gained an optional per-surface features map.
Evidence

a name reserved for the viewer's local , reserved_mcp_server_name

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.238 →