anomalyco / anomalyco/opencode

GitHub Copilot models not appearing in /models after successful OAuth authentication

Open
#38,812 2 comments 13 reactions 1 assignee View on GitHub

@rekram1-node is already working on this.

Since Jul 25, 2026.

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

Description

Description

Description:

OS: Windows 11 (PowerShell)
OpenCode version: v1.18.5 (latest)
Steps to reproduce:

Run /connect in the TUI
Select "GitHub Copilot" and complete the device flow at github.com/login/device
Authentication succeeds — auth.json stores the OAuth token correctly
Run /models — only big-pickle appears, no copilot models listed
Tried re-authenticating, clearing auth.json, clearing models.json cache — same result
What I expected: Copilot models (e.g., copilot/claude-sonnet-4.6, copilot/gpt-5.3-codex) should appear in /models after authentication.

What happened: No copilot models appear in the model picker. Also tried setting "model": "copilot/claude-sonnet-4.6" directly in opencode.jsonc but it doesn't work (provider doesn't seem to initialize).

Evidence:

~/.local/share/opencode/auth.json contains valid OAuth token for github-copilot
~/.cache/opencode/models.json lists 27 copilot models under github-copilot key
The provider simply doesn't surface in the TUI
Additional context: GitHub Copilot subscription is active (Pro/Pro+). Authentication flow completes without errors. The issue appears to be that the copilot provider doesn't initialize or register in the TUI despite having valid credentials and model data.

Plugins

No response

OpenCode version

No response

Steps to reproduce

No response

Screenshot and/or share link

No response

Operating System

No response

Terminal

No response

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.