集成指南
clavitor + OpenClaw
Your OpenClaw agent manages credentials, rotates API keys, and completes 2FA — all from a single CLI call. Personal data stays sealed behind your fingerprint, face, or security key.
What your agent sees
共享字段
Your agent reads these to authenticate, deploy, and automate.
- API keys (GitHub, AWS, Stripe, OpenAI...)
- SSH 主机凭证
- 数据库连接字符串
- TOTP 种子——按需获取实时双因素认证码
- 服务账户密码
What your agent never sees
个人字段
使用您的指纹、面容或安全密钥在客户端进行加密。服务器仅存储密文。无密钥，则无法访问。
- 信用卡号及 CVV
- 护照及政府身份证件
- 恢复码及助记词
- 社会安全号码
- 银行账户详情
Connect in 60 seconds
1. 创建 Agent
Open your vault -> Agents -> Create. Name it and choose which entries it can access. Copy the setup token.
2. 初始化 CLI
$ echo "$CLAVITOR_TOKEN" | clavitor-cli init
3. Resolve credentials at startup
Replace hardcoded keys in your OpenClaw config with clavitor:// references, then render at launch:
{
"providers": {
"openrouter": { "apiKey": "clavitor://OpenRouter API/key" },
"fireworks": { "apiKey": "clavitor://Fireworks.ai/key" }
}
}$ clavitor-cli render openclaw.json | openclaw start --config -
You don't have to do anything
Once connected, your OpenClaw agent handles credentials automatically. It looks up what it needs, generates 2FA codes, and authenticates — you just describe what you want done.
"Deploy to production"
Your agent looks up server credentials, SSH key, and any required API tokens — then does the deployment.
clavitor-cli get "aws-production" --field secret_key clavitor-cli totp "aws" 283941
"Log in to GitHub and check the CI"
Your agent finds the credential, generates a live TOTP code, and completes the 2FA flow. No phone needed.
clavitor-cli get "github" --field password clavitor-cli totp "github" 847203
"Save this API key"
Your agent stores new credentials directly via clavitor-cli put. Sign up for a service, generate an API key — saved immediately, encrypted at the credential tier.
"Remember this for later"
License keys, server configs, migration plans — written via clavitor-cli memory put or clavitor-cli note put. Encrypted, searchable by embedding from any later agent session.
Multi-agent swarm support
Running a swarm of OpenClaw agents? Each gets its own agent token and scopes.
Deploy agent
Scoped to SSH keys, server creds, and API tokens
Billing agent
Scoped to Stripe, payment gateways, and invoicing
Dev agent
Scoped to GitHub, CI/CD, and database credentials
所有访问操作均会被记录
The audit log records which agent accessed which credential, when, and from where.
# TIME ACTION ENTRY ACTOR 2026-03-08 10:23:14 read github.com cli:claw-deploy 2026-03-08 10:23:15 totp github.com cli:claw-deploy 2026-03-08 11:45:02 read aws-production cli:claw-billing 2026-03-08 14:12:33 render - cli:claw-dev