{"version":"2.1.267","anchor":"artifacts-gain-an-asset-store-uploadlistreaddelete","canonical_anchor":"artifacts-gain-an-asset-store-uploadlistreaddelete","heading":"Artifacts gain an asset store (upload\/list\/read\/delete)","tier":"soon","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/artifacts-gain-an-asset-store-uploadlistreaddelete","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### Artifacts gain an asset store (upload\/list\/read\/delete)\n\nArtifacts with an assets capability now support uploading, listing, reading, and deleting stored files\n\n**What**\n\nThe Artifact tool now documents four new actions for artifacts whose page declares an `assets` capability:\n\n- `upload_asset` \u2014 push a local file into the artifact's asset store\n\n- `list_assets` \u2014 enumerate what's stored\n\n- `read_asset` \u2014 pull a stored file back down to disk\n\n- `delete_asset` \u2014 remove a stored file\n\n**Why**\n\nThis gives an artifact its own persistent file storage that Claude can manage directly, useful for artifacts that need to keep data, uploads, or generated files around between sessions rather than only living in the page itself.\n\n- Area: Artifacts\n- Names: `assets`\n- Tier: Nothing to try yet\n- Useful: 5\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}