# NousResearch/hermes-agent · NODE_EXTRA_CA_CERTS dropped in Bitwarden vault backend

## Open now

- 1 issue, 2 PRs open on GitHub.
- #120512: Bitwarden vault backend strips NODE_EXTRA_CA_CERTS, making self-hosted Vaultwarden behind a private CA unreachable
- PR #120513: fix(vault): forward NODE_EXTRA_CA_CERTS to the bw child
- PR #120967: fix(vault): keep NODE_EXTRA_CA_CERTS and TLS CA env vars in Bitwarden backend

The Bitwarden vault backend strips NODE_EXTRA_CA_CERTS and related TLS CA environment variables, breaking connectivity to self-hosted Vaultwarden instances behind a private CA. These items track the problem and proposed fixes to forward those variables to the bw child process.

## TL;DR

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

- #120512: Bitwarden vault backend strips NODE_EXTRA_CA_CERTS, making self-hosted Vaultwarden behind a private CA unreachable

## Prior & competing PRs

- **#120513: fix(vault): forward NODE_EXTRA_CA_CERTS to the bw child**. open
  - maintainer direction: category `silent_close`; implication `active`
  - files: `agent/vault_backends/bitwarden.py`, `tests/agent/test_vault_backends.py`
- **#120967: fix(vault): keep NODE_EXTRA_CA_CERTS and TLS CA env vars in Bitwarden backend**. open
  - maintainer direction: category `silent_close`; implication `active`
  - files: `agent/vault_backends/bitwarden.py`, `tests/agent/test_bitwarden_tls_env.py`

## Fix status

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