GitHub Copilot

If you pay for GitHub Copilot, Empryo can use it. Claude Opus/Sonnet, GPT-4o, GPT-5.4, o-series, Gemini 2.5 Pro - all included in your Copilot subscription, no extra cost.

Setup

Reusing an IDE token instead

If you already signed in to Copilot in VS Code or JetBrains, that token works too:

jq -r '."github.com".oauth_token' ~/.config/github-copilot/apps.json
empryo --set-key copilot <token>

On Windows the path is ~\AppData\Local\github-copilot\apps.json. /keys inside the TUI does the same thing.

Which models your seat can actually run

Copilot's catalog lists every model GitHub sells, not the ones your seat may use. A plan with no premium allowance (Copilot Free, free_limited_copilot) routes only the base GPT line — gpt-4.1 and gpt-4o. Every other id answers:

The requested model is not supported.

Empryo rewrites that refusal with the reason and your seat SKU instead of passing it through, because GitHub's own message names neither. Claude, Gemini and the GPT-5 line need a paid Copilot plan.

Models whose terms you have not accepted yet (policy.state: disabled — most new SKUs) are accepted automatically on first use, the same call the official editor extensions make when you pick the model there.

Two wire formats

Copilot is the only provider whose endpoint varies per model, and Empryo follows the supported_endpoints its /models declares:

The Responses lane runs with store: false and encrypted reasoning replay, so a multi-step agent turn keeps its reasoning across tool calls. The mapping is cached on disk, so a --headless run resuming a saved model encodes the right wire before it opens any picker.

Reasoning effort comes from Copilot's own per-model ladder (/effort), which is not always the vendor's: Copilot's Claude SKUs take low|medium|high|max, gpt-5.6 adds none.

Usage and quota

Copilot bills a monthly allowance, not tokens, so the number that matters is how much of the month is left. GitHub reports it and Empryo shows it next to the relay subscription meters, in the same gauge:

Subscription · copilot
● pro                    octocat
  ▸ premium        [▰▰▰▰▰▱▱▱▱▱]   50%  ↺ 12d
    chat           [▰▱▱▱▱▱▱▱▱▱]   10%  ↺ 12d
    completions    [▱▱▱▱▱▱▱▱▱▱]    0%  ↺ 12d  editor only

Three allowances come back, and they are not equivalent:

That last row is why completions is drawn dimmed and marked *editor only*: a spent completions cap says nothing about whether your next turn will go through, so it must never read as "your plan is spent".

Where it shows, on every surface that can carry a plan meter:

The status bar carries one plan meter, and it follows the model: a copilot/* turn shows the Copilot allowance, a proxy/* turn shows the relay window. They are never both true at once, so they never compete for the slot.

Numbers are cached for five minutes; they only move monthly, and GitHub's Acceptable Use Policies discourage chatty automation against their servers.

Legal position

GitHub restructured its terms on 27 April 2026. What governs Copilot now depends on your seat:

Section J covers ownership of input and output, model training and the opt-out, disclaimers and indemnity. It places no restriction on which client you use. The constraints that do apply come from elsewhere in the agreement:

The official route

Since mid-2026 GitHub ships a supported path that did not exist when this integration was written:

If being on a sanctioned integration matters more to you than running Copilot models inside Empryo's own agent loop, that SDK is the route GitHub endorses. Empryo's provider talks to the chat endpoint directly instead, which is what lets Copilot models use the same tools, Genome and compaction as every other provider.

Re-verify if GitHub publishes updated terms after 2026-08-02.