Cairn

Oneshot exit code fix for failures

NousResearch/hermes-agent · cluster 74659 · hermes cli

Data as of

4 open items. Fix attempted, not merged.

The short answer

1open issue
3open PRs
4items grouped
Known?
Yes. 4 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 3 PRs.

These items address a bug where the oneshot/hermes -z mode incorrectly exits with code 0 on HTTP 402 errors and agent/provider refusals, causing unattended callers to misread failures as success.

Open issues1

  • Issue#74659hermes -z (oneshot) exits 0 on HTTP 402 and on agent refusal — unattended callers read success

Open PRs3

  • PR#74708fix(oneshot): return nonzero for unsuccessful runs
  • PR#74777fix(cli): oneshot exits non-zero on HTTP 402 and provider refusal (#74659)
  • PR#104211feat(oneshot): preserve structured terminal-failure facts in the usage report
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
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/74659.json
cluster/74659.md