Cairn

Explain why approval prompts escalate to a human

NousResearch/hermes-agent · cluster 135802 · gateway

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.

The three members all concern approval flows that ask a human for input, focusing on making the reason clear. They discuss distinguishing guardian or infrastructure failures, fail-closed escalations, manual mode, and fallback-route verdicts from genuine guardian ESCALATE outcomes by passing the reason through to the prompt.

Open issues1

  • Issue#135802Smart approvals: infra failures are indistinguishable from genuine ESCALATE — thread the failure reason through to the prompt

Open PRs2

  • PR#135832fix(approval): tell fail-closed escalates from genuine guardian ESCALATEs
  • PR#136674fix(approvals): announce why a human is being asked - guardian failure, manual mode, or a fallback-route verdict
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
gateway
Closed issues
0
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/135802.json
cluster/135802.md