A bad process-wrapper variable now logs clearly, and on Windows warns it is ignored entirely.
What's wrong with this entry?
The environment variable naming a process wrapper is now validated once and cached. If the value is unusable, an error-level log says sessions that require it will refuse to start rather than run unwrapped. On Windows it logs a warning that the value is ignored, because the launcher must exec into Claude Code, so sessions run unwrapped.
- Only logged when the variable is set.
is set but ignored on Windows \u2014 the launcher must exec into Claude Code, which Windows can't do; sessions run unwrapped
Strings lifted out of the shipped bundle, so the claim above can be checked against them.