disableWindowsBashCommandSplit
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.
A managed setting, disableWindowsBashCommandSplit, now carries through when an organisation policy sets it to true
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.319.
In the changelogs
2Releases whose published page names disableWindowsBashCommandSplit.
-
v2.1.319
Admins can set disableWindowsBashCommandSplit in managed settings
A managed setting, disableWindowsBashCommandSplit, now carries through when an organisation policy sets it to true
named in this entry, found in this entry's text
-
v2.1.319
Very long Bash commands on Windows can be split and sent in pieces
On Windows, a Bash command too long for one shell argument can now be split into pieces and checked on arrival instead of failing
found in this entry's text
First cited
1The earliest release whose published evidence quoted disableWindowsBashCommandSplit was v2.1.319, 6 Nov 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.