
Argent for Cline
Point Cline's provider at Argent and add Argent hooks: model calls and tool actions both come under policy. Here is what Argent governs, how it connects and what your team sets.
What Argent does with Cline
Every call Cline 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 Cline 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 Cline connects
Cline reaches Argent in two ways.
- Gateway base URL. Cline 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.
- Tool hooks. Before Cline 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 cline 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.
Proven with the real tool. Argent's team has driven Cline itself through a live Argent gateway and checked the signed records it produced.
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 Cline. These are the settings the Argent console shows for this tool. Values in angle brackets come from your tenant.
- Provider -> Argent. Cline settings -> API Provider: OpenAI Compatible -> Base URL = the Argent gateway route for your tenant, API Key = the Argent-issued agent key, Model ID = a routed model. For Anthropic: API Provider Anthropic -> Use custom base URL.
- Hooks. Cline's own docs warn a failed hook does not fail closed - the wrapper supplies that.
- CLI proxy/CA. Cline CLI: lowercase https_proxy, http_proxy, no_proxy and NODE_EXTRA_CA_CERTS; config in ~/.cline/ (providers in ~/.cline/data/settings/providers.json, CLINE_DATA_DIR to relocate).
Roll it out to every machine
Make it the only way Cline runs on company machines. These controls are documented by the platform each one belongs to (linked); pair them with the Argent settings above.
- Cline Teams/Enterprise remote configuration. Admin chooses the API provider, endpoint, models and headers for the org; members cannot select another provider or a personal Cline account, and the endpoint field shows a lock. For OpenAI-compatible/Anthropic providers members still supply their own keys. Vendor docs
- Cline MCP and feature controls. Control MCP servers, MCP marketplace and YOLO mode org-wide. Vendor docs
- Hooks distribution by MDM (macOS). Place the Argent hook wrappers at the hook locations, ~/.cline/hooks/ or ~/Documents/Cline/Hooks/, or set CLINE_HOOKS_DIR. 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. Run a Cline task; the Argent console live stream shows llm rows for the Argent agent key and signed shell.exec action rows.
argent doctor cline 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, OpenAI Codex IDE extension, 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