# NousResearch/hermes-agent · Proxy env vars dropped in stdio MCP subprocesses

## Open now

- 1 issue, 0 PRs open on GitHub.
- #106984: Stdio MCP subprocess environment drops http_proxy/https_proxy/no_proxy

Stdio MCP subprocesses were not inheriting HTTP proxy environment variables from the parent process. These members address identifying and fixing that forwarding gap.

## TL;DR

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

- #106984: Stdio MCP subprocess environment drops http_proxy/https_proxy/no_proxy

## Prior & competing PRs

- **#106988: fix(mcp): forward proxy env vars to stdio MCP subprocesses**. closed without merge
  - maintainer direction: category `wontfix_bydesign`; implication `wontfix`
- **#107851: fix(mcp): preserve proxy env vars in stdio subprocess env (#106984)**. closed without merge
  - maintainer direction: category `silent_close`; implication `active`

## Fix status

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