suppressAlwaysAllowRule
A Claude Code settings key, read out of the shipped bundle. No mined inventory carries it: everything below comes from what this site has written about it.
Replying to an artifact comment always asks first, and tells you whether the artifact is shared.
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.221.
In the changelogs
7Releases whose published page names suppressAlwaysAllowRule.
-
v2.1.281
Auto mode now handles dangerous-removal safety checks directly: deny or timed dialog
In auto mode, dangerous-removal safety checks can now be denied outright or shown as a dialog that denies itself after a timeout
found in this entry's text
-
v2.1.268
New permission-request fields: defaultToNo and suppressAlwaysAllowRule
Permission requests now carry defaultToNo and suppressAlwaysAllowRule fields from the server
found in this entry's text, named in this entry
-
v2.1.260
Host profile collection has its own telemetry
Forced-ask permission decisions now include a suggested standing allow rule where applicable.
found in this entry's text
-
v2.1.246
MCP tool prompts can hide the "don't ask again" option
MCP permission prompts can be returned without the "don't ask again" option.
found in this entry's text
-
v2.1.234
Every artifact asset action now asks permission, with its own consent scope
Uploading, listing, reading and deleting artifact files each ask permission separately, with deletes asking every time.
found in this entry's text
-
v2.1.221
Comment replies always ask, and the prompt names who will see them
Replying to an artifact comment always asks first, and tells you whether the artifact is shared.
found in this entry's text
-
v2.1.203
Artifact Listing: First-Session Confirmation Required
found in this entry's text
First cited
3The earliest release whose published evidence quoted suppressAlwaysAllowRule was v2.1.246, 25 Aug 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.
Presence across releases
0The 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 settings key does. All settings keys.