oc

Give your agents access,
not your secrets.

Open-source credential vault. Your agents call services and never see a key.

$curl -fsSL onecli.sh/install | sh
GitHub
OneCLI terminal flow: start the proxy, add credentials, and agents just work
API keys scattered everywhere.One encrypted vault.
Revoking access means hunting down keys.Revoke once, everywhere.
Agent acts without asking.Human approves before it's done. Define policies per action.

Works with any agent framework

Add OneCLI, remove the risk

OpenClawNanoClawIronClawDifyn8nOpenHands+ any framework
OneCLI architecture showing agents connecting through the OneCLI proxy to external services
Without OneCLI+ OneCLI
Secret handlingLLM sees raw API keysEncrypted vault,
agent never sees keys
SetupHardcode keys or env varsdocker run ghcr.io/onecli/onecli

How it works

1. Start OneCLI

$docker run -d -p 10254:10254 -p 10255:10255 -v onecli-data:/app/data ghcr.io/onecli/onecli
{
  "status": "running",
  "dashboard": "localhost:10254",
  "gateway": "localhost:10255"
}

2. Add credentials

$open http://localhost:10254
{
  "credentials": ["google", "github", "slack"]
}

3. Your agent just works

$curl -x http://localhost:10255 https://gmail.googleapis.com/gmail/v1/users/me/messages
{
  "messages": [
    { "from": "alice@acme.co", "subject": "Re: Q3 roadmap" },
    { "from": "github@noreply.com", "subject": "PR #42 merged" },
    { "from": "linear@linear.app", "subject": "ONC-118 assigned to you" }
  ]
}

What you get

Zero code changes

Set HTTPS_PROXY and your agent's existing HTTP calls get credentials injected. No SDK, no wrapper.

Encrypted vault

Credentials stored in local KMS or OneCLI Cloud. Never written to disk in plain text.

Full audit trail

See every API call, which agent made it, and when. Set limits, approve or deny in real-time.

One Docker container

Proxy, vault, and dashboard all run from a single docker run command.