Skip to content

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

Description

@Aquarius-Zhan

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. V2 TUI: simplify provider labels in prompt and model picker #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

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions