Issue Station
Sign In
Tools hereToolbox

hermes - 💡(How to fix) Fix Startup noise: repeated Bitwarden Secrets Manager warning when BWS_ACCESS_TOKEN is unset [1 pull requests]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Every time Hermes starts, if secrets.bitwarden.enabled: true (the default config template ships with this value) but BWS_ACCESS_TOKEN is not set, the warning prints three times to the terminal:

Bitwarden Secrets Manager: secrets.bitwarden.enabled is true but BWS_ACCESS_TOKEN is not set.  Run `hermes secrets bitwarden setup`.

This is noisy and confusing for users who don't use Bitwarden Secrets Manager.

Error Message

  • Silence if the user hasn't interacted with Bitwarden config -- only warn if the user explicitly set enabled: true (rather than it being the default).

Root Cause

Every time Hermes starts, if secrets.bitwarden.enabled: true (the default config template ships with this value) but BWS_ACCESS_TOKEN is not set, the warning prints three times to the terminal:

Bitwarden Secrets Manager: secrets.bitwarden.enabled is true but BWS_ACCESS_TOKEN is not set.  Run `hermes secrets bitwarden setup`.

This is noisy and confusing for users who don't use Bitwarden Secrets Manager.

Fix Action

Fixed

Code Example

Bitwarden Secrets Manager: secrets.bitwarden.enabled is true but BWS_ACCESS_TOKEN is not set.  Run `hermes secrets bitwarden setup`.
RAW_BUFFERClick to expand / collapse

Description

Every time Hermes starts, if secrets.bitwarden.enabled: true (the default config template ships with this value) but BWS_ACCESS_TOKEN is not set, the warning prints three times to the terminal:

Bitwarden Secrets Manager: secrets.bitwarden.enabled is true but BWS_ACCESS_TOKEN is not set.  Run `hermes secrets bitwarden setup`.

This is noisy and confusing for users who don't use Bitwarden Secrets Manager.

Steps to Reproduce

  1. Install Hermes Agent (fresh config.yaml has secrets.bitwarden.enabled: true)
  2. Do not set BWS_ACCESS_TOKEN
  3. Run hermes
  4. Observe the warning printed three times before the interactive session starts

Expected Behavior

Options (pick one or suggest an alternative):

  • Default to disabled -- ship secrets.bitwarden.enabled: false in the default config template so users only get the warning if they explicitly enabled it.
  • Print once instead of three times -- deduplicate the warning.
  • Silence if the user hasn't interacted with Bitwarden config -- only warn if the user explicitly set enabled: true (rather than it being the default).

Environment

  • Hermes Agent (latest)
  • Config: secrets.bitwarden section ships pre-enabled in default config template
  • Fix applied locally: hermes config set secrets.bitwarden.enabled false

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING