{"version":"2.1.288","anchor":"artifact-db-writes-with-embedded-base64-files-get-specific-g","canonical_anchor":"artifact-db-writes-with-embedded-base64-files-get-specific-g","heading":"Claude is told to upload files instead of storing them in artifact documents","tier":"notice","area":"Artifacts","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/artifact-db-writes-with-embedded-base64-files-get-specific-g","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Claude is told to upload files instead of storing them in artifact documents\n\nWhen a too-large artifact document contains encoded file data, Claude is now told to upload the file instead\n\n**What**\n\nWhen Claude saves a document to an artifact's storage and the write is too big or over its limit, Claude Code checks for what looks like base64 data. Base64 is a way of writing a file out as text. If it finds some, the error now tells Claude that documents hold data, not files, and to upload the file with `upload_asset`. The message also gives the maximum document size in KiB. Before, the error only gave the size and said to write less per document.\n\n**Why**\n\nClaude is pointed to the right way to store files, so it does not keep retrying writes that will fail.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}