Peer DM command exit code when remote agent errors

NousResearch/hermes-agent · cluster 136472 · hermes cli

Data as of

3 open items. Fix attempted, not merged.

The short answer

1open issue
2open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 2 PRs.

Three members (one bug report and two fix PRs) concern hermes peer dm returning exit code 0 when the peer's agent turn errors out, making these cases look like successful replies. The PRs propose making an errored remote turn exit with code 1; titles alone do not show whether either change has been merged.

Open issues1

  • Issue#136472[Bug]: `hermes peer dm` exits 0 when the peer's agent fails — a failed DM is indistinguishable from an answered one

Open PRs2

  • PR#136476fix(peer): report failed remote agent turns with exit one
  • PR#136479fix(peer): a failed peer-DM turn exits 1, not a silent success
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
0 PRs closed without merging

For your agent

The same facts, typed.