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.234 Home All releases ←olderv2.1.233 v2.1.235newer→
Claude Code v2.1.234

Inline policy helpers run with a scrubbed environment and a fixed PowerShell path

Under the hood
Useful2 Signal2
Elsewhere

Inline admin policy scripts run with a stripped environment and a PowerShell resolved from fixed paths only.

What

When an admin policy helper is delivered as an inline script, the child process environment is stripped before it runs. On Windows the PowerShell binary is resolved only from a fixed list of absolute install locations on C:, never from PATH.

Details
  • The sh path runs with a fixed PATH and LC_ALL=C after deleting ENV, BASH_ENV, LD_, DYLD_ and similar variables.
  • The pwsh path rebuilds PSModulePath, PATH, PATHEXT and COMSPEC, and drops DOTNET_, COMPLUS_ and COR_ variables.
  • If no stock PowerShell install is found, the helper fails rather than falling back to a PATH lookup.
Evidence

PowerShell not found at any of its stock install locations on C: (fixed absolute candidates only; PATH is never consulted)

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