Nothing to try yet
Artifact permission prompts now sort into five distinct classes instead of one generic ask
What
Artifacts (Claude Code's generated files/apps) that need to ask permission before taking some action are now classified into one of five named categories: delete, access_change, standing_job, public_change, or foreign_read. Each class carries its own metadata about whether and how the answer can be remembered. A new consent cache keyed by account and conversation also remembers past answers within that scope.
Why
Sorting asks into specific classes instead of one generic permission check lets Claude Code apply different remembering rules to different kinds of risk, for example treating a delete differently from a one-time read.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
Whether the `tengu_artifact_five_class_asks` gate is enabled for this site's account is unread, so no reading can be reported.