AI clients and agents

Argent for Aider

Aider takes an OpenAI-compatible base URL, so pointing it at Argent puts every call under policy. Here is what Argent governs, how it connects and what your team sets.

01 / AI CLIENTS AND AGENTS

What Argent does with Aider

Every call Aider 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 Aider 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
02 / AI CLIENTS AND AGENTS

How Aider connects

Aider reaches Argent in two ways.

  • Gateway base URL. Aider 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.
  • TLS-inspecting forward proxy. Aider 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.

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.

03 / AI CLIENTS AND AGENTS

What you configure

What your team sets in Aider. These are the settings the Argent console shows for this tool. Values in angle brackets come from your tenant.

  1. Gateway. export OPENAI_API_BASE=https://<gateway>/<route>/v1; export OPENAI_API_KEY=<Argent key>; aider --model openai/<model>. Equivalents: --openai-api-base, AIDER_OPENAI_API_BASE, openai-api-base: in.aider.conf.yml. Anthropic: ANTHROPIC_API_BASE (or ANTHROPIC_BASE_URL via LiteLLM) with an anthropic/ model.
  2. Proxy and CA. HTTPS_PROXY=http://proxy:8080 NO_PROXY=...; SSL_CERT_FILE=<ca bundle PEM> for model calls (as documented by LiteLLM). Keep verify-ssl true (default).
04 / AI CLIENTS AND AGENTS

Roll it out to every machine

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

05 / AI CLIENTS AND AGENTS

Check that it works

Send one request and look for the signed row. Run aider; 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