OneCLI – Vault for AI Agents in Rust
Agents never see real keys, but Vault already does secret injection.
Local vault for AI agents. Use API keys without exposing raw stored keys to the model.
No read_secret tool means agents can use keys without ever reading them.
Developers building or using AI agents with API integrations
1Password CLI · AWS Credential Helper · Doppler
Agents never see real keys, but Vault already does secret injection.
Agents never touch raw tokens — you swap literal credentials for template variables and a proxy injects scoped secrets server-side while surfacing one‑click approval links to humans. It also fingerprints machines, uses SSH key auth, and tries to infer minimal OAuth scopes per request, which is a neat user-in-the-loop model. The obvious trade-off is centralizing trust in the proxy and the integration work for every provider, but the UX for human approvals and instant revocation is compelling.
Proxy tokens worthless if leaked, real keys never enter LLM context windows.
Vault proxy injects credentials at the network layer so agents never touch your keys.
Agents never see credentials — brokered access beats retrieval for prompt injection safety.
Agents can't leak secrets they never had—placeholder injection at the wire.