Cairn

Windows venv console script launcher fixes

NousResearch/hermes-agent · cluster 39185 · hermes cli

Data as of

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

The short answer

0open issues
0open PRs
5items grouped
Known?
Yes. 5 related items grouped here, 2 issues already closed.
Fix event
A fix was merged to main in PR #54457. 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.

These issues and PRs address problems with console script entry points and launchers not being created or found correctly in Windows virtual environments. Work spans PATH propagation, missing .exe files, and repair/verification of launchers during install and update operations.

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.

  • #54457 fix(windows): repair missing console script launchers

    merged to main

    files: hermes_cli/main.py, scripts/install.ps1, tests/hermes_cli/test_verify_console_scripts.py

2 PRs closed without merging

From the close comments: done elsewhere 1 · superseded by another PR 1

  • #39396 fix(cli): propagate venv Scripts to session PATH on Windows install (#39185) · done elsewhere → 95994bb, #39185
  • #53203 fix(windows): verify launchers after primary install · superseded by another PR → #54457, #52940
Closed issues · 2
  • Closed#39185hermes command not available on Windows — missing .exe entry point in venv/Scripts/
  • Closed#52931Windows: hermes.exe console_script entry point missing after uv pip install -e .
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.34: 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
hermes cli
Merged PRs
#54457
Closed issues
2
Attempts
2 PRs closed without merging
Fix link checked
28 Jun 2026

For your agent

The same facts, typed.

cluster/39185.json
cluster/39185.md