{"version":"2.1.318","anchor":"artifact-files-now-get-a-framingpermission-mode-and-are-mar","canonical_anchor":"artifact-files-now-get-a-framingpermission-mode-and-are-mar","heading":"Artifact files are now tagged with a mode when read and written","tier":"internal","area":"Artifacts","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/artifact-files-now-get-a-framingpermission-mode-and-are-mar","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Artifact files are now tagged with a mode when read and written\n\nClaude Code now works out a framing mode for artifact files and applies it when it writes them, cleaning up if a write fails\n\n**Unclear.** It is not clear what the framing value does for the person opening the artifact.\n\n**What**\n\nWhen Claude Code reads an artifact, it now works out a framing value. That value depends on your role, whether the artifact was written together with others, whether its type is locked, and whether it comes from outside your organization. Claude Code records the value after reading.\n\nWhen Claude Code saves an artifact's files ahead of time so they open quickly, it now applies a mode to them before and after writing. If the write fails, it cleans up. Before, these files were written with no such mode.\n\n**Why**\n\nThis changes how artifact files are labelled and protected on your disk.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}