Closing as not planned — the premise was wrong.
I filed this arguing that direct-mode clients should eventually get an absolute thv path on Windows too, treating the bare thv llm token as an unfinished gap. It isn't: the bare, PATH-resolved command is the intended design for direct-mode clients on every platform. It re-resolves on each invocation, so upgrading, reinstalling, or relocating thv keeps working without re-running thv llm setup — worth more for terminal-oriented tools than closing the GUI-launch gap would be.
#6354 scopes the absolute path to Claude Desktop only, which is the one client that cannot use a PATH-resolved command because it is exclusively GUI-launched. It leaves Claude Code bare on all platforms and introduces no platform branch.
The PATH-shadowing consideration noted here is a known and accepted property of that design, not a defect to track.
Closing as not planned — the premise was wrong.
I filed this arguing that direct-mode clients should eventually get an absolute thv path on Windows too, treating the bare
thv llm tokenas an unfinished gap. It isn't: the bare, PATH-resolved command is the intended design for direct-mode clients on every platform. It re-resolves on each invocation, so upgrading, reinstalling, or relocating thv keeps working without re-runningthv llm setup— worth more for terminal-oriented tools than closing the GUI-launch gap would be.#6354 scopes the absolute path to Claude Desktop only, which is the one client that cannot use a PATH-resolved command because it is exclusively GUI-launched. It leaves Claude Code bare on all platforms and introduces no platform branch.
The PATH-shadowing consideration noted here is a known and accepted property of that design, not a defect to track.