
Argent for Mistral Vibe CLI
Mistral Vibe's provider setting points at Argent, so its calls land under policy. Here is what Argent governs, how it connects and what your team sets.
What Argent does with Mistral Vibe CLI
Every call Mistral Vibe CLI 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 Mistral Vibe CLI 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
How Mistral Vibe CLI connects
Mistral Vibe CLI reaches Argent in one way.
- Gateway base URL. Mistral Vibe CLI points its model URL at your Argent route and uses an Argent agent key in place of the provider key. Argent removes that key and adds the real provider credential from your vault on the way out, so the tool never holds it.
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 Mistral Vibe CLI. These are the settings the Argent console shows for this tool. Values in angle brackets come from your tenant.
- Provider. ~/.vibe/config.toml or./.vibe/config.toml: [[providers]] api_base = "https://<gateway>/<route>/v1", backend, api_style, api_key_env_var.
Roll it out to every machine
Make it the only way Mistral Vibe CLI runs on company machines. These controls are documented by the platform each one belongs to (linked); pair them with the Argent settings above.
- Mistral admin-published Vibe configuration. Org/workspace admins publish TOML that the CLI fetches into memory (no local managed file). 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. Look for the llm row for the Argent key in the Argent console live stream.
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, OpenAI Codex CLI, Gemini CLI, GitHub Copilot CLI
- All integrations: Browse every AI client, provider, vault and identity source
Want this running on your own use cases?
Book a demo