Repository navigation
Closed as not planned
Labels
P2Normal backlog priority with limited blast radius.Normal backlog priority with limited blast radius.clawsweeper:fix-shape-clearClawSweeper found a clear likely implementation shape for this issue.ClawSweeper found a clear likely implementation shape for this issue.clawsweeper:needs-maintainer-reviewClawSweeper marked this issue as needing maintainer review before automation.ClawSweeper marked this issue as needing maintainer review before automation.clawsweeper:needs-product-decisionClawSweeper marked this issue as needing a product or behavior decision.ClawSweeper 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 does not recommend queueing a new automated fix PR for this issue.clawsweeper:source-reproClawSweeper found a high-confidence source-level issue reproduction.ClawSweeper found a high-confidence source-level issue reproduction.impact:auth-providerAuth, provider routing, model choice, or SecretRef resolution may break.Auth, provider routing, model choice, or SecretRef resolution may break.issue-rating: 🦞 diamond lobsterVery strong issue quality with high-confidence source-level or clear reproduction.Very strong issue quality with high-confidence source-level or clear reproduction.
Description
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.
Reacted by clawsweeper
Metadata
Metadata
Assignees
Labels
P2Normal backlog priority with limited blast radius.Normal backlog priority with limited blast radius.clawsweeper:fix-shape-clearClawSweeper found a clear likely implementation shape for this issue.ClawSweeper found a clear likely implementation shape for this issue.clawsweeper:needs-maintainer-reviewClawSweeper marked this issue as needing maintainer review before automation.ClawSweeper marked this issue as needing maintainer review before automation.clawsweeper:needs-product-decisionClawSweeper marked this issue as needing a product or behavior decision.ClawSweeper 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 does not recommend queueing a new automated fix PR for this issue.clawsweeper:source-reproClawSweeper found a high-confidence source-level issue reproduction.ClawSweeper found a high-confidence source-level issue reproduction.impact:auth-providerAuth, provider routing, model choice, or SecretRef resolution may break.Auth, provider routing, model choice, or SecretRef resolution may break.issue-rating: 🦞 diamond lobsterVery strong issue quality with high-confidence source-level or clear reproduction.Very strong issue quality with high-confidence source-level or clear reproduction.
Type
Fields
Priority
None yet
Activity
clawsweeper commentedon Jun 10, 2026
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:
extensions/opencode/index.ts:36, e3a6da0f5181)extensions/opencode-go/index.ts:116, e3a6da0f5181)docs/providers/opencode.md. (docs/providers/opencode.md:24, e3a6da0f5181)docs/providers/opencode.md. (docs/providers/opencode.md:12, 7761e7626ffe)Likely related people:
extensions/opencode/index.ts,extensions/opencode-go/index.ts,extensions/opencode-go/provider-catalog.ts)extensions/opencode-go/provider-catalog.ts,docs/providers/opencode.md)extensions/opencode/index.ts,docs/providers/opencode.md)Codex review notes: model internal, reasoning high; reviewed against e3a6da0f5181.
monish-rgb commentedon Jun 11, 2026
Hi I would like to work on this issue