# NousResearch/hermes-agent · Lazy cryptography import fix for Bitwarden plugin

## Open now

- Nothing open on GitHub.

A bug where importing cryptography at module level in the Bitwarden secret source caused conflicts with native venv modules, addressed by deferring the import. One unrelated self-update locking item is also present in this group.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 1 PR(s) closed without merging.
- A fix was merged to main in PR #86857. Verify it addresses your case.
- **Recommended:** read PR #86857 (and any competing PRs below) before filing. Confirm the merged change covers your symptom.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `resolved` · deciding PR(s): `pr-86857`. 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.

## Closed / duplicate issues

- #86735: hermes update always fails exit 2: "already loaded native venv modules: cryptography" on Windows — bitwarden.py imports cryptography at module level

## Prior & competing PRs

- **#86857: fix(update): self-lock deferral fires only when the swap is actually at risk**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `hermes_cli/main.py`, `hermes_cli/update_cmd.py`, `tests/hermes_cli/test_update_self_lock.py`
- **#86826: fix(agent): import cryptography lazily in the Bitwarden secret source (#86735)**. closed without merge
  - maintainer direction: category `partial_fix`; implication `needs_llm`; refs `#86826`, `#86735`, `#86782`, `#84114`, `#77517`

## Fix status

- Merged to main in PR #86857 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-08-15`.