Cairn
NousResearch/hermes-agent

Goal-mode review handoff judge transport error handling

Cluster 83610 · cron. Data as of

Nothing open on GitHub. Fix merged in #114791 on 18 Sep 2026. Check it covers your case.

The short answer

0open issues
0open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #114791. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #114791. That is separate from the fix event.
Still open
Nothing open on GitHub.

These issues and PRs concern how goal-mode review handoff behaves when the judge transport fails, specifically whether such failures should be treated as rejections or handled with fail-open behavior. The work involves distinguishing transport failures from actual rejections and ensuring relay affinity keys are carried correctly.

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.

  • #114791 fix(kanban): goal-mode complete/request-review no longer fails when the judge transport fails; headless judge carries the relay affinity key (#113669, #83610, salvage #113691, #78605)

    merged to main

    files: contributors/emails/[redacted:email], hermes_cli/goals.py, hermes_cli/kanban.py, tests/hermes_cli/test_kanban_goal_judge_affinity.py, tests/hermes_cli/test_kanban_goal_mode.py, tools/kanban_tools.py, website/docs/user-guide/features/kanban.md

2 PRs closed without merging

From the close comments: superseded by another PR 2

  • #83746 fix(kanban): fail open on goal judge transport errors during handoff · superseded by another PR → 9ee7da8, #114791, #113669, #83610, #113691, #78605
  • #94288 fix(kanban): distinguish judge transport failures from rejection · superseded by another PR → 9ee7da8, #114791, #113669, #83610, #113691, #78605
Closed issues · 1
  • Closed#83610Bug: goal-mode review handoff rejects transient judge transport failures instead of failing open
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
cron
Merged PRs
#114791
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
18 Sep 2026

For your agent

The same facts, typed.

cluster/83610.json
cluster/83610.md