{"version":"2.1.318","anchor":"artifact-file-readsasset-saves-now-tracked-with-framing-beg","canonical_anchor":"artifact-file-readsasset-saves-now-tracked-with-framing-beg","heading":"Saving artifact files now cleans up after a failed write","tier":"internal","area":"Artifacts","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/artifact-file-readsasset-saves-now-tracked-with-framing-beg","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Saving artifact files now cleans up after a failed write\n\nFetched artifact files and saved assets are now tracked before and after writing to disk, with cleanup if the write fails\n\n**Unclear.** What the steps run before and after each write record, or whether they change anything a reader can see, is not known.\n\n**What**\n\nWhen Claude Code writes a fetched artifact file or a saved asset to disk, it now runs an extra step before and after the write, and cleans up if the write fails. Before, it wrote the file directly with no extra steps. No messages you see have changed.\n\n**Why**\n\nA save that fails partway through is now cleaned up rather than left as it was.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}