Claude Code v2.1.221 ·
Windows sandbox errors carry a code and the failing subcommand
Windows sandbox failures now carry a specific error code, though one remediation hint was dropped.
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
WindowsArea: what it touches
ImprovementsKind: in v2.1.221,
ImprovementsSection of the release
What
Windows sandbox failures now raise a typed error instead of a bare Error, so callers can branch on the cause rather than parse a message.
Details
- The error class is WindowsSandboxError, carrying a machine-readable code plus the
srt-win subcommand that failed. - Codes:
bin_shell_invalid, srt_win_nonzero, srt_win_bad_json, not_provisioned, argv_too_long. - The argv-length message lost its trailing remediation sentence suggesting you shorten the command.
- Windows only.
Evidence
srt_win_bad_json
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
See this entry in the whole of v2.1.221 →
