Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.265 ·

Artifact permission-ask classifier reworked into five named classes with a rollout gate

Artifact permission prompts now sort into five distinct classes instead of one generic ask

Nothing to try yet In Development
JSON All of v2.1.265
Nothing to try yetTier: how much it should matter to you
4Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
In DevelopmentKind: in v2.1.265,
What probably matters to youSection of the release

Unclear Whether the tengu_artifact_five_class_asks gate is enabled for this site's account is unread, so no reading can be reported.

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.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhether the `tengu_artifact_five_class_asks` gate is enabled for this site's account is unread, so no reading can be reported.

See this entry in the whole of v2.1.265 →

Feedback