Full artifact comment threads with reply and resolve actions sit behind CLAUDE_CODE_ARTIFACT_COMMENTS, off by default.
A whole subsystem for reading and replying to comment threads on published Claude artifacts is present in this build but switched off absent a server value.
- It fetches comment threads from the artifact frame host JSON, posts replies via
/api/frame/comments/, and resolves threads via the same path plus/resolve. - The Artifact tool gains
commentsandreplyactions plusthread_idandtextparameters, and a response schema carrying threads, comments, resolved/activated flags and span_quote. Reply text is plain text capped at 4096 bytes of UTF-8. - Schema fields, tool prompt section, permission text and result rendering are all added conditionally: the code checks whether
thread_idis in the built schema to decide whether to append the Comments prompt section, so with the gate off the actions do not exist at all. - Threads are heavily sanitised: control and default-ignorable characters stripped, anchor paths capped at 10
" > "segments and 1024 chars, span quotes byte-capped. Degraded fields are counted into arows_degradedtelemetry payload withdropped_threads,dropped_comments,degraded_fields. - Gate:
te.CLAUDE_CODE_ARTIFACT_COMMENTS ?? Je("tengu_teal_corbel", !1), an env var override over a remote-config gate whose in-source fallback is off.
rate limited — comment replies spend the user's budget; do not retry now, 'reply' posts a reply into one comment thread (pass url, thread_id, text), reply only: the reply text. Plain text, at most 4096 bytes of UTF-8., 'comments' reads the comment threads on a published artifact (pass url). 'reply' posts a reply into one comment thread (pass url, thread_id, text)
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
tengu_teal_corbel Off by default, switched on for this accountThe shipped code defaults this off, and the flag server returned on for the one account this site reads on this version. That is the reading that makes the entry above worth a second look, and it still says nothing about your account.
This account: on · anonymous baseline: on · compiled default in v2.1.221: off
These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.
Read once, for one account on one subscription tier, against v2.1.221. It isn't a statement about your account. What a flag value here can and cannot tell you
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
New in this build: CLAUDE_CODE_ARTIFACT_COMMENTS