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.239 Home All releases ←olderv2.1.238 v2.1.240newer→
Claude Code v2.1.239

PowerShell path checks distinguish a timeout from an error

You'll notice
Useful2 Signal1
Windows

On Windows, a PowerShell path check that times out now says so with the timeout value.

What

On Windows, when Claude Code checks the PowerShell interpreter path for policy purposes, a check that times out now reports "cannot stat path (timed out after ..." with the timeout value, rather than looking like an ordinary failure.

Details
  • The result of checking each path is cached in a shared map, so repeated checks of the same path do not re-run the stat.
  • Windows-only code path.
Evidence

cannot stat path (timed out after

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.239 →