Use enableArtifact instead of disableArtifact, which now only counts when set to true.
What's wrong with this entry?
The old setting is now marked deprecated and only still does anything when set to true. The replacement key documents which settings tier wins: an off in managed settings, --settings or your user settings is final, while project and local settings can only turn the feature off, never back on.
- Unset means on, once the feature is otherwise available.
disableArtifact: falseno longer has an effect; useenableArtifact: falseto turn it off.
Deprecated: use enableArtifact: false. Still honored
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.221
Inline /mcp enable/disable detects changes made in another session
Both mention enable disable
-
v2.1.246
Plugin enable/disable no longer lose telemetry, and can target built-in plugins
Both mention enable disable
-
v2.1.247
claude plugin enable/disablerefuses an ambiguous bare nameBoth mention enable disable