Skip to main content
kRouter
All integrations

Use GitHub Copilot with any AI provider

GitHub Copilot IDE with MITM. Pointing GitHub Copilot at kRouter gives it 100+ providers behind a single local endpoint — free tiers, subscriptions you already pay for, and paid APIs — with automatic failover when one runs out. GitHub Copilot is configured through MITM interception.

Why GitHub Copilot needs interception

GitHub Copilot has no setting for a custom endpoint — it talks to api.individual.githubcopilot.com and nowhere else. kRouter runs a local proxy with a trusted certificate that intercepts just that host, so the app keeps working exactly as before while its requests are routed to whichever provider you mapped. Nothing leaves your machine except the upstream call.

Setup

  1. Install kRouter

    Install globally, then start it in the background.

  2. Connect a provider

    Open the dashboard and connect whichever providers you want GitHub Copilot to reach.

  3. Point GitHub Copilot at kRouter

    Enable GitHub Copilot interception on the CLI Tools page and map each model to a provider.

Model slots GitHub Copilot exposes

Each slot maps to whichever provider model you choose, so GitHub Copilot keeps its own naming while the request goes wherever you point it.

  • GPT-5 mini
  • GPT-5.4 nano
  • Claude Haiku 4.5
  • GPT-4o
  • GPT-4.1

What changes for GitHub Copilot

Nothing about how you use GitHub Copilot changes — same interface, same workflow. What changes is where its requests land. Instead of being tied to one vendor and one bill, every request goes through your own machine first and out to whichever provider you mapped: a free tier for routine edits, a subscription you already pay for on the heavy turns, a paid API only when nothing else fits. When one account hits a limit, the next takes over mid-session rather than failing the task. And because the router runs locally, your prompts are not passing through a third-party service on the way.

Troubleshooting GitHub Copilot

GitHub Copilot shows a certificate warning

The local certificate has not been trusted yet. Run the trust step from the CLI Tools page — it installs kRouter's root certificate so the intercepted host validates normally.

Requests fail after MITM is turned off

Interception writes host entries while it runs. If it was stopped without cleaning up, those entries can point the app at a proxy that is no longer listening. kRouter detects this state and tells you how to clear it.

GitHub Copilot + kRouter FAQ

Can GitHub Copilot use providers other than its default?

Yes — that is the point of routing it through kRouter. kRouter presents one OpenAI-compatible endpoint that fans out to 100+ providers, so GitHub Copilot can reach any of them without knowing they exist.

How is GitHub Copilot pointed at kRouter?

Through MITM interception. GitHub Copilot has no endpoint setting, so kRouter intercepts its traffic locally instead.

Does routing GitHub Copilot through kRouter cost anything?

kRouter is free and MIT-licensed and adds nothing to your bill. What you pay is whatever the provider you routed to charges — which is often nothing, if you route to a free tier or a subscription you already hold.

What happens when a provider runs out of quota mid-session?

kRouter parks that account until its real reset time and fails over to the next one you have connected, so GitHub Copilot keeps working instead of erroring out mid-task.

Get GitHub Copilot routing in two minutes

kRouter is free, MIT-licensed, and runs entirely on your machine — no account, no proxy in the middle.

Install kRouter