Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.234 ·

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

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

Under the hood New Features
JSON All of v2.1.234
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
ElsewhereArea: what it touches
New FeaturesKind: in v2.1.234,
New FeaturesSection of the release
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 →

Feedback