Documentation Index
Fetch the complete documentation index at: https://docs.agent-vault.dev/llms.txt
Use this file to discover all available pages before exploring further.
Prerequisites
- A running Agent Vault instance (see installation guide)
- OpenCode installed
Quick start
Launch OpenCode withvault run. It wraps OpenCode with a vault-scoped session, pre-configures HTTPS_PROXY and CA trust so outbound HTTPS routes through Agent Vault transparently, and installs the Agent Vault skills so OpenCode knows how to discover services and raise proposals. If you haven’t logged in yet, you’ll be guided through setup automatically.
Target a specific vault
Try it out
Ask OpenCode to do something that requires an external API:“Fetch my recent Stripe charges”Here’s what happens — with zero pre-configuration:
- OpenCode calls
https://api.stripe.com/...directly.HTTPS_PROXYroutes the call through Agent Vault - Agent Vault returns a 403 — Stripe isn’t configured yet
- OpenCode reads the
proposal_hintand creates a proposal requesting Stripe access - OpenCode presents you with an approval link
- You click the link, paste your Stripe key, and click Allow
- OpenCode retries — Agent Vault injects your Stripe credentials at the proxy boundary and the request succeeds
You didn’t pre-configure anything. The agent discovered what it needed, asked for approval, and handled the rest.
Alternative: invite-based setup
If you can’t usevault run (e.g. you’re connecting a remote or cloud-hosted OpenCode instance), use the invite flow instead:
Next steps
Agent protocol
Full request lifecycle end-to-end.
Services
Pre-configure services you know the agent will need.