GitHub Copilot Adapter

GitHub Copilot does not expose a native plugin API for telemetry interception. The FORG Copilot adapter uses a transparent local proxy that Copilot routes through, allowing FORG to observe token counts and model data without intercepting or storing any completions.

Note: This adapter requires routing Copilot traffic through a local proxy. Review the security considerations below before deploying in a production environment. Corporate Copilot accounts with custom routing policies may need IT approval.

Prerequisites

• GitHub Copilot (Individual, Business, or Enterprise) active subscription
• VS Code, JetBrains, or Neovim with Copilot plugin
• FORG CLI installed and activated
• Port 7248 available on localhost (proxy port)

Installation

npm install -g @forg-pro/copilot-adapter

Start the proxy:

forg-copilot-proxy start
# FORG Copilot proxy listening on 127.0.0.1:7248
# Forwarding to api.githubcopilot.com

Configure your editor to route Copilot through the proxy:

# VS Code settings.json
{
  "github.copilot.advanced": {
    "debug.overrideProxyUrl": "http://127.0.0.1:7248"
  }
}

# JetBrains (Settings → HTTP Proxy):
# Host: 127.0.0.1
# Port: 7248

Security considerations

• The proxy is TLS-terminating for localhost only — it does NOT intercept or decrypt prompt/completion content
• Only metadata headers (model, token counts) are observed; request/response bodies are forwarded unread
• The proxy runs as your local user account and cannot be accessed from other machines
• All forwarded traffic is re-encrypted before sending to GitHub's API endpoints

What gets captured

• Model used per request (gpt-4o, claude-3.5-sonnet, etc.)
• Token counts from Copilot's API response headers
• Latency from request to first byte
• Copilot API error codes

Known limitations

• GitHub Copilot Business/Enterprise with SAML SSO may reject proxy configuration
• Cost figures are estimated — Copilot is seat-licensed, so FORG uses list prices for cost calculation
• Inline completions generate high signal volume (100+ signals/hour typical)
• Auto-restart of the proxy process is not included in beta — add to your login items manually

Troubleshooting

# Check proxy status:
forg-copilot-proxy status

# View proxy logs:
forg-copilot-proxy logs

# Test the proxy connection:
curl -v http://127.0.0.1:7248/health