Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
Internal ChangesKind: in v2.1.271,
Internal ChangesSection of the release
What
When Claude's automatic reaction to an Artifact comment falls back after a failed "rehand" attempt (handing the comment back to Claude to answer), it now checks whether the failure reason was hitting a cap (a limit), and logs a separate telemetry event, fork_rehand_fallback_cap, distinct from the generic fork_rehand_fallback event used for other fallback causes.
Why
This lets the team distinguish fallbacks caused by hitting a limit from other kinds of fallback failures, which doesn't change what users see but improves diagnosis of this feature.
