allowedDomains
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.
Set strictAllowlist to have the sandbox flat-out deny hosts outside your allowed domains instead of prompting.
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.219.
In the changelogs
12Releases whose published page names allowedDomains.
-
v2.1.304
Windows sandbox works out its file access from credentials and allowed domains
On Windows, the sandbox now uses its credentials and allowed network domains when working out which files it may reach
found in this entry's text, named in this entry
-
v2.1.285
Sandbox status shown to host apps now describes the rules actually enforced
The sandbox status that Claude Code reports to host apps now describes the enforced rules and gains a field for allowing all Unix sockets
found in this entry's text
-
v2.1.284
Sandbox blocks allowed websites that point to internal or cloud-metadata addresses
The sandbox now checks where an allowed hostname really points and refuses loopback, link-local, cloud-metadata and similar internal addresses
found in this entry's text, named in this entry
-
v2.1.283
One invalid sandbox deny entry now withholds the matching allow rules
If one entry in deniedDomains, denyWrite or denyRead is invalid, Claude Code now withholds the matching allow list instead of applying it
found in this entry's text
-
v2.1.268
Domain-pattern validation rejects overly-broad wildcards for allowedDomains/deniedDomains
Sandbox domain lists now reject overly broad wildcard patterns like *.com
found in this entry's text, named in this entry
-
v2.1.232
An empty allowedDomains list no longer produces an empty egress allowlist
An empty allowedDomains list no longer produces an empty egress allowlist; you get a warning.
found in this entry's text
-
v2.1.224
Sandbox AWS credential pairs get precedence rules and scope warnings
Conflicting AWS credential pairs in the sandbox now resolve predictably and warn about risky setups.
found in this entry's text
-
v2.1.221
sandbox.credentials.files gains a
maskmode with regex extractionYou can mask secrets in credential files so sandboxed commands see placeholders while real values are swapped in on egress.
found in this entry's text
-
v2.1.219
New sandbox setting: network.strictAllowlist
Set strictAllowlist to have the sandbox flat-out deny hosts outside your allowed domains instead of prompting.
named in this entry, found in this entry's text
-
v2.1.186
Network
strictAllowlistSettingfound in this entry's text
-
v2.1.186
deniedDomainsNow Accepts Deny-All Wildcardfound in this entry's text
-
v2.1.113
Network Denied Domains Configuration
found in this entry's text
First cited
7The earliest release whose published evidence quoted allowedDomains was v2.1.113, 17 Apr 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.
1 further span in the ledger name it. The list above is the earliest first and stops at 6.
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.