AI clients and agents

Argent for Claude Code in VS Code and JetBrains

The Claude Code extensions share the CLI's settings, so one Argent setup governs the terminal and the IDE. Here is what Argent governs, how it connects and what your team sets.

Anthropic logo
01 / AI CLIENTS AND AGENTS

What Argent does with Claude Code in VS Code and JetBrains

Every call Claude Code in VS Code and JetBrains 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 Claude Code in VS Code and JetBrains 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
02 / AI CLIENTS AND AGENTS

How Claude Code in VS Code and JetBrains connect

Claude Code in VS Code and JetBrains reach Argent in two ways.

  • TLS-inspecting forward proxy. Claude Code in VS Code and JetBrains keep their normal provider settings and send their 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 Claude Code in VS Code and JetBrains run a tool or submit 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 claude-code 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.

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 Claude Code in VS Code and JetBrains. These are the settings the Argent console shows for this tool. Values in angle brackets come from your tenant.

  1. Connect the shared engine. Run argent login and argent connect claude-code once on the machine. VS Code and JetBrains extensions use ~/.claude/settings.json (env, hooks, apiKeyHelper) exactly like the CLI.
  2. VS Code only: extension env. Extension setting claudeCode.environmentVariables can hold extra env for the Claude process (Settings -> Extensions -> Claude Code). Not needed after connect; managed settings still win.
  3. Launch environment. VS Code inherits shell exports only when started from that shell (code.); put proxy/CA in settings.json env instead so GUI launches work.
  4. JetBrains. The plugin launches the installed claude command in the IDE terminal (Claude command setting picks the executable), so CLI settings and managed settings apply; no separate JetBrains policy store.
04 / AI CLIENTS AND AGENTS

Roll it out to every machine

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

  • Same Claude Code managed settings (files, macOS profile, HKLM policy). The extensions honor the same managed-settings sources (env, hooks, permissions, MCP, login lock). Deploy once; it covers CLI + VS Code + JetBrains. Vendor docs
  • VS Code enterprise policy: AllowedExtensions. Pin which extensions may run in VS Code (allow only approved publishers/extension IDs so unmanaged AI extensions cannot be installed). 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.

argent connect claude-code --emit-managed writes an admin-deployable managed-settings.json that pins the Argent key helper above user and project settings.

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. Same as CLI: argent doctor claude-code, then ask the extension a question and look for the signed llm row for the claude-code agent 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