Specific error messages for artifact comment failures exist behind the same comments gate, unreachable by default.
What
The artifact comments paths classify several failures specifically instead of reporting a generic HTTP error.
Details
- Reading comments through a network egress proxy that blocks the artifact content host returns a dedicated message stating this is not a transient failure, detected from HTTP 403 plus the
x-proxy-errorheader valueblocked-by-allowlist. - Replying to a thread the user has not activated for Claude is detected from the body text and reported as a distinct
not_activatedoutcome rather than a generic 403. - Resolve failures map 409/403 bodies to
superseded,grant_inactive, andprincipal_mismatch. - Behind the same artifact-comments gate, so unreachable in this build absent a server value.
Evidence
the network egress proxy in this environment blocks the artifact content host — comments cannot be read here (not a transient failure)
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Names in the bundleCLAUDE_CODE_ARTIFACT_COMMENTS
One source agreesOne thing we can check says the same as this entry.
The name it cites is new in this build
New in this build: CLAUDE_CODE_ARTIFACT_COMMENTS