AI clients and agents

Argent for Amp

Amp's managed settings route its model calls to Argent, attributed to an agent with an owner. Here is what Argent governs, how it connects and what your team sets.

01 / AI CLIENTS AND AGENTS

What Argent does with Amp

Every call Amp 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 Amp 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 Amp connects

Amp reaches Argent in one way.

  • Gateway base URL. Amp 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.

03 / AI CLIENTS AND AGENTS

What you configure

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

  1. Proxy and CA. HTTP_PROXY / HTTPS_PROXY and NODE_EXTRA_CA_CERTS; amp.proxy in managed settings.
  2. Model routing. Personal settings -> Model Routing, workspace Model Routing, or amp config model-providers: Custom URL connection with Base URL, API format, API key, Model mapping. amp.url / AMP_URL change the Amp service URL, not the model provider.
04 / AI CLIENTS AND AGENTS

Roll it out to every machine

Make it the only way Amp runs on company machines. These controls are documented by the platform each one belongs to (linked); pair them with the Argent settings above.

  • Amp managed settings file (macOS). Admin-distributed settings including amp.url and amp.proxy (the workspace-delivered document cannot set these two keys). Vendor docs
  • Amp workspace managed settings and model connections. Admins provide workspace model connections and can forbid personal ones. 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

05 / AI CLIENTS AND AGENTS

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