{"version":"2.1.281","anchor":"artifact-permission-remembered-artifact-grant-no-longer-cov","canonical_anchor":"artifact-permission-remembered-artifact-grant-no-longer-cov","heading":"Artifact permission: remembered artifact grant no longer covers the call when heldYesDoesNotCover is set","tier":"notice","area":"Artifacts","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/artifact-permission-remembered-artifact-grant-no-longer-cov","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Artifact permission: remembered artifact grant no longer covers the call when heldYesDoesNotCover is set\n\nAn artifact permission you already approved no longer skips the prompt when the request is marked as not covered by that approval\n\n**Unclear.** The finding does not say which kinds of request get the `heldYesDoesNotCover` mark.\n\n**What**\n\nWhen Claude wants to do something with an artifact, Claude Code can ask you for permission, and a yes can be remembered for that artifact. Now, if a request is marked `heldYesDoesNotCover`, the question is shown to you again even though a yes was remembered for that artifact.\n\n**Why**\n\nA past approval no longer silently covers requests that have been marked as outside it, so you get asked about those.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}