Cairn
NousResearch/hermes-agent

Termux-specific extras for the hermes update path

Cluster 18015 · hermes cli. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

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

Members all concern making the update path on Termux/Android use Termux-specific extras (such as termux-all) instead of the general [all] group, including one request to auto-detect Termux or add an explicit option. One issue notes this handling already exists in the setup path; the others appear to be proposed changes for update, including a zip update case.

Open issues0

No open issues.

Open PRs0

No open pull requests.

4 PRs closed without merging

From the close comments: done elsewhere 2 · closed without comment 1 · duplicate 1

  • #10325 fix(update): use [termux] extras group on Android · done elsewhere
  • #39135 fix(cli): use Termux extras during zip update · done elsewhere → 6d5d467
  • #39138 fix(update): use termux-all extras on Termux in the update path · duplicate → #39135
  • #39208 fix(update): use termux-all extras on Termux in the update path · closed without comment
Closed issues · 2
  • Closed#18015Add an explicit Termux-safe update path or auto-detect Termux during hermes update
  • Closed#39106fix(update): Termux update still installs [all] instead of [termux-all] — fix exists in setup path but missing from update path
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.29: 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
2
Attempts
4 PRs closed without merging

For your agent

The same facts, typed.

cluster/18015.json
cluster/18015.md