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.221 Home All releases ←olderv2.1.220 v2.1.222newer→
Claude Code v2.1.221

Artifact comment errors distinguish egress-proxy blocks and non-activated threads

Not switched on
Useful2 Signal2
Artifacts not in their notes

Artifact comment failures would name the real cause, like a proxy block or an unactivated thread, once enabled.

Specific error messages for artifact comment failures exist behind the same comments gate, unreachable by default.

CLAUDE_CODE_ARTIFACT_COMMENTS
What

The artifact comments paths classify several failures specifically instead of reporting a generic HTTP error.

Details
  • Reading comments through a network egress proxy that blocks the artifact content host returns a dedicated message stating this is not a transient failure, detected from HTTP 403 plus the x-proxy-error header value blocked-by-allowlist.
  • Replying to a thread the user has not activated for Claude is detected from the body text and reported as a distinct not_activated outcome rather than a generic 403.
  • Resolve failures map 409/403 bodies to superseded, grant_inactive, and principal_mismatch.
  • Behind the same artifact-comments gate, so unreachable in this build absent a server value.
Evidence

the network egress proxy in this environment blocks the artifact content host — comments cannot be read here (not a transient failure)

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

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.221 →