AI clients and agents

Argent for Qwen Code

Qwen Code's endpoint and proxy settings route its calls through Argent for checks and signed records. Here is what Argent governs, how it connects and what your team sets.

Alibaba Qwen logo
01 / AI CLIENTS AND AGENTS

What Argent does with Qwen Code

Every call Qwen Code 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 Qwen Code 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 Qwen Code connects

Qwen Code reaches Argent in two ways.

  • Gateway base URL. Qwen Code 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. Qwen Code 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 Qwen Code. These are the settings the Argent console shows for this tool. Values in angle brackets come from your tenant.

  1. Endpoint and proxy. settings.json modelProviders[providerId][].baseUrl = Argent gateway route (or --openai-base-url / OPENAI_BASE_URL); top-level proxy or --proxy for the network proxy.
04 / AI CLIENTS AND AGENTS

Roll it out to every machine

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

  • System settings that override user settings (Linux). Administrator-overriding settings. Vendor docs
  • System settings (macOS). Same. 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