NousResearch/hermes-agent
Lazy cryptography import fix for Bitwarden plugin
Cluster 86735. Data as of
Nothing open on GitHub. Fix merged in #86857 on 15 Aug 2026. Check it covers your case.
The short answer
0open issues
0open PRs
3items grouped
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #86857. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #86857. That is separate from the fix event. - Still open
- 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.
Open issues0
Open PRs0
Fixes on record
-
#86857 fix(update): self-lock deferral fires only when the swap is actually at risk
files:
hermes_cli/main.py,hermes_cli/update_cmd.py,tests/hermes_cli/test_update_self_lock.py
1 PR closed without merging
From the close comments: partial fix 1
-
#86826 fix(agent): import cryptography lazily in the Bitwarden secret source (#86735) · partial fix →
#86826,#86735,#86782,#84114,#77517
Closed issues · 1
- Closed#86735hermes update always fails exit 2: "already loaded native venv modules: cryptography" on Windows — bitwarden.py imports cryptography at module level
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means 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 LabAt a glance
- Merged PRs
- #86857
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 15 Aug 2026