Group of 3 You'll notice
Posting a reply comment on an Artifact now retries once on failure using a client-generated id, and reports if a retry was actually a replay
What
When Claude Code posts a reply to a comment on an Artifact, the request handling is now more resilient:
- The reply tool now generates a client id for each reply and sends it with the request.
- On a server error (5xx) or a 499 status, the request waits a short randomized delay (roughly 800-1500ms) and retries once using that same client id.
- If the retried request comes back with a 409 "id_in_use" conflict, it's now treated as a successful resend rather than a failure, and the tool result can include
replayed: trueto show this happened. - The underlying request function also now distinguishes relay errors from generic network errors so callers can opt into this retry behavior.
Why
This prevents duplicate or lost comment replies when a network hiccup or transient server error occurs, since the retry reuses the same id instead of risking a duplicate post.