copilot CLI.
Prerequisites
Before setting up the integration, ensure you have:- Novageness CLI: Installed and logged in — see the CLI guide
- GitHub Copilot: VS Code extension or Copilot CLI
Setup with Novageness CLI
copilot CLI pick up the same hooks. Restart your terminal (and reload the VS Code window) after setup.
To remove the Novageness configuration:
Telemetry export
Setup also points Copilot Chat’s OpenTelemetry exporter at Novageness, so chat turns are reported alongside the activity the hooks capture. It writes five VS Code settings:
Reload the VS Code window afterwards — these are read once when the extension activates.
--clear removes these five settings and leaves the rest of your VS Code configuration untouched.
Telemetry export needs an HTTPS gateway. Where the gateway URL is plain HTTP, setup reports Gateway URL is not https; skipping Copilot telemetry export and configures everything else as normal, because the API key travels as a header on every turn.
captureContent is false, so the spans carry the shape of each turn rather than its text.Usage
Basic Usage
After configuration, every tool call Copilot makes — shell commands, file reads, file writes, edits — is intercepted by the Novageness hooks. Policies are checked before the tool runs, and matching actions (block, warn, audit, Slack approval) are enforced inline.Security Benefits
Using GitHub Copilot with Novageness Security AI Gateway provides:- Request Monitoring: All Copilot tool calls are logged and monitored
- Analytics: See which files and commands Copilot touches across your org
- Compliance: Ensure AI interactions meet your organization’s standards
- Audit Trail: Complete visibility into AI usage patterns
Novageness CLI
Install the CLI to set up and manage tools
Tool Policies
Configure security guardrails for AI tools