Secure GitHub Copilot with AxSentinel

Copilot sees your code. AxSentinel makes sure it doesn't see your secrets.

The Problem

GitHub Copilot sends surrounding code context to GitHub's AI models for completions and chat. If your open files contain hardcoded API keys, database credentials, or customer data, Copilot may include them in its context window. GitHub's Copilot for Business offers some data protections, but the context still leaves your machine.

The Solution

Route Copilot's traffic through the AxSentinel proxy using system-level HTTP proxy settings. Every request is scanned before it reaches GitHub's servers. This works alongside Copilot for Business — AxSentinel adds a local scanning layer that catches secrets before they ever leave your network.

Get Started in Minutes

1

Start the AxSentinel proxy

Run the proxy on port 8990.

~/.axsentinel/sentinel --proxy --port 8990
2

Set system proxy environment variables

Copilot doesn't support custom API endpoints, so you need to use system-level proxy settings. Add these to your shell profile.

export HTTP_PROXY=http://localhost:8990
export HTTPS_PROXY=http://localhost:8990
3

Verify in VS Code

Open VS Code, trigger a Copilot completion, and check the proxy terminal for scanning activity.

Key Features

System proxy approach

Works with Copilot's existing infrastructure — no GitHub configuration changes needed.

Complements Copilot for Business

Copilot for Business handles server-side retention. AxSentinel handles client-side scanning before data leaves your machine.

Scans completions and chat

Both inline completions and Copilot Chat requests are intercepted and scanned.

Per-developer control

Each developer can choose block, redact, or prompt mode independently.

Frequently Asked Questions

Does this break Copilot?
No. Clean requests pass through transparently. Copilot works normally — only requests containing secrets are blocked or redacted.
Do I still need Copilot for Business?
Yes, if you want server-side data protections from GitHub. AxSentinel is a complementary client-side layer.
Does the system proxy affect other traffic?
Yes — HTTP_PROXY affects all HTTP traffic from that shell session. You can scope it to specific terminals or use the VS Code extension instead.
Can I use the VS Code extension instead?
The VS Code extension manages its own proxy. However, Copilot uses its own connection path, so system proxy settings are more reliable for Copilot specifically.

Ready to secure your AI workflow?

Free tier includes regex scanning for unlimited developers. Pro adds ML-powered detection and the compliance dashboard.