Clearer service-key errors ship inside artifact comments, which require CLAUDE_CODE_ARTIFACT_COMMENTS or a gate that falls back to off.
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.
- The refusal is recorded as a
service_key_credentialreason in theartifact_comment_session_resolvelog. - 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.
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.
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.246: off
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
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.