AI clients and agents

Argent for Devin for Terminal

Argent hooks check every Devin CLI prompt and tool action before it runs, and sign the decision. Here is what Argent checks, how the hooks connect and what your team sets.

01 / AI CLIENTS AND AGENTS

What Argent does with Devin for Terminal

Argent governs Devin for Terminal where the agent acts. Devin for Terminal sends its model calls through Cognition's own service, so Argent works through the tool's hooks: every prompt and every tool action is checked by Argent before it runs.

  • A named agent with a human owner. argent connect registers Devin for Terminal as an Argent agent under the signed-in person. Identity tethering
  • Prompts and actions checked first. Every tool call and every prompt submit goes to the Argent decision and data-loss scan before it runs. Agent permissions
  • Fails closed. If Argent cannot answer, the hook refuses the action, so an outage never turns into an open door.
  • A signed record of every decision. Allows and denies land in the signed audit ledger with the agent and owner named. One-click audit evidence
02 / AI CLIENTS AND AGENTS

How Devin for Terminal connects

Devin for Terminal reaches Argent in one way.

  • Tool hooks. Before Devin for Terminal 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 devin 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.

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 Devin for Terminal. These are the settings the Argent console shows for this tool. Values in angle brackets come from your tenant.

  1. Hooks. argent login && argent connect devin: ~/.config/devin/config.json hooks.PreToolUse (matcher *) and hooks.UserPromptSubmit.
04 / AI CLIENTS AND AGENTS

Roll it out to every machine

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

  • Devin CLI system policy file (Linux). Machine policy that pins enterprise_host/account_id for sign-in and can force outbound proxy settings; enterprise/team settings also cover model restrictions, MCP allowlist, permissions, sandbox and network rules. 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. Ask Devin for Terminal to run a harmless shell command. The Argent console live stream shows a signed hook decision for the prompt and one for the command, under the agent's name.

argent doctor devin checks the certificate pin, the keychain entry, the relay and the gateway's answer, without printing any secret.

Every hook decision also appears on the live stream with the agent's name and owner.