anomalyco / anomalyco/opencode

Why was the per-model provider mapping removed from the OpenCode Go page, and can it be restored?

Open
#39,857 3 comments 0 reactions 1 assignee View on GitHub

@Hona is already working on this.

Since Jul 31, 2026.

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

Description

Question

Why was the per-model provider mapping removed from the OpenCode Go page,
and will provider/upstream information be restored or exposed again on the
website, in /zen/go/v1/models, and in the TUI model picker?

Context
  • Until 2026-07-16, opencode.ai/go displayed each Go model's provider source.
    For example, GLM-5.2 was listed as "DeepInfra, Fireworks AI, Z.ai" and
    DeepSeek V4 Flash as "DeepSeek".
  • The mapping was hardcoded in packages/console/app/src/routes/go/index.tsx
    as models = [{ name, provider }] and was removed by commit 5121352
    ("go: grok 4.5 and kimi k3", 2026-07-16). The page now shows model names
    and request limits only.
  • The public API https://opencode.ai/zen/go/v1/models also returns model IDs
    without any provider field, and the Go docs page only lists models + endpoints.
Specific questions
  1. Was removing the provider column intentional? If so, why?
  2. Do Go models actually route through the providers that were previously
    listed (e.g. DeepInfra / Fireworks AI / Z.AI for GLM-5.2), or are all Go
    requests now served by one internal gateway? If they are still served by
    those upstreams, why hide them?
  3. #36270 (V2 TUI) notes subscription models do not expose their backing
    provider as structured metadata and suggests adding an
    upstreamProviderID field. Is this planned?
  4. Will provider information be restored on the website, in
    /zen/go/v1/models, and in the TUI model picker?
Environment
  • OpenCode version: 1.18.9
  • OS: Windows 11
  • Terminal: Windows Terminal
References

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.