{"version":"2.1.268","anchor":"new-deny-path-for-asset-saves-outside-working-folders-in-no","canonical_anchor":"new-deny-path-for-asset-saves-outside-working-folders-in-no","heading":"New deny path for asset saves outside working folders in no-consent-surface sessions","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/new-deny-path-for-asset-saves-outside-working-folders-in-no","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### New deny path for asset saves outside working folders in no-consent-surface sessions\n\nArtifact asset saves outside the working folder are now auto-denied when no one can approve the prompt\n\n**What**\n\nArtifacts can save files (`read_asset` requests) outside the session's normal working folders, but only with the user's approval. In sessions where there's no way to show that approval prompt at all \u2014 such as Cowork or local-agent sessions running without a live user to ask \u2014 this request is now automatically denied instead of falling through to whatever the previous logic happened to produce.\n\n**Why**\n\nThis closes a gap where a permission request that can never be answered could previously behave unpredictably; now it's refused outright, keeping asset saves confined to the working folders when there's no one present to grant an exception.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}