
Argent for OpenCode
OpenCode runs through Argent by proxy, hooks or base URL, with one argent connect command. Here is what Argent governs, how it connects and what your team sets.
What Argent does with OpenCode
Every call OpenCode 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 OpenCode 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 OpenCode connects
OpenCode reaches Argent in three ways.
- TLS-inspecting forward proxy. OpenCode 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.
- Tool hooks. Before OpenCode 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.
- Gateway base URL. OpenCode 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.
One command does the setup. argent connect opencode 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.
A small loopback relay holds the agent key and adds it to each proxy connection, so the key is never written into the tool's settings.
Proven with the real tool. Argent's team has driven OpenCode 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 OpenCode. These are the settings the Argent console shows for this tool. Values in angle brackets come from your tenant.
- Connect.
argent login && argent connect opencode. - Proxy and CA. HTTPS_PROXY=<proxy URL> (http:// with credentials also works), NO_PROXY=localhost,127.0.0.1 (the TUI talks to a local server), NODE_EXTRA_CA_CERTS=<Argent CA PEM>.
- Gateway alternative. opencode.json: provider.<id>.options.baseURL = Argent gateway route; for an unlisted OpenAI-compatible provider add provider.<id>.npm = "@ai-sdk/openai-compatible" and models; use @ai-sdk/openai for a Responses endpoint. OPENCODE_CONFIG names an extra config file.
Roll it out to every machine
Make it the only way OpenCode runs on company machines. These controls are documented by the platform each one belongs to (linked); pair them with the Argent settings above.
- OpenCode managed config directory (overrides user, OPENCODE_CONFIG, project and inline settings) (macOS). Pin provider baseURL, plugins (the Argent hook plugin), permissions and MCP so users cannot override them. Vendor docs
- OpenCode managed config directory (Linux). 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
Check that it works
Send one request and look for the signed row. argent doctor opencode; run opencode run 'say OK'; look for the llm row for the argent-opencode-<host> agent and hook rows 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