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

Comment replies always ask, and the prompt names who will see them

Not switched on
Useful3 Signal3
Permissions not in their notes

Replying to an artifact comment always asks first, and tells you whether the artifact is shared.

Comment reply permission prompts sit behind CLAUDE_CODE_ARTIFACT_COMMENTS, off by default.

Feature flag
tengu_teal_corbel On for this account, and not off by default

The flag server returned on for the one account this site reads, and nothing in this release compiles it off by default. The compiled default is shown below, and says which it is when we cannot read one: a fifth of gates compile in a string or a number rather than on or off, and most published releases have no gate table behind them at all. No client can see what the server returns for your account.

This account: on · anonymous baseline: on · compiled default in v2.1.221: on

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

CLAUDE_CODE_ARTIFACT_COMMENTS
What

Replying to an artifact comment can never be auto-allowed, and the confirmation states the artifact's sharing state so the audience is clear before posting.

Details
  • Permission for reply returns behavior "ask" with suppressAlwaysAllowRule, so no always-allow rule can be created.
  • Before prompting, the artifact's share mode is probed; the message says whether the artifact is shared, falling back to share-status-unconfirmed wording when the probe fails.
  • Reading comments is allowed without a prompt, except when the read was triggered by a new-comments notification, which forces a prompt.
  • Behind the artifact-comments gate (CLAUDE_CODE_ARTIFACT_COMMENTS / tengu_teal_corbel).
Evidence

Posting a comment reply visible to other viewers requires confirmation

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 →