
Argent for GitHub Copilot in JetBrains
Copilot in JetBrains IDEs uses the IDE proxy and the Argent certificate, so its calls land under policy. Here is what Argent governs, how it connects and what your team sets.
What Argent does with GitHub Copilot in JetBrains
Every call GitHub Copilot in 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 GitHub Copilot in 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
How GitHub Copilot in JetBrains connects
GitHub Copilot in JetBrains reaches Argent in one way.
- TLS-inspecting forward proxy. GitHub Copilot in JetBrains 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 user's own sign-in stays in place. GitHub Copilot in JetBrains signs in to GitHub / JetBrains with the user's token, which Argent never replaces. Turn on the tenant setting that lets Argent inspect these sign-in-bound hosts (Policy > 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.
What you configure
What your team sets in GitHub Copilot in JetBrains. These are the settings the Argent console shows for this tool. Values in angle brackets come from your tenant.
- IDE proxy. Settings -> Appearance & Behavior -> System Settings -> HTTP Proxy -> Manual proxy configuration -> HTTP: host/port of the Argent proxy (or loopback relay). The Copilot plugin uses this; there is no separate Copilot proxy key (Tools -> GitHub Copilot -> Network only adds a Kerberos SPN override).
- Tenant switch. Tenant needs Allow sign-in-bound vendors (Policy > Settings) on.
Roll it out to every machine
Make it the only way GitHub Copilot in JetBrains runs on company machines. These controls are documented by the platform each one belongs to (linked); pair them with the Argent settings above.
- Managed IDE configuration (JetBrains). Pre-seed the IDE HTTP proxy and trusted CA for every developer via the JetBrains managed-config / shared settings distribution, so the IDE starts already routed. Vendor docs
- GitHub org/enterprise Copilot policies and plan-subdomain firewall rule. Same as the VS Code entry: per-seat feature policies and blocking *.individual.githubcopilot.com. 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. Use Copilot Chat in the IDE; Argent console live stream should show an intercept tunnel to api.<plan>.githubcopilot.com and llm rows.
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: GitHub Copilot in VS Code, GitHub Copilot in Visual Studio, Cursor, Kiro IDE
- All integrations: Browse every AI client, provider, vault and identity source
Want this running on your own use cases?
Book a demo