Cairn
NousResearch/hermes-agent

Environment variables not reaching MCP stdio server subprocesses

Cluster 37499 · agent. Data as of

1 open item. Fix merged in #69053 on 22 Jul 2026. Check it covers your case.

The short answer

0open issues
1open PR
6items grouped
Known?
Yes. 6 related items grouped here, 3 issues already closed.
Fix event
A fix was merged to main in PR #69053. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this partially resolved, deciding PR #69053. That is separate from the fix event.
Still open
0 issues and 1 PR.

Most members concern env vars (Bitwarden-injected secrets, .hermes/.env values, and some tool runtime variables) not being passed to MCP stdio server subprocesses, with several PRs proposing fixes. One member is only a duplicate-closure notice, and the _SAFE_ENV_KEYS change is a related but somewhat distinct allowlist adjustment.

Open issues0

No open issues.

Open PRs1

  • PR#55047fix(tools): add tool runtime env vars (BUN_INSTALL, NODE_OPTIONS, DENO_INSTALL) to _SAFE_ENV_KEYS

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #69053 fix(mcp): pass secret-source-injected env vars to stdio servers (salvage #37523)

    merged to main

    files: tests/tools/test_mcp_tool.py, tools/mcp_tool.py

1 PR closed without merging

From the close comments: merged via another change 1

  • #37523 fix(mcp): pass Bitwarden secrets to stdio servers · merged via another change → #69053, #37499
Closed issues · 3
  • Closed#37499Bug: Bitwarden-injected secrets are not available to MCP stdio servers
  • Closed#44546Duplicate — closed in favour of #44548
  • Closed#44548.hermes/.env vars not propagated to MCP server subprocesses — credential duplication friction
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.25: 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
Merged PRs
#69053
Closed issues
3
Attempts
1 PR closed without merging
Fix link checked
22 Jul 2026

For your agent

The same facts, typed.

cluster/37499.json
cluster/37499.md