Skip to main content

​
Install

Auto-detects your OS and architecture, downloads the latest release, and installs. Works for both fresh installs and upgrades. 
curl -fsSL https://get.agent-vault.dev | sh
Supports macOS (Intel + Apple Silicon) and Linux (x86_64 + ARM64).
On a successful install the script sends an anonymous ping (OS, architecture, version — nothing else) so we can count installs for the launch. Opt out by placing AGENT_VAULT_NO_TELEMETRY=1 in front of sh, not curl:
curl -fsSL https://get.agent-vault.dev | AGENT_VAULT_NO_TELEMETRY=1 sh
Verify the installation: 
agent-vault --help

​
Build from source

Prerequisites: Go 1.25+, Node.js 22+ 
git clone https://github.com/Infisical/agent-vault.git
cd agent-vault
make build
sudo mv agent-vault /usr/local/bin/

​
Start the server

agent-vault server
On first run, Agent Vault generates a random data encryption key (DEK) that encrypts all credentials at rest with AES-256-GCM. You can optionally set a master password to wrap the DEK (leave it empty for passwordless mode). The master password is never stored on disk. For non-interactive or automated environments, set the AGENT_VAULT_MASTER_PASSWORD environment variable or pass --password-stdin instead. Omit it entirely for passwordless mode. See environment variables for all options. To run in the background: 
agent-vault server -d
To stop a background server: 
agent-vault server stop

​
Register and log in

The first user to register becomes the instance owner with full admin privileges and is automatically granted admin on the default vault. Any CLI command that needs authentication will walk you through registration and login automatically — just run the command you want and follow the prompts. You can also register explicitly: 
agent-vault auth register
agent-vault auth login
Subsequent users can self-register via agent-vault auth register, the web registration page, or be invited to a vault by a vault admin.

​
Transparent proxy

HTTP/1.1 only today. Clients that negotiate HTTP/2 end-to-end will not proxy through this path — use the explicit /proxy endpoint instead.
Agent Vault exposes a second ingress as a transparent HTTPS_PROXY. This lets clients that respect the proxy environment variable (but can’t be pointed at a custom base URL) route through Agent Vault. The listener is TLS-encrypted (cert signed by the MITM CA) so the CONNECT handshake carrying session tokens is protected. It listens on port 14322 by default; pass --mitm-port 0 to disable, or a different port to change it: 
agent-vault server               # transparent proxy on 14322 (default)
agent-vault server --mitm-port 0 # disable
A software-backed root CA is created on first launch under ~/.agent-vault/ca/ (private key encrypted with the DEK). Clients must trust this root before the proxied TLS handshake will succeed. Fetch the root certificate from any machine that can reach the server: 
# From stdout (pipe into a trust-store installer)
agent-vault ca fetch > agent-vault-ca.pem

# Save to a file
agent-vault ca fetch -o /etc/ssl/certs/agent-vault-ca.pem

# Or with curl — the endpoint is public
curl -O http://localhost:14321/v1/mitm/ca.pem
Then install into the relevant trust store. For example, on macOS: 
agent-vault ca fetch | sudo security add-trusted-cert -d -r trustRoot \
    -k /Library/Keychains/System.keychain /dev/stdin
See the CLI reference for all agent-vault ca fetch flags.

​
Upgrade

Re-run the same install command — the script detects your existing installation, stops the running server, backs up your database, and installs the latest version: 
curl -fsSL https://get.agent-vault.dev | sh
On a successful upgrade the script sends the same anonymous ping (OS, architecture, version). Opt out by placing AGENT_VAULT_NO_TELEMETRY=1 in front of sh, not curl:
curl -fsSL https://get.agent-vault.dev | AGENT_VAULT_NO_TELEMETRY=1 sh
Restart the server afterward: 
agent-vault server
Database migrations run automatically on server startup — no manual steps required.

​
Verify a release (optional)

Every release includes SHA-256 checksums and a cosign signature for supply-chain security. No keys to manage — verification uses GitHub’s OIDC identity. 
# Download the checksums and signature bundle from the release page, then:

# 1. Verify the binary hasn't been tampered with
sha256sum --check checksums.txt

# 2. Verify the checksums were signed by the Infisical/agent-vault GitHub Actions workflow
cosign verify-blob \
  --bundle checksums.txt.bundle \
  --certificate-identity-regexp "github.com/Infisical/agent-vault" \
  --certificate-oidc-issuer "https://token.actions.githubusercontent.com" \
  checksums.txt