# NousResearch/hermes-agent · Buzz gateway access to external/managed secrets

## Open now

- Nothing open on GitHub.

These items concern the Buzz gateway's inability to see privately or externally managed secrets (such as Bitwarden-held keys) during preflight and requirement checks. A fix addresses secret visibility alongside related auth and environment isolation concerns.

## 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 #99427. Verify it addresses your case.
- **Recommended:** read PR #99427 (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: `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.

## Closed / duplicate issues

- #95216: Buzz gateway preflight cannot see Bitwarden-managed private key

## Prior & competing PRs

- **#99427: fix(buzz): npub allowlists, per-profile auth, external secrets, and multiplex env isolation all work now (salvages #78435 #83155 #95224 #98748)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `contributors/emails/[redacted:email]`, `gateway/authz_mixin.py`, `plugins/platforms/buzz/adapter.py`, `tests/gateway/test_buzz_adapter.py`, `tests/gateway/test_buzz_authz.py`, `tests/gateway/test_buzz_websocket.py`, `tests/gateway/test_multiplex_profile_authz.py`, `tests/plugins/platforms/buzz/test_buzz_unscoped_requirement_gate.py`
- **#95224: fix(buzz): let the requirement gate see externally managed secrets**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `#99427`, `#95216`

## Fix status

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