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.248 Home All releases ←olderv2.1.247 v2.1.250newer→
Claude Code v2.1.248

Permission prompts say whose comment is being acted on

Not switched on
Useful2 Signal4
Artifacts not in their notes

Comment permission prompts can name whose comment it is, behind an artifact-comments env var.

Author-naming in comment prompts sits behind CLAUDE_CODE_ARTIFACT_COMMENTS and a server gate.

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.248: on

Read once, for one account on one subscription tier, against v2.1.248. It isn't a statement about your account. What a flag value here can and cannot tell you

CLAUDE_CODE_ARTIFACT_COMMENTS
What

Permission prompts for comment actions now name the comment's author in plain words, either inline as your comment "…", Claude's comment "…", a viewer's comment "…" or the comment "…", or as a thread, for example Claude's comment thread. This only runs on the artifact comments path, behind the tengu_teal_corbel gate and the CLAUDE_CODE_ARTIFACT_COMMENTS environment variable.

Details
  • The quoted excerpt is normalised before display: newlines and tabs collapse to spaces, double quotes become single quotes, and the text is truncated with an ellipsis at 120 characters.
  • A target is only built when the call has a tool-use id, the permission mode is not dontAsk, and prompt suppression is not set, so nothing is computed when no prompt would be shown.
  • The formatters are defined in this build; the exact line as rendered in the prompt is inferred from those definitions rather than read at the render site.
Evidence

Claude's comment thread

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.248 →