Cairn
NousResearch/hermes-agent

CLI exit code propagation and silent failure bugs

Cluster 62810 · hermes cli. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
4items grouped
Known?
Yes. 4 related items grouped here, 0 issues 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
1 issue and 1 PR.

These issues and PRs address cases where CLI commands return exit code 0 despite failures, including skills install resolution errors and integer exit statuses being dropped by the command dispatcher.

Open issues1

  • Issue#62810[Bug]: CLI exit-status compatibility: boolean handler success exits 1

Open PRs1

  • PR#62832fix(console): preserve integer command-handler exit statuses (#62810)

2 PRs closed without merging

From the close comments: won't fix / by design 1 · other 1

  • #43645 fix: propagate CLI command exit codes · won't fix / by design
  • #104432 fix(cli): treat bool handler results as success, not exit 1 · other → #62810, #62826, #103272
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
0
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/62810.json
cluster/62810.md