NousResearch/hermes-agent

CLI startup update check SSH prompt interference

Cluster 104591. Data as of 2026-10-24 04:06 UTC

Nothing open on GitHub. Fix merged in #104996 on 7 Sep 2026. Check it covers your case.

open issues

open PRs

items grouped

Known?: Yes. 4 related items grouped here, 1 issue already closed.
Fix event: A fix was merged to main in PR #104996. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this resolved, deciding PR #104996. That is separate from the fix event.
Still open: Nothing open on GitHub.

Next step: read #104996, then check it covers your case.

Read #104996 Pick up a Lab task

These issues and PRs concern the CLI's background update-check process inadvertently triggering interactive SSH host-key prompts that hijack terminal input. The work addresses how the update check's git environment is configured to prevent SSH from accessing the TTY.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

#104996 Startup update checks avoid SSH host-key prompts by default (#104591, salvage #104599)

merged to main

files: evals/update_check_ssh_pty.py, hermes_cli/_subprocess_compat.py, hermes_cli/banner.py, tests/hermes_cli/test_banner_git_state.py, tests/hermes_cli/test_noninteractive_git.py, tests/hermes_cli/test_update_check.py, website/docs/user-guide/configuration.md

2 PRs closed without merging

From the close comments: duplicate 1 · merged via another change 1

#104599 fix(cli): probe update-check origin URL under the fetch's isolated git env · merged via another change → 03c20ba, 9f0bf22, 9197afe, 3a42722, #104996, #104591, #104647
#104647 fix(cli): update check never hands the tty to ssh (#104591) · duplicate → #104599, #104591

Closed issues · 1

Closed#104591Startup update check spawns interactive ssh host-key prompt that hijacks CLI input (insteadOf + GIT_CONFIG_GLOBAL=/dev/null mismatch)

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

Merged PRs: #104996
Closed issues: 1
Attempts: 2 PRs closed without merging
Fix link checked: 7 Sep 2026

For your agent

The same facts, typed.

cluster/104591.json
cluster/104591.md