Cairn
NousResearch/hermes-agent

Bitwarden secrets env var aliasing and mapping

Cluster 51447 · agent. Data as of

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

The short answer

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

These issues and PRs concern how Bitwarden secrets are exposed as environment variables, specifically adding profile-scoped aliasing, key prefix/mapping support, and preserve-existing logic so plugins that read fixed env var names can receive the correct secrets across multiple profiles.

Open issues1

  • Issue#63088feat(secrets): key prefix/mapping support for Bitwarden Secrets Manager

Open PRs0

No open pull requests.

Fixes on record

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

  • #69058 feat(secrets): orchestrator-level preserve_existing + profile aliasing (#58073, #51447)

    merged to main

    files: agent/secret_sources/registry.py, tests/secret_sources/test_profile_secrets.py, website/docs/user-guide/secrets/index.md

1 PR closed without merging

From the close comments: other 1

  • #51616 fix(bitwarden): alias profile-scoped secrets to canonical env vars · other → #69058, #51447
Closed issues · 1
  • Closed#51447[BUG] Bitwarden profile-suffixed secrets never reach platform plugins that read a fixed env var (Telegram bot tokens silently fail for N-1 of N profiles)
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.39: 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
#69058
Closed issues
1
Attempts
1 PR closed without merging
Fix link checked
22 Jul 2026

For your agent

The same facts, typed.

cluster/51447.json
cluster/51447.md