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

tengu_artifact_five_class_asks

flag never mined JSON

A Claude Code feature flag, read out of the shipped bundle. No mined inventory carries it: everything below comes from what this site has written about it.

Pinning someone else's artifact can now be auto-allowed instead of prompting, under an experiment

Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.265.

First seen — never in a mined build
Last seen — never in a mined build
Builds0 / 161on this box, as of v2.1.322
Written about v2.1.265 first named in a changelog, 8 Sep 2026

In the changelogs

6

Releases whose published page names tengu_artifact_five_class_asks.

  1. v2.1.267
    Artifact write_db permission prompts now describe file provenance and version-pinned edits to others' artifacts

    Permission prompts for writing to artifacts now explain whose file it is and flag version-pinned edits

    gate cited by this entry

  2. v2.1.265
    Pinning an artifact can auto-allow without asking under the five-class-asks experiment

    Pinning someone else's artifact can now be auto-allowed instead of prompting, under an experiment

    gate cited by this entry

  3. v2.1.265
    Whole new Artifact consent model built behind CLAUDE_CODE_ARTIFACT_FIVE_CLASS_ASKS, off by default

    A rewritten Artifact permission system with five-way ask classification exists behind an off-by-default flag

    gate cited by this entry, found in this entry's text

  4. v2.1.265
    Artifact reads gain a five-class consent latch

    Reading someone else's shared artifact can now be auto-allowed via a remembered consent choice

    gate cited by this entry

  5. 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

    gate cited by this entry

  6. v2.1.265
    New env-gated 'five class asks' artifact permission behavior

    New env variable CLAUDE_CODE_ARTIFACT_FIVE_CLASS_ASKS toggles a permission-asking behavior for artifacts, logged via telemetry

    gate cited by this entry

Gate readings

0

No release here has a gate table behind it for this flag. Most published releases have none at all: the readings exist only for versions the pipeline captured flag state on.

First cited

1

The earliest release whose published evidence quoted tengu_artifact_five_class_asks was v2.1.265, 8 Sep 2026. That is the oldest release this project wrote about it, so it is a floor on the name's age and not the release that introduced it. It is not a presence reading: which builds carried the name is the table below.

ReleaseDateThe span that was quoted
v2.1.2658 Sep 2026tengu_artifact_five_class_asks

Presence across releases

0

The miner has never read a build containing this name. It is here because a changelog entry of ours names it, which is evidence that it existed and not evidence of which releases carried it. The inventory starts at v2.1.138 and everything older than that was never mined.

Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the feature flag does. All feature flags.

Feedback