# NousResearch/hermes-agent · Retry 403 responses flagged as server_error

## Open now

- 1 issue, 3 PRs open on GitHub.
- #117869: fix(agent): a 403 whose error body self-identifies as server_error should be retried, not treated as a credential refusal
- PR #117871: fix(agent): retry a relay 403 stamped code=server_error instead of benching the credential
- PR #117874: fix(agent): retry a 403 whose error body self-identifies as server_error
- PR #134714: fix(opencode): a relay 403 stamped code=server_error retries instead of benching the key \[risk 0.80\]

These issues and PRs address agent behavior when receiving a 403 response whose error body identifies itself as a server_error, arguing it should be retried rather than treated as a credential failure. The change prevents credentials from being dropped or the agent being benched in such cases.

## TL;DR

- 7 member(s): 1 open issue(s), 0 closed issue(s), 3 open PR(s), 0 merged PR(s), 3 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.29`: 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

- #117869: fix(agent): a 403 whose error body self-identifies as server_error should be retried, not treated as a credential refusal

## Prior & competing PRs

- **#117871: fix(agent): retry a relay 403 stamped code=server_error instead of benching the credential**. open
  - maintainer direction: category `duplicate_of`; implication `duplicate`; refs `02cdb0505baf1152eaf3d5252e3d5c065cc78d4d`, `#117874`, `#117874`
  - files: `agent/error_classifier.py`, `tests/agent/test_403_relay_credential_recovery.py`, `tests/agent/test_error_classifier_403_relay.py`, `tests/fixtures/opencode_go_403_relay_envelopes.json`
- **#117874: fix(agent): retry a 403 whose error body self-identifies as server_error**. open
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `#117869`
  - files: `agent/error_classifier.py`, `tests/agent/test_error_classifier.py`
- **#117911: fix(agent): retry 403 with server_error code instead of auth-failing**. closed without merge
  - maintainer direction: category `uncategorized`; implication `needs_llm`
- **#118295: fix(agent): retry 403 server errors without dropping credentials**. closed without merge
  - maintainer direction: category `superseded_by_pr`; implication `superseded`; refs `#117869`, `#118286`, `#117869`, `#117871`
- **#119579: fix(agent): retry 403 with server_error code instead of auth-failing (closes #117869)**. closed without merge
  - maintainer direction: category `uncategorized`; implication `needs_llm`; refs `#117869`, `#117869`
- **#134714: fix(opencode): a relay 403 stamped code=server_error retries instead of benching the key \[risk 0.80\]**. open
  - maintainer direction: category `uncategorized`; implication `needs_llm`
  - files: `plugins/model-providers/opencode-zen/__init__.py`, `tests/agent/test_403_relay_credential_recovery.py`, `tests/fixtures/opencode_go_403_relay_envelopes.json`, `tests/plugins/model_providers/test_opencode_go_profile.py`

## Fix status

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