Skip to content

Docs feedback: /providers/opencode #91930

Closed as not planned
Closed as not planned

Description

@rp7181120-star

Page: /providers/opencode
URL: https://docs.openclaw.ai/providers/opencode

Missing or confusing:
OpenClaw Version: 2026.6.5

Issue:
Zen API returns full model catalog including deepseek-v4-flash-free.

curl -s https://opencode.ai/zen/v1/models

shows dozens of models.

However:

openclaw models list --all --provider opencode

returns only:

opencode/claude-opus-4-6

Steps attempted:

  • Deleted ~/.openclaw/cache
  • Restarted gateway
  • Re-authenticated with:
    openclaw models auth login --provider opencode --force --set-default
  • Re-ran onboarding

Result:
Only Claude is imported into the local registry.
Zen catalog models such as deepseek-v4-flash-free are missing despite being present in the live API response.

Activity

  1. clawsweeper commented on Jun 10, 2026

    @clawsweeper
    Contributor

    Thanks for the context here. I swept through the related work, and this is now duplicate or superseded.

    The report is valid, but the newer canonical issue captures the same missing OpenCode Zen catalog, live endpoint evidence, user impact, proposed plugin boundary, and unresolved curated-versus-live policy decision in greater detail.

    Canonical path: Keep #92479 as the single tracker and resolve there the provider-owned offline seed, live discovery policy, metadata enrichment, and regression coverage for Zen.

    So I’m closing this here and keeping the remaining discussion on #92479.

    Review details

    Best possible solution:

    Keep #92479 as the single tracker and resolve there the provider-owned offline seed, live discovery policy, metadata enrichment, and regression coverage for Zen.

    Do we have a high-confidence way to reproduce the issue?

    Yes. The live Zen endpoint returns the reported model, while current main’s Zen plugin lacks the catalog and dynamic-resolution hooks implemented by the sibling Go provider.

    Is this the best way to solve the issue?

    Yes. Consolidating this report into the newer canonical issue is the best tracking approach because it preserves the same reproduction, root cause, implementation boundary, and remaining product decision without splitting discussion.

    Security review:

    Security review: This issue has no proposed patch requiring a security or supply-chain review.

    AGENTS.md: found and applied where relevant.

    What I checked:

    • Canonical issue: The open canonical issue documents the same absent Zen provider catalog, the 48-row live endpoint, manual registration requirement, sibling OpenCode Go implementation, and product-policy questions.
    • Missing Zen catalog hook: Current main registers OpenCode Zen authentication and runtime policy but no catalog, dynamic model resolver, or catalog augmentation hook. (extensions/opencode/index.ts:36, e3a6da0f5181)
    • Sibling provider contract: OpenCode Go implements static/live provider catalog loading, dynamic resolution, and catalog augmentation, demonstrating the existing provider-owned seam relevant to the canonical issue. (extensions/opencode-go/index.ts:116, e3a6da0f5181)
    • Documented multi-model behavior: The provider documentation describes Zen as a curated multi-model proxy and instructs users to verify available models through the provider-scoped list command. Public docs: docs/providers/opencode.md. (docs/providers/opencode.md:24, e3a6da0f5181)
    • Live upstream reproduction: The live Zen endpoint returned 48 model rows, including the specifically reported deepseek-v4-flash-free model.
    • Feature history: Repository history connects the unified OpenCode integration to commit 7761e76 and shows subsequent OpenCode provider work by the listed routing candidates. Public docs: docs/providers/opencode.md. (docs/providers/opencode.md:12, 7761e7626ffe)

    Likely related people:

    • steipete: Authored the provider-plugin migration and multiple recent OpenCode routing, catalog, base-URL, and model updates that define the current ownership boundary. (role: recent area contributor; confidence: high; commits: 8e2a1d0941c7, c97c5a5aff2e, 390be8138f28; files: extensions/opencode/index.ts, extensions/opencode-go/index.ts, extensions/opencode-go/provider-catalog.ts)
    • ImLukeF: Introduced OpenCode Go support and the unified OpenCode Zen/Go documentation, establishing the sibling catalog structure relevant to this report. (role: feature introducer; confidence: high; commits: 7761e7626ffe; files: extensions/opencode-go/provider-catalog.ts, docs/providers/opencode.md)
    • vincentkoc: Contributed OpenCode provider helpers and documentation maintenance and was explicitly mentioned on this issue’s timeline. (role: recent area contributor; confidence: medium; commits: 66701d5a1e16, 7de76ac6e395, ba5544816352; files: extensions/opencode/index.ts, docs/providers/opencode.md)

    Codex review notes: model internal, reasoning high; reviewed against e3a6da0f5181.

  2. added
    P2Normal backlog priority with limited blast radius.
    impact:auth-providerAuth, provider routing, model choice, or SecretRef resolution may break.
    issue-rating: 🦞 diamond lobsterVery strong issue quality with high-confidence source-level or clear reproduction.
    clawsweeper:source-reproClawSweeper found a high-confidence source-level issue reproduction.
    clawsweeper:queueable-fixClawSweeper marked this issue as an existing queue_fix_pr work candidate.
    clawsweeper:fix-shape-clearClawSweeper found a clear likely implementation shape for this issue.
    clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.
    clawsweeper:needs-maintainer-reviewClawSweeper marked this issue as needing maintainer review before automation.
    clawsweeper:needs-product-decisionClawSweeper marked this issue as needing a product or behavior decision.
    and removed
    clawsweeper:fix-shape-clearClawSweeper found a clear likely implementation shape for this issue.
    clawsweeper:queueable-fixClawSweeper marked this issue as an existing queue_fix_pr work candidate.
    on Jun 10, 2026
  3. monish-rgb commented on Jun 11, 2026

    @monish-rgb

    Hi I would like to work on this issue

  4. locked as resolved and limited conversation to collaborators on Jun 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Normal backlog priority with limited blast radius.clawsweeper:fix-shape-clearClawSweeper found a clear likely implementation shape for this issue.clawsweeper:needs-maintainer-reviewClawSweeper marked this issue as needing maintainer review before automation.clawsweeper:needs-product-decisionClawSweeper marked this issue as needing a product or behavior decision.clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.clawsweeper:source-reproClawSweeper found a high-confidence source-level issue reproduction.impact:auth-providerAuth, provider routing, model choice, or SecretRef resolution may break.issue-rating: 🦞 diamond lobsterVery strong issue quality with high-confidence source-level or clear reproduction.

    Type

    No type

    Fields

    Priority

    None yet

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions