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

Clear error when the Windows sandbox runs from a mapped network drive

You'll notice
Useful3 Signal0
Windows

On Windows, launching from a mapped network drive now tells you that's the problem and names the drive.

What

A sandbox failure caused by launching from a mapped network drive now explains itself and names the drive, instead of surfacing as a generic sandbox failure.

Details
  • triggered by sandbox exit code 16 together with a structured mapped_drive_cwd error from the sandbox runtime
  • fires a sandbox_exec telemetry event at the point windows_mapped_drive_cwd
  • Windows sandbox execution path only
Evidence

mapped drives don't exist for the sandbox account. Use a workspace on a local drive.

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 →