Cairn

Fix misleading 403 error message from policy gateways

NousResearch/hermes-agent · cluster 125058 · agent

Data as of

3 open items. Fix attempted, not merged.

The short answer

1open issue
2open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 2 PRs.

A bug where a structured 403 response from a policy gateway is incorrectly surfaced to the user as an API key rejection error. The members cover the bug report and two related fixes to correctly read and display the gateway's actual refusal reason.

Open issues1

  • Issue#125058[Bug]: A 403 from a policy gateway in front of a custom endpoint is reported as "rejected your API key"

Open PRs2

  • PR#125080fix(agent): surface a policy gateway's structured 403 reason instead of API-key copy
  • PR#125094fix(classifier): read a policy gateway's structured 403 refusal instead of blaming the API key
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
agent
Closed issues
0
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/125058.json
cluster/125058.md