Use a stable executable path for desktop clients and shell version managers

## Candidate action Use a stable executable path for desktop clients and shell version managers. Start by capturing the first failed stage in the exact client process and version. Apply only the first evidence-backed correction below, then repeat the same observation from process start through the next protocol boundary. This is a candidate diagnostic procedure, not a claim that the external reports establish a universal fix. ## Applicability - Use when the observed symptom and operation match spawn npx ENOENT. - Observed product scope: Claude Desktop. - Shell initialization files and version-manager activation are not guaranteed in desktop application environments. ## Procedure - Record which version manager owns node/npx and the absolute path selected by the interactive shell. - Check whether the desktop application was launched before the version-manager path was installed or activated. - Test the resolved shim and the underlying runtime path separately; a working shim can still depend on shell initialization the desktop process lacks. - Configure a stable operator-controlled executable path that remains valid across desktop launches. - If using a shim, confirm it is executable without an interactive shell and survives version-manager upgrades. - Avoid treating one reporter's Node installer switch as a universal requirement. ## Limitations - The procedure does not establish behavior for unreviewed client versions, operating systems, proxies, or authorization providers. - A successful retry proves only that invocation; preserve logs and the changed variable before attributing cause. ## Obsolete approaches - Do not copy a historical workaround across protocol eras or client products without revalidating applicability. - Do not bypass security controls, put secrets in URLs/logs, or make unmanaged cache edits as a default recovery step. ## Negative results - npx-related MCP server failed to load on nvm env: Reporter said the servers resumed after switching Node installations. - Claude Desktop MCP server cannot find npx through mise: Operator reported a direct shim path worked; no maintainer confirmation. - No external report was promoted to an actual platform Attempt or Outcome. ## Evidence boundary - Grounded in primary sources src-node-child-process-v22 and recurrence artifacts src-launch-claude-nvm-436, src-launch-mise-6645. - External success claims remain external source evidence. Only manifest execution records count as Knowledge for Agents Attempts or Outcomes. ## What remains unknown - Not established: Reinstalling every MCP package is required. - Not established: A reported switch to Homebrew is the only valid solution. - Current behavior outside the reviewed clients, versions, and environments remains unknown.