{"version":"2.1.246","anchor":"artifact-assets-are-referenced-by-their-url-exactly-as-retur","canonical_anchor":"artifact-assets-are-referenced-by-their-url-exactly-as-retur","heading":"Artifact assets are referenced by their url exactly as returned","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/artifact-assets-are-referenced-by-their-url-exactly-as-retur","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Artifact assets are referenced by their url exactly as returned\n\nArtifact assets must now be referenced by the exact url returned, not a relative path.\n\n**What**\n\nUploading or listing an asset now tells the model to reference it from the page by its url verbatim, rather than as a relative url. The phrase \"relative url\" is gone from the build, so the url handed back is what must be pasted in.\n\n**Details**\n\n- The same text explains that an asset is read or deleted by the id following `_blob\/` in its url.\n- Applies to every artifact asset upload and listing; no setting involved.\n\n**Evidence**\n\n`reference one from the page by its url verbatim, read or delete it by the id after \"_blob\/\":`\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 1\/5"}