Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.221 Home All releases ←olderv2.1.220 v2.1.222newer→
Claude Code v2.1.221

Windows sandbox errors carry a code and the failing subcommand

You'll notice
Useful2 Signal0
Windows

Windows sandbox failures now carry a specific error code, though one remediation hint was dropped.

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.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.221 →