{"version":"2.1.274","anchor":"new-guard-on-artifact-file-reads-triggered-by-unattended-aut","canonical_anchor":"new-guard-on-artifact-file-reads-triggered-by-unattended-aut","heading":"New guard on artifact file reads triggered by unattended auto-reply notifications","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/new-guard-on-artifact-file-reads-triggered-by-unattended-aut","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### New guard on artifact file reads triggered by unattended auto-reply notifications\n\nArtifact file reads triggered by unattended auto-reply notifications are now blocked outside background\/subagent contexts\n\n**What**\n\nThe permission check for reading artifact files now explicitly refuses to allow the read when it was queued as a result of an unattended auto-reply notification, unless the current context is a background or subagent context.\n\n**Why**\n\nThis closes off a path where an automatic, unattended notification reply could trigger a file read outside of a controlled background process, keeping such reads confined to contexts where they're expected.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 1\/5"}