{"version":"2.1.239","anchor":"artifact-request-schema-auto-reply-gated-embeds-compiled-out","canonical_anchor":"artifact-request-schema-auto-reply-gated-embeds-compiled-out","heading":"Artifact request schema: auto_reply gated, embeds compiled out","tier":"soon","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/artifact-request-schema-auto-reply-gated-embeds-compiled-out","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Artifact request schema: auto_reply gated, embeds compiled out\n\nArtifact auto-reply appears only with comments enabled, and an embeds field is compiled out entirely.\n\n**What**\n\nThe `auto_reply` field of the artifact request schema now appears only when artifact comments are enabled, via the `CLAUDE_CODE_ARTIFACT_COMMENTS` environment variable or, failing that, the remote flag `tengu_teal_corbel` whose fallback is off. A separate `embeds` field sits behind a build-time constant set to false, so it never appears in the shipped schema.\n\n**Evidence**\n\n`auto_reply`\n\n- Flag `tengu_teal_corbel`: Off by default, switched on for this account (read for one account on one subscription tier against v2.1.239; this account: on, anonymous baseline: on, compiled default: off)\n- Area: Artifacts\n- Names: `CLAUDE_CODE_ARTIFACT_COMMENTS`\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}