{"version":"2.1.319","anchor":"new-managed-setting-disablewindowsbashcommandsplit-is-carrie","canonical_anchor":"new-managed-setting-disablewindowsbashcommandsplit-is-carrie","heading":"Long Bash commands on Windows can be split into pieces, with a managed opt-out","tier":"use","area":"Managed Settings","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/new-managed-setting-disablewindowsbashcommandsplit-is-carrie","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Long Bash commands on Windows can be split into pieces, with a managed opt-out\n\nBehind tengu_mossy_melody, Windows splits Bash commands too long for one argument into pieces, and disableWindowsBashCommandSplit lets admins turn it off\n\n**Unclear.** What turning on `disableWindowsBashCommandSplit` changes in how commands are handled is not known.\n\n**What**\n\nOn Windows, a shell command can be too long to pass to the shell as a single argument, which used to make it fail. Claude Code has a new Windows-only way to handle this:\n\n- The command is split into several arguments and put back together, with a sha256 check (a fingerprint) to confirm the whole text arrived.\n\n- If it still cannot fit or cannot be confirmed, Claude is told to break it up, for example: \"Claude Code did not run this command: it is too long for one argument of the shell on Windows, and the shell could not confirm that it had the whole text, which was sent in several arguments. Break it into shorter commands.\"\n\n- The path is controlled by the server switch `tengu_mossy_melody`, whose built-in default is off. Nothing has been read about it.\n\n- A new managed setting, `disableWindowsBashCommandSplit`, turns the splitting off. It counts only when an organization's policy sets it to true, and it is merged the same way as `disableSkillShellExecution` and `allowManagedHooksOnly`.\n\n**Why**\n\nWhere the switch is on, long commands on Windows may run instead of failing. Administrators who do not want commands split this way can block it through policy.\n\n- Area: Managed Settings\n- Names: `disableWindowsBashCommandSplit`, `disableSkillShellExecution`, `allowManagedHooksOnly`\n- Tier: Use it now\n- Useful: 5\/5\n- Signal: 3\/5\n- Scope: both\n- Heads-up: no"}