For agents that don’t have a chat interface or need raw environment variables, see Connect a custom agent.
Prerequisites
- A running Agent Vault server (installation)
- A user account with vault access (member or admin)
Option 1: Wrap with agent-vault vault run
The simplest approach for local development. Wraps your agent process with the environment variables it needs — no invite, no token management.
--vault to target a specific vault:
Option 2: Paste an invite prompt
For agents you can’t wrap withvault run (e.g. cloud-hosted agents, or when you want to paste into an existing session).
- Web UI
- CLI
What happens next
Once connected, the agent follows the Agent Vault protocol automatically:- Routes API requests through the Agent Vault proxy
- If a service isn’t configured yet, the agent creates a proposal and shares an approval link
- You click the link, provide any required credentials, and approve
- The agent retries and the request succeeds
For long-lived agents
Invited agents are instance-level entities with named identities that persist across sessions. You can manage vault access, rotate agent tokens, and revoke agents at any time. See Agents overview for the full lifecycle.Next steps
Agents overview
How agents work, vault access, and management commands.
Proposals
How agents request access to new services.