{"repo":"NousResearch/hermes-agent","public_id":"81281","display_label":"Egress CONNECT auth fix for mapped providers","summary":"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.","subsystem":"agent/proxy_sources","counts":{"members":5,"open_issues":1,"open_issues_distinct":1,"open_prs":2,"closed_issues":0,"merged_prs":0,"attempt_prs":4},"landed_fix":null,"resolution":{"state":"unresolved","by":null},"freshness":{"state":"never_verified","last_verified_at":null,"is_stale":false},"grouping":{"backbone":"STRUCTURAL_SPANNING","link_density":0.4},"fix_edges":[],"members":[{"kind":"issue","number":81281,"title":"[Bug]: egress: sandbox cannot reach mapped providers — rootless bind topology + secrets `require: true` rejecting the synthetic CONNECT","url":null,"state":"open"},{"kind":"pr","number":81291,"title":"fix(egress): allow mapped CONNECTs to reach MITM (#81281)","url":null,"state":"closed","close_reason":{"category":"stale_abandoned","implication":"active"},"merged":false},{"kind":"pr","number":122826,"title":"fix(egress): keep secret require rules off the CONNECT handshake","url":null,"state":"open","close_reason":{"refs":[{"kind":"commit","value":"364aae99367","number":0}],"category":"uncategorized","implication":"needs_llm"},"merged":false},{"kind":"pr","number":128572,"title":"fix(egress): do not require proxy token on synthetic CONNECT (#81281)","url":null,"state":"closed","close_reason":{"category":"uncategorized","implication":"needs_llm"},"merged":false},{"kind":"pr","number":136798,"title":"fix(agent): generate secrets require:false so mapped-host CONNECT tunnels survive","url":null,"state":"open","close_reason":{"category":"silent_close","implication":"active"},"merged":false}],"trust":{"default_tier":"verified","includes_suggested":false}}