{"version":"2.1.275","anchor":"artifact-read-permission-checks-hardened-against-a-check-tim","canonical_anchor":"artifact-read-permission-checks-hardened-against-a-check-tim","heading":"Artifact read permission checks hardened against a check-time race, and support multi-file save messaging","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/artifact-read-permission-checks-hardened-against-a-check-tim","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### Artifact read permission checks hardened against a check-time race, and support multi-file save messaging\n\nArtifact file reads now detect a permission check that changed mid-flight, and report multi-file saves\n\n**What**\n\nWhen Claude Code checks permission for reading a file from an artifact (via `read_file`\/`read_asset`), it now detects if a file-edit safety check or an \"ask\" permission rule for one of the destination files changed while the permission check was in progress. If that happens, the read is denied with a message explaining that nothing was read and to retry, rather than proceeding based on stale information.\n\n- The permission-request wording also now distinguishes saving multiple files at once (\"save N files ... to ...\") from the existing single-file wording.\n\n**Why**\n\nThis closes a race condition where a permission decision could be based on outdated information about a file's safety status, and makes the messaging clearer when several files are being saved from an artifact in one request.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}