NousResearch/hermes-agent

Egress CONNECT auth fix for mapped providers

Cluster 81281 · agent/proxy sources. Data as of

3 open items. Fix attempted, not merged.

The short answer

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

These items concern a bug where sandbox egress fails to reach mapped providers due to proxy token requirements being incorrectly applied to synthetic CONNECT requests. Two related fixes address the MITM routing and token-requirement logic.

Open issues1

  • Issue#81281[Bug]: egress: sandbox cannot reach mapped providers — rootless bind topology + secrets `require: true` rejecting the synthetic CONNECT

Open PRs2

  • PR#122826fix(egress): keep secret require rules off the CONNECT handshake
  • PR#136798fix(agent): generate secrets require:false so mapped-host CONNECT tunnels survive

2 PRs closed without merging

From the close comments: stale or abandoned 1 · other 1

  • #81291 fix(egress): allow mapped CONNECTs to reach MITM (#81281) · stale or abandoned
  • #128572 fix(egress): do not require proxy token on synthetic CONNECT (#81281) · other
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.40: 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/proxy sources
Closed issues
0
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.