GitHub Copilot

If you pay for GitHub Copilot, memcode can run on it by reusing the GitHub login you already have. No API key.

Before you start

Sign in to the GitHub CLI:

gh auth login

memcode uses the token gh stores, or a GH_TOKEN or GITHUB_TOKEN in your environment. A classic personal access token (ghp_...) will not work. The Copilot API needs the OAuth token that gh auth login sets up.

Connect

memcode auth use copilot

Now run memcode as usual and it uses your Copilot subscription. To check, run memcode auth status, or run memcode auth for the picker.

Where the login comes from

memcode looks for a GitHub token in COPILOT_GITHUB_TOKEN, then GH_TOKEN, then GITHUB_TOKEN, and falls back to gh auth token. It exchanges that for a short-lived Copilot token per session. It only does this when you have selected the Copilot source, never behind your back.

If it stops working

If memcode says the token was rejected, run gh auth login again, and make sure GH_TOKEN isn't set to a classic ghp_ token.