{"version":"2.1.227","anchor":"launcher-wrapper-variable-warns-clearly-when-it-cannot-be-us","canonical_anchor":"launcher-wrapper-variable-warns-clearly-when-it-cannot-be-us","heading":"Launcher wrapper variable warns clearly when it cannot be used","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/launcher-wrapper-variable-warns-clearly-when-it-cannot-be-us","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Launcher wrapper variable warns clearly when it cannot be used\n\nA bad process-wrapper variable now logs clearly, and on Windows warns it is ignored entirely.\n\n**What**\n\nThe 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.\n\n**Details**\n\n- Only logged when the variable is set.\n\n**Evidence**\n\n`is set but ignored on Windows \\u2014 the launcher must exec into Claude Code, which Windows can't do; sessions run unwrapped`\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}