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.246 Home All releases ←olderv2.1.245 v2.1.247newer→
Claude Code v2.1.246

Artifact comments refuse organization service keys

Not switched on
Useful2 Signal3
Artifacts Notable not in their notes

Artifact comments now explain org service key failures clearly, but comments themselves need an env var.

Clearer service-key errors ship inside artifact comments, which require CLAUDE_CODE_ARTIFACT_COMMENTS or a gate that falls back to off.

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

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

CLAUDE_CODE_ARTIFACT_COMMENTS
What

Resolving a comment thread, or replying and resolving, now stops with an explanation to pass on to you when the session is authenticated with an organization service key that has no Claude agent grant, rather than failing obscurely. Artifact comments as a whole require the environment variable CLAUDE_CODE_ARTIFACT_COMMENTS or the tengu_teal_corbel gate, which falls back to off, so this is unreachable in a default build.

Details
  • The refusal is recorded as a service_key_credential reason in the artifact_comment_session_resolve log.
  • The same gate covers new fields sent with comments recording auto-reply, edit permission, whose turn it is, whether the thread was named by the user, and declined replies.
Evidence

this session's credential is an organization service key with no Claude agent grant, so it cannot post or resolve comments

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