anomalyco / anomalyco/opencode

GitHub Copilot OAuth succeeds but provider is never registered ("Provider not found: github-copilot")

Open
#41,820 1 comment 2 reactions 1 assignee View on GitHub

@jlongster is already working on this.

Since Aug 11, 2026.

Dominant language
TypeScript
Stars
209k
Forks
27.5k
PR merge metrics
PR metrics pending

Description

Description

GitHub Copilot OAuth login appears to succeed, but OpenCode never registers the provider.

I successfully authenticate with GitHub Copilot using the device flow. After authorizing in the browser, OpenCode reports that the login completed and opencode providers list shows:

  • GitHub Copilot (oauth)

However, the provider cannot actually be used.

Running:

opencode models github-copilot

always returns:

Error: Provider not found: github-copilot

As a result, I cannot select or use GitHub Copilot even though the OAuth credentials are stored successfully.

I also verified that:

  • GitHub Copilot Student is active on my GitHub account.
  • The OAuth credentials exist in ~/.local/share/opencode/auth.json.
  • Re-authenticating multiple times does not fix the issue.
  • Upgrading OpenCode to the latest version does not fix the issue.
Plugins

None

OpenCode version

1.18.16

Steps to reproduce
  1. Install OpenCode 1.18.16 on macOS.
  2. Run OpenCode and choose GitHub Copilot as the provider.
  3. Complete the GitHub device OAuth flow successfully.
  4. Verify that opencode providers list shows "GitHub Copilot (oauth)".
  5. Run opencode models github-copilot.
  6. Observe the error: Provider not found: github-copilot.
  7. GitHub Copilot cannot be selected or used despite successful authentication.
Screenshot and/or share link

No response

Operating System

macOS Tahoe 26.5.1 (Apple Silicon)

Terminal

Apple terminal

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.