Claude Code v2.1.221 ·
Reply failure when the thread isn't activated
A reply to an unactivated artifact thread would show as its own state, once comments are live.
Nothing to try yetTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
In DevelopmentKind: in v2.1.221,
In DevelopmentSection of the release
A distinct not-activated reply state exists on artifact comments, whose enablement is unresolved.
What
A reply to a thread the viewer has not activated is surfaced in the transcript as its own state rather than a generic error.
Details
- the "artifact_comment_reply" telemetry outcome is recorded as not_activated
- rides on the same artifact comment/reply actions whose enablement is unresolved in this build
Evidence
reply needs thread activation by the user
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.221 →
