{"version":"2.1.239","anchor":"artifact-embeds-parser-and-renderer-ship-schema-field-does-n","canonical_anchor":"artifact-embeds-parser-and-renderer-ship-schema-field-does-n","heading":"Artifact embeds: parser and renderer ship, schema field does not","tier":"soon","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/artifact-embeds-parser-and-renderer-ship-schema-field-does-n","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Artifact embeds: parser and renderer ship, schema field does not\n\nArtifact responses can carry pinned embed items that parse and render, but the schema key never ships.\n\n**What**\n\nArtifact responses can now carry embeds, a list of pinned items (uuid, path, module, files) plus warnings, which is parsed from server responses and rendered into a readable block that cuts off with \"(embeds truncated)\". The parser and renderer are ungated, but the artifact tool's result schema declares the `embeds` key only inside a spread guarded by a module-level constant set to false, and that constant is used nowhere else.\n\n**Details**\n\n- Whether an undeclared key survives result validation is not settled in this build, so it is unclear whether any embed text reaches the model.\n- No artifact embeds code exists in 2.1.238.\n\n**Evidence**\n\n`(embeds truncated)`\n\n- Area: Artifacts\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}