Cairn
NousResearch/hermes-agent

Termux/Android install and update compatibility issues

Cluster 40328 · hermes cli. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues 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
1 issue and 1 PR.

These issues and PRs address multiple problems running the project on Termux and PRoot Android environments, including uv installation hangs, wrong extras groups being used during updates, hardlink/cross-device errors, and 32-bit ARM compatibility. The members share a common theme of making installation and update paths work correctly on Android/Termux.

Open issues1

  • Issue#40328fix(update): support Termux/PRoot environments (hardlink cross-device + build isolation)

Open PRs1

  • PR#40377fix(update): support Termux/PRoot environments (UV_LINK_MODE=copy)

1 PR closed without merging

From the close comments: superseded by another PR 1

  • #40335 fix(update): detect PRoot environments and set UV_LINK_MODE=copy · superseded by another PR → #40377, #40328
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.67: 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
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/40328.json
cluster/40328.md