
Argent for GitHub Copilot in VS Code
Copilot Chat in VS Code runs through the Argent forward proxy while users keep their own Copilot sign-in. Here is what Argent governs, how it connects and what your team sets.
What Argent does with GitHub Copilot in VS Code
Every call GitHub Copilot in VS 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 GitHub Copilot in VS 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
How GitHub Copilot in VS Code connects
GitHub Copilot in VS Code reaches Argent in two ways.
- TLS-inspecting forward proxy. GitHub Copilot in VS 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.
- Gateway base URL. GitHub Copilot in VS 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.
The user's own sign-in stays in place. GitHub Copilot in VS Code signs in to GitHub / Microsoft 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).
Proven with the real tool. Argent's team has driven GitHub Copilot in VS Code 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 GitHub Copilot in VS Code. These are the settings the Argent console shows for this tool. Values in angle brackets come from your tenant.
- Tenant switches. Forward proxy on with Allow sign-in-bound vendors on in Policy > Settings (otherwise the proxy refuses api.*.githubcopilot.com), plus the unlisted-host passthrough setting on, or an allowlist covering github.com, api.github.com and VS Code's own hosts; without it the GitHub sign-in loops.
- Models and pricing. The model allowlist must include copilot:* (or the exact models), else Argent denies the model. Copilot models need price rows (provider copilot), else Argent refuses the model as unpriced.
- Point VS Code at the Argent forward proxy. Settings -> Application -> Proxy (http.proxy) = http://<proxy or loopback relay>:<port> (an http:// URL; Copilot does not support an https:// proxy URL). http.proxySupport MUST stay "override" (the VS Code default): "on" lets Copilot's own network stack skip the proxy. Keep http.proxyStrictSSL = true. The agent key authenticates to the proxy.
- Trust the Argent per-tenant intercept CA. Put the CA in the OS trust store (MDM/GPO in an enterprise). VS Code's fetch layer passes an explicit CA list (bundled roots plus the OS store) and ignores NODE_EXTRA_CA_CERTS unless http.systemCertificates is false. Do not set http.proxyStrictSSL=false.
- Reload Window. Run Developer: Reload Window after any proxy setting change: the chat WebSocket is long-lived and keeps its old route.
- Optional: BYOK through the gateway. Command Palette -> Chat: Manage Language Models -> Add Models -> Custom Endpoint; give the Argent gateway URL, an Argent-issued key and the model. Requires the org policy 'Bring Your Own Language Model Key in VS Code'.
Roll it out to every machine
Make it the only way GitHub Copilot in VS Code runs on company machines. These controls are documented by the platform each one belongs to (linked); pair them with the Argent settings above.
- VS Code ADMX policy (Intune / GPO) (Windows). Locks VS Code AI/Copilot behavior and extension sources. Vendor docs
- VS Code configuration profile (Jamf / Intune / Kandji) (macOS). Same policy IDs as Windows. Vendor docs
- VS Code policy file (Linux). Same policy IDs. Vendor docs
- GitHub enterprise / org Copilot policies. Which features and clients are allowed per seat: Copilot in IDE, Copilot CLI, cloud agent, third-party agents, MCP servers in Copilot, and BYOK. Disable 'Bring Your Own Language Model Key in VS Code' to stop local custom endpoints, or leave it on to let users point at Argent. Vendor docs
- Firewall rule keyed to the Copilot plan subdomain. Force corporate seats only: allow *.business.githubcopilot.com / *.enterprise.githubcopilot.com and BLOCK *.individual.githubcopilot.com so personal Copilot subscriptions cannot be used on the corporate network; then send the allowed hosts through the Argent proxy. 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. Chat in Copilot, then look in the Argent console live stream for signed allow rows with metering under the agent's name. A prompt with a test SSN should show a signed deny row.
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 JetBrains, 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