Cairn
NousResearch/hermes-agent

Kanban card completion misclassifying branch-rules 403 as auth blocker

Cluster 132473 · hermes cli. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 1 PR 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 items concern the kanban PR-URL completion flow, where a 403 from the branch-rules endpoint is reportedly read as an infrastructure issue and then matched as an auth blocker, leaving a card parked. The two fix-titled items describe changing the respawn guard to rely on run outcomes rather than error text, and treating a branch-rules refusal as having no rules.

Open issues1

  • Issue#132473kanban: PR-URL completion contract parks a card forever when the branch-rules endpoint 403s (read as infra, then matched as blocker_auth)

Open PRs1

  • PR#132479fix(kanban): treat a branch-rules refusal as no rules, not an auth blocker

1 PR closed without merging

From the close comments: stale or abandoned 1

  • #142737 fix(kanban): respawn guard decides from run outcomes, never from error prose · stale or abandoned
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
1 PR closed without merging

For your agent

The same facts, typed.

cluster/132473.json
cluster/132473.md