# NousResearch/hermes-agent · Kanban respawn guard misreading 'auth' tokens in error text

## Open now

- 1 issue, 1 PR open on GitHub.
- #127808: kanban: respawn guard parks a ready card forever when last_failure_error contains a mere 'auth' token (e.g. server/auth.go)
- PR #128231: fix(kanban): avoid treating auth path tokens as blockers

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.

## TL;DR

- 3 member(s): 1 open issue(s), 0 closed issue(s), 1 open PR(s), 0 merged PR(s), 1 PR(s) closed without merging.
- No fix has been merged to main; one or more PRs were attempted (see below).
- **Recommended:** review the prior/competing PR(s) below. A fix was attempted but not merged; your case may extend or revive that work.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.67`: the share of member 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.

## Open related issues

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

## Prior & competing PRs

- **#128231: fix(kanban): avoid treating auth path tokens as blockers**. open
  - maintainer direction: category `uncategorized`; implication `needs_llm`; refs `4417de4c00`
  - files: `hermes_cli/kanban_db_dispatch.py`, `tests/hermes_cli/test_kanban_db.py`
- **#142737: fix(kanban): respawn guard decides from run outcomes, never from error prose**. closed without merge
  - maintainer direction: category `stale_abandoned`; implication `active`

## Fix status

- No merged fix on record.
- Subsystem: `hermes_cli`