# NousResearch/hermes-agent · Auxiliary provider auth failure skips task fallback chain

## Open now

- Nothing open on GitHub.

A bug where a 401 error on an explicit auxiliary provider fails to walk the task's own configured fallback chain. The fix ensures auth failures on explicit auxiliary providers correctly honor the task-level fallback chain.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 1 PR(s) closed without merging.
- A fix was merged to main in PR #114868. Verify it addresses your case.
- **Recommended:** read PR #114868 (and any competing PRs below) before filing. Confirm the merged change covers your symptom.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `resolved` · deciding PR(s): `pr-114868`. 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.

## Closed / duplicate issues

- #114060: \[Bug\]: an auth error on an explicit auxiliary provider never reaches the task's own configured fallback_chain

## Prior & competing PRs

- **#114868: fix(aux): a 401 on an explicit auxiliary provider walks that task's own fallback_chain (#114060, salvage #114066)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `agent/auxiliary_client.py`, `tests/agent/test_auxiliary_auth_rung_fallthrough.py`, `website/docs/user-guide/features/fallback-providers.md`
- **#114066: fix(auxiliary): honor task fallback after explicit auth failure**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `fe6b5cfd156a`, `#114868`, `#114060`, `#114066`

## Fix status

- Merged to main in PR #114868 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-09-18`.