Secret Manager — Vault

Adds a HashiCorp Vault backend to the Secrets extension, so your API keys and tokens are stored in Vault instead of on your machine. Install it when your team already keeps credentials in Vault.

What you can do

• Store, view, and delete secrets in HashiCorp Vault, using Vault's KV v2 (key-value) secrets engine.
• Connect to a Vault server with its address, mount, and an access token — the token is verified when you connect and kept in your OS keychain, never in a project file.
• Let your other extensions read those secrets when they need them.

Getting started

1. Install and open the Secrets extension.
2. Choose + → Connect HashiCorp Vault and enter your Vault address, KV v2 mount, and token.
3. Add and reference secrets as usual; they're read from and written to Vault.

Requirements

• Desktop app.
• The Secrets extension for the sidebar and list.
• A reachable Vault server with a KV v2 mount and a token allowed to read, write, and delete on it.

Settings

Setting	Default	What it does
secrets.vault.defaultAddress	http://127.0.0.1:8200	Prefills the Vault address in the connect form.
secrets.vault.defaultMount	secret	Prefills the KV v2 mount in the connect form.