Cairn
NousResearch/hermes-agent

SSH config ignored in doctor connectivity check

Cluster 29481 · hermes cli. Data as of

1 open item. Fix attempted, not merged.

The short answer

0open issues
1open PR
4items grouped
Known?
Yes. 4 related items grouped here, 1 issue already closed.
Fix event
No fix has been merged to main. 2 PRs 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 1 PR.

These issues and PRs concern a bug where the doctor command's SSH backend check does not respect configured SSH user, port, key, or environment-aware settings. The fixes aim to make the SSH connectivity check honor the relevant configuration values.

Open issues0

No open issues.

Open PRs1

  • PR#29498fix(doctor): match SSH backend host key policy

2 PRs closed without merging

From the close comments: merged via another change 1 · superseded by another PR 1

  • #26851 fix(doctor): SSH connectivity check ignores TERMINAL_SSH_USER / PORT / KEY · merged via another change → #27382
  • #29509 fix(doctor): use .env-aware config for SSH backend check · superseded by another PR
Closed issues · 1
  • Closed#29481[Bug]: hermes doctor SSH check ignores configured SSH user/port/key
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
hermes cli
Closed issues
1
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/29481.json
cluster/29481.md