Cairn
NousResearch/hermes-agent

Kanban respawn guard misreading 'auth' tokens in error text

Cluster 127808 · 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 respawn guard, which reportedly keeps a ready card parked when last_failure_error contains an 'auth' token such as a path like server/auth.go. The related pull request titles describe changing the guard to rely on run outcomes rather than error prose and to avoid treating auth path tokens as blockers.

Open issues1

  • Issue#127808kanban: respawn guard parks a ready card forever when last_failure_error contains a mere 'auth' token (e.g. server/auth.go)

Open PRs1

  • PR#128231fix(kanban): avoid treating auth path tokens as blockers

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/127808.json
cluster/127808.md