Claude Code v2.1.222 ·
Unsafe-PATH command resolution guard, off in this build
A guard that would reject commands found only in your current directory stays disabled.
Nothing to try yetTier: how much it should matter to you
3Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
SandboxArea: what it touches
In DevelopmentKind: in v2.1.222,
What probably matters to youSection of the release
Three spawn wrappers now share an unsafe-PATH check, but its controlling predicate returns false so nothing is refused.
What
A third spawn wrapper picked up the same guard as the other two: resolve the command and refuse it if it only resolves inside the current directory.
Details
- The predicate that controls all three call paths is a function that returns false in this build, so no command is refused at runtime.
- If enabled, a command found only in the current directory would be rejected as being in an unsafe location.
Evidence
not found or is in an unsafe location (current directory)
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.222 →
