Skip to main content

Server configuration

Email SMTP configuration

Configure SMTP to enable Agent Vault to send emails for verification codes, vault invites, and notifications.
To verify SMTP is working, run agent-vault email test. It sends a test email to the owner’s address. See the Configure Email SMTP guide for step-by-step setup instructions for popular providers like SendGrid, AWS SES, Resend, and more.

Infisical credential store

Setting INFISICAL_URL enables Infisical-backed vaults: Agent Vault polls Infisical and caches the encrypted snapshot locally. Local mutations are rejected. See Credential stores. Supply env vars for one auth method. Detection picks the first complete group in priority order: Universal → Kubernetes → AWS IAM → GCP IAM → GCP ID Token → LDAP. GCP IAM and GCP ID Token share INFISICAL_GCP_AUTH_IDENTITY_ID; setting INFISICAL_GCP_IAM_SERVICE_ACCOUNT_KEY_FILE_PATH alongside selects IAM, otherwise ID Token (which pulls a JWT from the GCP metadata server).
The Infisical machine identity should have read-only access. Agent Vault never writes back, and a read-only identity caps blast radius if the broker is compromised.

Telemetry

Agent Vault collects anonymous usage telemetry to help improve the product. No credential values, request payloads, or secret data are ever included. Events capture command invocations and feature usage with the authenticated user’s email for company attribution.