Retry 403 responses flagged as server_error

NousResearch/hermes-agent · cluster 117869 · agent

Data as of

4 open items. Fix attempted, not merged.

The short answer

1open issue
3open PRs
7items grouped
Known?
Yes. 7 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 3 PRs 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 3 PRs.

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.

Open issues1

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

Open PRs3

  • PR#117871fix(agent): retry a relay 403 stamped code=server_error instead of benching the credential
  • PR#117874fix(agent): retry a 403 whose error body self-identifies as server_error
  • PR#134714fix(opencode): a relay 403 stamped code=server_error retries instead of benching the key [risk 0.80]

3 PRs closed without merging

From the close comments: superseded by another PR 1 · other 2

  • #117911 fix(agent): retry 403 with server_error code instead of auth-failing · other
  • #118295 fix(agent): retry 403 server errors without dropping credentials · superseded by another PR → #117869, #118286, #117871
  • #119579 fix(agent): retry 403 with server_error code instead of auth-failing (closes #117869) · other → #117869
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.29: 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
agent
Closed issues
0
Attempts
3 PRs closed without merging

For your agent

The same facts, typed.