NousResearch/hermes-agent

MCP test command exit code on failure

Cluster 114230. Data as of 2026-10-24 13:18 UTC

Nothing open on GitHub. Fix merged in #114865 on 18 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 #114865. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this resolved, deciding PR #114865. That is separate from the fix event.
Still open: Nothing open on GitHub.

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

Read #114865 Pick up a Lab task

These issues and PRs concern 'hermes mcp test' not returning non-zero exit codes when a connection fails or a server is unknown, making it unreliable for automation. The work addresses adding distinct non-zero exit codes for different failure scenarios.

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.

#114865 fix(mcp): hermes mcp test exits 1 on connection failure and 3 on unknown server (#114230, salvage #70287)

merged to main

files: contributors/emails/[email protected], hermes_cli/main.py, hermes_cli/mcp_config.py, tests/hermes_cli/test_mcp_config.py, website/docs/guides/use-mcp-with-hermes.md

2 PRs closed without merging

From the close comments: superseded by another PR 2

#114235 fix(mcp): make failed server probes fail automation · superseded by another PR → 22ead77, #114865, #114230, #70287
#114237 fix(cli): make 'hermes mcp test' exit non-zero on failure · superseded by another PR → 22ead77, #114865, #114230, #70287

Closed issues · 1

Closed#114230hermes mcp test exits 0 for a connect, a connection failure and an unknown server — please exit non-zero or add --json

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: #114865
Closed issues: 1
Attempts: 2 PRs closed without merging
Fix link checked: 18 Sep 2026

For your agent

The same facts, typed.

cluster/114230.json
cluster/114230.md