{"version":"2.1.295","anchor":"five-class-asks-capability-is-now-hardcoded-on","canonical_anchor":"five-class-asks-capability-is-now-hardcoded-on","heading":"Artifact five_class_asks capability is now always advertised","tier":"internal","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/five-class-asks-capability-is-now-hardcoded-on","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Artifact five_class_asks capability is now always advertised\n\nThe artifact `five_class_asks` capability is now a fixed value instead of depending on an environment variable or a remote flag\n\n**Unclear.** What this capability does for someone using Claude Code is not stated.\n\n**What**\n\nArtifacts are files and outputs Claude Code produces and can share. When working with artifacts, Claude Code sends a list of the capabilities it supports. In that list, the `five_class_asks` field used to be worked out at runtime. It is now the constant `!0`, which means it is always on.\n\n- Before, the value came from the environment variable `CLAUDE_CODE_ARTIFACT_FIVE_CLASS_ASKS`. An environment variable is a setting passed to a program from outside it. When that variable was not set, the value came from the remote flag `tengu_cobalt_plinth_bryony`, which defaulted to false.\n\n- The neighbouring capabilities `types_on`, `watch_rail` and `auto_react` are still worked out at runtime.\n\n- Nobody checked whether the old helper is now unused or whether `CLAUDE_CODE_ARTIFACT_FIVE_CLASS_ASKS` is still read anywhere.\n\n**Why**\n\nThe capability no longer depends on a setting, so it is advertised for everyone. Setting `CLAUDE_CODE_ARTIFACT_FIVE_CLASS_ASKS` may no longer control it.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}