Cairn

Gateway /update broken for pip/PyPI installs

NousResearch/hermes-agent · cluster 39104 · gateway

Data as of

5 open items. Fix attempted, not merged.

The short answer

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

A cluster of bugs and fixes around the /update endpoint and CLI update path failing for pip-installed (PyPI/system) packages, primarily due to incorrect PROJECT_ROOT resolution and .git-based install detection rejecting non-git installs.

Open issues3

  • Issue#39104Gateway /update fails with "not_git_repo" for pip (PyPI) installs
  • Issue#46406[Bug]: System-installed hermes CLI resolves PROJECT_ROOT to Python package dir, not project dir — cascading failure when venv is unavailable
  • Issue#59850hermes update (Windows): dependency install runs at PROJECT_ROOT (running-CLI dir), not the extracted install root → `uv pip install -e .` exit 2

Open PRs2

  • PR#46418fix(cli): recover project root outside editable installs
  • PR#71510fix(cli): target the managed install root in the ZIP update path

6 PRs closed without merging

From the close comments: superseded by another PR 2 · closed without comment 1 · merged via another change 1 · stale or abandoned 1 · other 1

  • #39155 fix(gateway): remove .git check blocking /update on pip installs · closed without comment
  • #39157 fix(gateway): detect pip installs in /update instead of bare .git check · stale or abandoned
  • #39158 fix(gateway): allow update for pip installs · superseded by another PR → #39157, #39104
  • #39232 fix(gateway): allow /update for pip installs (#39104) · merged via another change → #39157, #39155, #39158, #39104, #54825
  • #46571 fix(cli): validate PROJECT_ROOT by walking to pyproject.toml (#46406) · other
Show 1 more
  • #59866 fix(cli): pass cwd to install functions to support update when PROJECT_ROOT diverges from install root · superseded by another PR → #71510, #59850
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.16: 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
gateway
Closed issues
0
Attempts
6 PRs closed without merging

For your agent

The same facts, typed.

cluster/39104.json
cluster/39104.md