{"version":"2.1.265","anchor":"new-artifact-ask-class-consentremember-system","canonical_anchor":"new-artifact-ask-class-consentremember-system","heading":"New artifact 'ask class' consent\/remember system","tier":"soon","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/new-artifact-ask-class-consentremember-system","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### New artifact 'ask class' consent\/remember system\n\nA new unified consent system governs sensitive artifact actions like delete and access changes\n\n**Unclear.** Whether unattended foreign reads are actually allowed to proceed depends on the `tengu_artifact_foreign_read_unasked` gate, which has not been read for this release.\n\n**What**\n\nA new consent system now governs a set of sensitive artifact operations: deleting an artifact, changing whether it's public, changing who can access it, standing (recurring) jobs, and reading an artifact someone else owns. Approving one of these actions can now cover its related files for the rest of the conversation, so the same consent isn't asked for repeatedly. A new telemetry event also records when a foreign (someone else's) artifact is read without being asked about first.\n\n**Why**\n\nThis reduces repeated approval prompts for related artifact actions within a single conversation, while still tracking cases where a foreign read happens without an explicit ask.\n\n- Area: Artifacts\n- Tier: Nothing to try yet\n- Useful: 4\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}