Cairn
NousResearch/hermes-agent

install.sh --no-venv flag and shim creation fixes

Cluster 31383 · apps/bootstrap-installer. Data as of

2 open items. Fix attempted, not merged.

The short answer

0open issues
2open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 1 issue already closed.
Fix event
No fix has been merged to main. 1 PR closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
0 issues and 2 PRs.

These issues and PRs concern broken behavior in install.sh when using the --no-venv flag, specifically around uv unexpectedly creating a virtual environment and the shim not being created as a result. Multiple fix attempts address shim creation and install target detection under this scenario.

Open issues0

No open issues.

Open PRs2

  • PR#31391fix(install): detect actual Hermes install target
  • PR#31405fix(install): create shim when --no-venv but uv created venv anyway (#31383)

1 PR closed without merging

From the close comments: other 1

  • #31390 fix(install): create shim under --no-venv when uv materialized a venv (#31383) · other → #31391
Closed issues · 1
  • Closed#31383install.sh: --no-venv flag is broken — uv sync always creates venv, shim never created
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.50: 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/bootstrap-installer
Closed issues
1
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/31383.json
cluster/31383.md