{"version":"2.1.292","anchor":"artifact-version-reads-and-listings-fail-closed-on-permissio","canonical_anchor":"artifact-version-reads-and-listings-fail-closed-on-permissio","heading":"Reading an artifact's earlier versions is refused with its own message when permission is unclear","tier":"internal","area":"Artifacts","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/artifact-version-reads-and-listings-fail-closed-on-permissio","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### Reading an artifact's earlier versions is refused with its own message when permission is unclear\n\nReading or listing an artifact's earlier versions is denied with a dedicated message when its permission check cannot complete\n\n**What**\n\nWhen Claude tries to read or list an artifact's earlier versions and the permission check for that action cannot complete, Claude Code refuses the action. This is called failing closed: when in doubt, the answer is no. These actions now get their own reason for the refusal.\n\nBefore, they were refused with the general message used for all artifact asset actions.\n\n**Why**\n\nIf access to an artifact's version history is refused, the message now says that it was the version read or listing that was blocked, rather than a general artifact refusal.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}