Windows PATH node priority during desktop install

NousResearch/hermes-agent · cluster 82309 · apps/desktop

Data as of 2026-10-22 12:15 UTC

Nothing open on GitHub. Fix merged in #125589. Check it covers your case.

open issues

open PRs

items grouped

Known?: Yes. 6 related items grouped here, 1 issue already closed.
Fix event: A fix was merged to main in PR #125589. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open: Nothing open on GitHub.

Next step: read #125589, then check it covers your case.

Read #125589 Pick up a Lab task

These items address a problem where a system-installed Node appearing before the managed Node on PATH causes install script failures on Windows. Two fixes aim to make the managed Node take precedence in that context.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

#125589 fix: Hermes never falls back to the user's node/npm/npx/uv

merged to main

files: agent/lsp/install.py, hermes_cli/doctor_tools.py, hermes_cli/gateway.py, hermes_cli/main_install_repair.py, hermes_cli/source_build.py, hermes_constants.py, scripts/install.ps1, scripts/install.sh, tests/e2e/core/upgrade/_install_helpers.py, tests/fixtures/resolution_allowlist.json, tests/gateway/test_adapter_connect_classification.py, tests/gateway/test_whatsapp_connect.py, tests/gateway/test_whatsapp_stale_bridge.py, tests/hermes_cli/test_desktop_update_verify.py, tests/hermes_cli/test_gateway_service.py, tests/hermes_cli/test_node_runtime_npm_resolution.py, tests/hermes_cli/test_source_build.py, tests/hermes_cli/test_web_ui_build.py, tests/plugins/platforms/photon/test_npm_error_log_regression.py, tests/plugins/platforms/photon/test_runtime_record.py (+5 more)
#125635 MCP stdio servers keep their configured PATH order again (revert #124792)

merged to main

files: tests/tools/test_mcp_tool_issue_948.py, tools/mcp_tool_common.py
#125721 fix: Hermes's own lint, activate, tui and MCP launchers use PM's node/npx/uv, never the user's

merged to main

files: hermes_platform/resolver/known_dirs.py, pm/__init__.py, pm/install.py, tests/agent/lsp/test_install_and_lint_fixes.py, tests/agent/lsp/test_shell_linter_lsp_skip.py, tests/fixtures/resolution_allowlist.json, tests/gateway/test_tui_slash_worker_path.py, tests/pm/test_startup_activation.py, tests/tools/test_file_operations_edge_cases.py, tests/tools/test_mcp_tool.py, tests/tools/test_mcp_tool_issue_948.py, tools/file_operations_lint.py, tools/mcp_tool_config.py, tui_gateway/server.py

2 PRs closed without merging

From the close comments: done elsewhere 1 · duplicate 1

#82355 fix(desktop): prevent Windows installs from using stale system Node · done elsewhere → ba34370, 7cadfaa, 79dbb14, 76d6798, 6ca1924, 28e6496, 8104ee6, 150b197, 5e4a2a3, 81b4c13, 26b3918, e0fae55, #124792, #82309, #125635, #82355, #91188, #125729, #125318, #125721, #108188, #108199, #126934, #125589
#91188 fix(desktop): make managed Node authoritative for Windows install scripts · duplicate → #82355

Closed issues · 1

Closed#82309[Windows] Desktop dependency install fails with ERR_REQUIRE_ESM when a system Node precedes the managed Node on PATH

How this cluster was grouped

Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
Pairwise link density 0.33: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem: apps/desktop
Merged PRs: #125589, #125635, #125721
Closed issues: 1
Attempts: 2 PRs closed without merging
Fix link checked: 28 Sep 2026

For your agent

The same facts, typed.

cluster/82309.json
cluster/82309.md