agentos.guide › blog
Hermes agent bitwarden support lets your Agent OS keep its provider keys in one Bitwarden project instead of a plain-text file on every machine, and lets its browser sign in to sites with your Bitwarden logins.
This guide gives you a quick start, five prompts to paste into your agents, and a monthly routine for keeping the vault tidy.
Everything follows the official Hermes Bitwarden guide and the Passwords and Logins page.
If you would like help planning your own setup, book a free SEO strategy session with my team.
Your Agent OS runs Hermes, a gateway and a few profiles, and every one of them reads provider keys from the environment.
With Secrets Manager switched on, each of those processes fetches the keys from Bitwarden as it starts, after ~/.hermes/.env loads.
The only thing left in .env is BWS_ACCESS_TOKEN, the machine-account token.
The password manager side is separate: a signed-in bw CLI makes your website logins available to the agent's browser.
Members of the AI Profit Boardroom get the installable Agent OS, so the gateway and profiles are in place before you add the vault.
hermes secrets bitwarden setup
hermes secrets bitwarden status
hermes secrets bitwarden sync
hermes vault sources
Run these yourself, in your own terminal, not through the agent.
The first is the wizard: it installs bws if needed, takes the token with hidden input, asks for your region and project, test-fetches and switches the integration on.
The second confirms the token is valid. The third is a dry run that shows which keys would be applied.
The last lists your login sources, where Bitwarden appears once bw is installed and signed in.
Hermes strips BWS_ACCESS_TOKEN from every process the agent spawns: the terminal, execute_code, background processes and cron scripts.
terminal.env_passthrough can't put it back, and the docs say to run bws from your own shell.
So the prompts below have the agent plan, audit and use the vault, never handle the token.
Read ~/.hermes/.env and config.yaml for every profile.
List each provider key by variable NAME only, never the value.
Group them by profile and mark any name that appears in more than one profile.
Suggest a Bitwarden project layout and the exact secret names to create.
Secret names in Bitwarden become the variable names Hermes sets, so this list is your project blueprint.
🔥 Want the vault, profiles and prompts set up in a ready-made Agent OS?
Inside the AI Profit Boardroom you get step-by-step video trainings, the installable Agent OS with Hermes, four coaching calls a week and 3,600+ members running setups like this.
For each profile, list the credential variables that must differ between profiles,
such as chat bot tokens.
Propose alias names in the form NAME_PROFILE (for example TELEGRAM_BOT_TOKEN_MILLA)
and list any variable that should stay local under secrets.preserve_existing.
Profile aliasing is on by default, per the Hermes secrets overview, and only credential-shaped suffixes such as _TOKEN or _API_KEY qualify.
Show me the secrets.bitwarden block from config.yaml.
Confirm enabled is true, project_id looks like a UUID and server_url starts with https://
or is empty for US Cloud.
Tell me the values of override_existing and cache_ttl_seconds.
The defaults are override_existing: true and cache_ttl_seconds: 300.
Leave override on unless you want .env to win on that machine.
If the agent reports a project id that doesn't look like a UUID, Hermes would have rejected it anyway, so re-run the wizard and pick the project from the list.
Open the supplier portal and log in with my saved Bitwarden login for that site.
If the manager is locked, ask me to unlock it.
Stop at the dashboard and tell me what you see. Do not submit any orders.
The first time, Hermes asks for your master password in a masked prompt and keeps only the session token, for one session with a 30-minute idle timeout.
The agent uses browser_vault, documented in the Hermes browser guide, and a fill only goes through on the item's own site.
Every first Monday of the month, remind me to check the expiry date of my
Bitwarden machine-account token and to run hermes secrets bitwarden token
myself if it needs replacing.
hermes secrets bitwarden token checks the new token with Bitwarden before saving, so a bad paste never breaks .env.
🔥 Unsure how to split keys across your machines?
Talk it through with my team. Book a free SEO strategy session and bring your list of profiles.
Nothing stops. Hermes prints a one-line warning, adds a line naming the fix command and carries on with whatever .env already holds.
Unattended runs such as cron still load API keys, but a locked password manager reports unavailable_in_this_session, so unlock it in a live session before scheduling login jobs.
The wizard asks whether your machine account lives on US Cloud, EU Cloud or a self-hosted server.
Leaving server_url empty means the US default. EU accounts use https://vault.bitwarden.eu.
Self-hosted URLs must use https://; plain http:// is refused unless the server is localhost, because the token is sent to that address.
Pick the wrong region and startup reports the token as rejected, so check this first when a fresh setup fails.
If the box running your gateway has a patchy connection, switch on encrypted_cache.enabled.
Hermes then stores the last good fetch in an AES-GCM encrypted file and, with max_stale_seconds set, uses it only after network or timeout failures.
A rejected token never falls back to stale secrets, so a revoked token still stops working straight away.
Each profile in your Agent OS reads its own environment, and the secrets layer respects that.
Variables a profile declares for its child processes are forwarded with that profile's own value, and one profile's declared value never reaches another profile's children.
Provider credentials cannot be declared for passthrough at all, so the agent's tools never receive your model keys directly.
If a Bitwarden item stores an authenticator seed, Hermes generates the current code and enters it for you after the password.
The code is only generated on the login's own site, the same rule that governs the password fill.
For codes sent by text or email, a small prompt appears in your Agent OS, you type the code, and Hermes enters it into the page.
Passkeys and app approvals need nothing typed: the agent asks you to approve on your device and waits for the page to move on.
hermes model and look for the "(from Bitwarden)" label next to each provider key..env, never in config.yaml, and never store it as a secret inside the project, where Hermes skips it anyway.hermes secrets bitwarden token with a fresh one.hermes secrets bitwarden status on each machine..env that now come from Bitwarden.hermes vault sources and disable any login source you no longer use with hermes vault sources --disable bitwarden.Running 1Password rather than Bitwarden? See the Hermes 1Password guide.
If your Agent OS spans a laptop and a server, switch the Secrets Manager hook on: keys rotate in one place and the agent never sees the token.
On a single machine, sign in to bw for logins and keep keys where they are, which is what the docs advise too.
No. Hermes strips the Bitwarden token from the agent's terminal and scripts, so run setup, status and bws yourself in your own shell.
~/.hermes/.env, as BWS_ACCESS_TOKEN. Region, project and other settings live in config.yaml under secrets.bitwarden.
Use profile aliasing: a secret named NAME_PROFILE fills NAME for that profile, and secrets.preserve_existing pins any variable that must stay local.
No. Install the bw CLI and sign in; Hermes detects it and asks for your master password the first time it needs a login.
Yes, the hook runs at every start. Website logins from a locked manager are not available in unattended runs.
Run hermes vault sources --disable bitwarden, or set vault.bitwarden.enabled to false.
Run the wizard yourself, paste the five prompts, and if you want help, book a free strategy session or join the AI Profit Boardroom to set up hermes agent bitwarden.
About Julian
I'm Julian Goldie, an AI entrepreneur, SEO expert and the founder of the AI Profit Boardroom, which has 3,400+ members.
I help business owners scale with AI agents, automation and SEO.
My YouTube channel has 400,000+ subscribers, and I run Goldie Agency, a seven-figure SEO agency.
→ Hermes Agent Browser: What It Is, The Quick-Start And Where It Fits In An Agent OS
→ Migrate Hermes Agent To New Machine In Your Agent OS
→ Hermes Webapp: Run Your Whole Agent OS From A Browser Tab, With Five Copy-Paste Prompts
The installable system behind every guide on this site — dashboard, agents, memory and pipelines — updated as new tools land, with 3,400+ members and four coaching calls a week.
Join the AI Profit Boardroom →📺 Video notes + links to the tools 👉
🎥 Learn how I make these videos 👉