How-To Series · 9: Locking It Down
Hermes · Passwords & Logins
Say "log into GitHub" and the agent signs in for you. Passwords are encrypted on this machine and injected straight into the page, never seen by the model.
After this videoYou can sign in to sites by asking, while the agent keeps your passwords encrypted on this machine and out of the model's view.
Hermes has a built-in vault for the sites you sign into with a browser. The first time the agent reaches a sign-in page it has no login for, it asks you in a masked prompt. After that it just works. Passwords are encrypted under ~/.hermes/vault/, bound to a site origin, and injected into the page over the supervised session's CDP socket, so the model never sees them. Two-factor codes, saved payment cards, and address fills work the same way. If you already use 1Password or Bitwarden, Hermes picks up its website logins automatically through the op or bw CLI.
About these resources. Every command in this video comes from the Passwords & Logins doc.
New words here · Plain English
one sentence each · full glossaryVaultA secure store on this machine where Hermes keeps the logins, cards, and addresses it fills for you. Encrypted, scoped to your profile.
OriginThe exact site a saved login is bound to, like https://github.com. Hermes only fills a password on that exact site.
Masked promptA prompt that hides what you type, used for passwords and codes so they never enter the conversation.
Master passwordThe password that unlocks a password manager. Hermes hands it to the manager CLI once and keeps only the session token, never seeing the password.
Sources · What this video distills
1 docs page · every command below traces to itCommands shown · Copy and paste
each shows the source doc it came fromhermes vault listhermes vault addhermes vault rm <handle>hermes vault sources