
Argent for OpenAI Codex IDE extension
The Codex IDE extension reads the same config as the CLI, so Argent governs both from one setup. Here is what Argent governs, how it connects and what your team sets.
What Argent does with OpenAI Codex IDE extension
Every call OpenAI Codex IDE extension makes to a model goes through Argent first. Argent knows which agent sent it and which person owns that agent, checks it against your policy, and writes a signed record of what it decided.
- A named agent with a human owner. Each install of OpenAI Codex IDE extension gets its own Argent agent identity tied to an accountable person, so no call is anonymous. Identity tethering
- Only the models you allow. The agent can reach only the providers and models your policy names, and a request can be swapped to an approved model. Model control
- Sensitive data handled before it leaves. Prompts and replies are scanned for personal and secret data, then redacted or blocked as your policy says. Sensitive data redaction
- Spend priced and capped. Every request is priced and metered against budgets for the agent, its owner and the teams above them. AI spend caps
- A signed record you can replay. Each decision becomes a hash-chained, signed audit record, and requests are grouped into sessions you can replay. Session replay
- Tool actions checked before they run. Shell commands, file reads and writes, web fetches, MCP calls and prompt submits ask Argent first; if Argent cannot answer, the action is refused. Agent permissions
How OpenAI Codex IDE extension connects
OpenAI Codex IDE extension reaches Argent in two ways.
- TLS-inspecting forward proxy. OpenAI Codex IDE extension keeps its normal provider settings and sends its HTTPS traffic through the Argent forward proxy and trusts your Argent certificate; the exact settings are below. The proxy signs in with the agent's own key, so every call is attributed, then runs the same checks as the gateway. It opens only known AI hosts, and its certificate is limited to those hosts.
- Tool hooks. Before OpenAI Codex IDE extension runs a tool or submits a prompt, its hook asks Argent for a decision and a data-loss scan. If Argent cannot answer, the hook refuses.
One command does the setup. argent connect codex registers a per-tool agent under the signed-in person, keeps its key only in the OS keychain, and writes the tool's own config with a backup. --revert puts the old config back. Keyless agents explains why keys stay out of config files.
A small loopback relay holds the agent key and adds it to each proxy connection, so the key is never written into the tool's settings.
The same steps are in the Argent console under Integrations > AI Clients, and each agent's Connect tab gives the copy-paste values for your tenant.
What you configure
What your team sets in OpenAI Codex IDE extension. These are the settings the Argent console shows for this tool. Values in angle brackets come from your tenant.
- Connect the shared config.
argent login && argent connect codexwrites ~/.codex/config.toml, which the VS Code/Cursor/Windsurf Codex extension reads. - Proxy/CA for a GUI launch. GUI-launched VS Code does not inherit shell env; set HTTPS_PROXY / CODEX_CA_CERTIFICATE in the launcher environment (launchd plist, systemd user env, Windows system env) or start the IDE from the shell.
- VS Code-only settings. UI options live in editor settings under chatgpt.*; they are not config.toml keys.
Roll it out to every machine
Make it the only way OpenAI Codex IDE extension runs on company machines. These controls are documented by the platform each one belongs to (linked); pair them with the Argent settings above.
- Same Codex requirements.toml / MDM keys. Extension and CLI share agent configuration layers including model, sandbox, MCP; admin requirements apply to both. Vendor docs
Argent ships the push kit. For managed fleets the console produces per-MDM scripts (Jamf, Kandji, Intune-style, shell and PowerShell) with your tenant certificate and proxy address built in, plus a fleet setup script and certificate bundle. Your company CA can sign the Argent certificate, so managed machines already trust it.
Want to see which AI tools people already run before you push anything? Start with Shadow AI discovery in watch mode. Watch before you enforce
Check that it works
Send one request and look for the signed row. Ask the extension a question; look for the signed llm row for the argent-codex agent in the Argent console live stream.
argent doctor codex checks the certificate pin, the keychain entry, the relay and the gateway's answer, without printing any secret.
Every request also appears on the live stream with the agent's name and owner, and in the session view. Session replay
Where to go next
Keep going. Pages that cover the same ground from another angle.
- Use case: Securing AI coding agents
- Goals: See all AI in your company, Data loss prevention, Budget and token spend, Model control and routing, Agent identity and ownership
- Capabilities: Keyless agents, Prompt injection defense, Response screening, One-click audit evidence
- Related integrations: Claude Code in VS Code and JetBrains, Cline, Roo Code, Kilo Code
- All integrations: Browse every AI client, provider, vault and identity source
Want this running on your own use cases?
Book a demo