Guía de integración
clavitor + OpenAI Codex
Give your Codex agent access to credentials and 2FA codes — without exposing card numbers, passports, or recovery codes.
What your agent sees
Campos compartidos
Your agent reads these to help you code, deploy, and authenticate.
- API keys (GitHub, AWS, Stripe, OpenAI...)
- Credenciales de host SSH
- Cadenas de conexión de bases de datos
- Semillas TOTP — códigos 2FA en vivo bajo demanda
- Contraseñas de cuentas de servicio
What your agent never sees
Campos personales
Cifrado en el lado del cliente con su huella dactilar, rostro o clave de seguridad. El servidor almacena el texto cifrado. Sin clave, sin acceso.
- Números de tarjeta de crédito y CVV
- Pasaportes y documentos de identidad oficiales
- Códigos de recuperación y frases semilla
- Números de la seguridad social
- Datos de cuentas bancarias
Configuración
Create an agent, initialize the CLI on the machine where Codex runs.
1. Cree un agente
Open your vault -> Agents -> Create. Name it "Codex" and choose which entries it can access. Copy the setup token.
2. Inicialice la CLI
$ echo "$CLAVITOR_TOKEN" | clavitor-cli init
3. Run with the proxy
Point Codex at the Clavitor proxy. Credentials are injected into API calls transparently — no keys in the environment.
$ export HTTPS_PROXY=http://localhost:1983 $ codex
CLI and proxy — by design, no REST or MCP
The agent surface is capability only, never enumeration. Codex fetches credentials by name through the CLI or transparently through the HTTPS proxy. There is no agent-facing list, search, browse, or discover endpoint — that's a deliberate architectural choice, not a missing feature.
CLI — one value at a time
$ clavitor-cli get "GitHub" --field password $ clavitor-cli totp "GitHub" $ clavitor-cli render app.config.json
Proxy — transparent injection
$ export HTTPS_PROXY=http://localhost:1983
$ curl -H "Authorization: Bearer clavitor://OpenAI/key" \
https://api.openai.com/v1/modelsOne vault, multiple agents
Running agents on different projects? Create a separate agent for each.
Work agent
Scoped to GitHub, AWS, Jira, and Slack credentials
Personal agent
Scoped to email, social media, and cloud storage
Deploy agent
Scoped to SSH keys, database creds, and API tokens
Cada acceso queda registrado
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:codex 2026-03-08 10:23:15 totp github.com cli:codex 2026-03-08 11:45:02 read openai-prod proxy:codex 2026-03-08 14:12:33 read aws-production cli:deploy-agent