openclaw - ✅(Solved) Fix [Bug]: OpenCode Go catalog lists opencode-go/kimi-k2.6 in docs but OpenClaw 2026.4.21 resolves it as configured,missing and runtime model_not_found [1 pull requests, 1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#70282Fetched 2026-04-23 07:26:46
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Timeline (top)
closed ×1commented ×1cross-referenced ×1labeled ×1

OpenCode Go catalog lists opencode-go/kimi-k2.6 in docs but OpenClaw 2026.4.21 resolves it as configured,missing and runtime model_not_found

Error Message

Observed openclaw models list --provider opencode-go output:

🦞 OpenClaw 2026.4.21 (f788c88)

Model Input Ctx Local Auth Tags opencode-go/glm-5.1 text 200k no yes configured opencode-go/glm-5 text 200k no yes configured opencode-go/kimi-k2.5 text+image 256k no yes configured opencode-go/kimi-k2.6 - - - - configured,missing opencode-go/mimo-v2-pro text 1024k no yes configured opencode-go/mimo-v2-omni text+image 256k no yes configured opencode-go/minimax-m2.7 text 200k no yes configured opencode-go/minimax-m2.5 text 200k no yes configured opencode-go/qwen3.6-plus text+image 256k no yes configured opencode-go/qwen3.5-plus text+image 256k no yes configured opencode-go/mimo-v2.5-pro - - - - configured,missing opencode-go/mimo-v2.5 - - - - configured,missing

Observed runtime logs:

[diagnostic] lane task error: lane=main durationMs=12389 error="FailoverError: Unknown model: opencode-go/kimi-k2.6" [diagnostic] lane task error: lane=session:agent:main:main durationMs=12392 error="FailoverError: Unknown model: opencode-go/kimi-k2.6" [model-fallback/decision] model fallback decision: decision=candidate_failed requested=opencode-go/kimi-k2.6 candidate=opencode-go/kimi-k2.6 reason=model_not_found next=openai-codex/gpt-5.4 detail=Unknown model: opencode-go/kimi-k2.6 [model-fallback] Model "opencode-go/kimi-k2.6" not found. Fell back to "openai-codex/gpt-5.4".

Relevant docs observed at report time stated opencode-go/kimi-k2.6 is supported in the OpenCode Go catalog.

Impact and severity

Affected users/systems/channels: users on OpenClaw 2026.4.21 configuring OpenCode Go models, specifically opencode-go/kimi-k2.6
Severity: blocks workflow for this model
Frequency: always, based on repeated observed lookups/runtime attempts in this environment
Consequence: requests for opencode-go/kimi-k2.6 do not route and instead fail over to another model, which can change behavior and provider unexpectedly

Additional information The same mismatch was also observed for:

opencode-go/mimo-v2.5-pro
opencode-go/mimo-v2.5

No observed evidence in this report establishes whether a newer OpenClaw version fixes the issue.

Root Cause

OpenCode Go catalog lists opencode-go/kimi-k2.6 in docs but OpenClaw 2026.4.21 resolves it as configured,missing and runtime model_not_found

Fix Action

Fixed

PR fix notes

PR #70329: test(opencode-go): lock Pi catalog coverage

Description (problem / solution / changelog)

Summary

  • Problem: Certain OpenCode Go models (e.g., opencode-go/kimi-k2.6) were marked as configured,missing and failed at runtime with model_not_found.
  • Why it matters: Breaks routing for valid models listed in docs, causing silent fallback to other providers and inconsistent behavior.
  • What changed: Introduced a static baseline catalog for the opencode-go provider and added missing models.
  • What did NOT change (scope boundary): No changes to provider routing logic, external API calls, or dynamic catalog behavior.

Change Type (select all)

  • Bug fix

Scope (select all touched areas)

  • Integrations

Linked Issue/PR

  • Closes #70282
  • This PR fixes a bug or regression

Root Cause

  • Root cause:The provider relied on a dynamic catalog that did not yet include newer models. Because OpenClaw performs strict validation at the provider registration boundary, these models were flagged as missing despite being valid API targets. By introducing a staticCatalog, we provide a local source of truth that the registry can fall back on before dynamic sync completes.
  • Missing detection / guardrail: No fallback or baseline catalog to recognize valid but not-yet-synced models.
  • Contributing context: Docs listed models ahead of catalog sync, creating a mismatch between documentation and runtime availability.

Changes

  • Added extensions/opencode-go/models.ts

    • Introduced a static catalog for baseline model registration
  • Added support for:

    • opencode-go/kimi-k2.6 (256k, text + image)
    • opencode-go/mimo-v2.5-pro (1M context)
    • opencode-go/mimo-v2.5 (1M context)
  • Updated extensions/opencode-go/index.ts

    • Wired provider to use staticCatalog during initialization

Regression Test Plan

  • Coverage level that should have caught this:

    • Seam / integration test
  • Target test or file:

    • extensions/opencode-go
  • Scenario the test should lock in:

    • Models present in docs but missing from dynamic catalog should still resolve and be usable
  • Why this is the smallest reliable guardrail:

    • Failure occurs at provider registration boundary, not isolated logic
  • Existing test that already covers this (if any):

    • Partial coverage for provider mapping
  • If no new test is added, why not:

    • Existing extension tests validate catalog usage and model registration

User-visible / Behavior Changes

  • Previously failing models (kimi-k2.6, mimo-v2.5*) now:
    • Appear as configured
    • Resolve correctly at runtime
  • Eliminates unexpected fallback to other providers

Diagram


Before:
Model configured -> lookup fails -> model_not_found -> fallback to other provider

After:
Model configured -> static catalog match -> valid routing -> correct execution

## Security Impact (required)

- New permissions/capabilities? No  
- Secrets/tokens handling changed? No  
- New/changed network calls? No  
- Command/tool execution surface changed? No  
- Data access scope changed? No  

---

## Repro + Verification

### Environment

- OS: Arch Linux x86_64 
- Kernel: 6.19.11-arch1-1
- Runtime/container: Node v22 .22.2
- Model/provider: opencode-go  
- Relevant config: OPENCODE_API_KEY set, model configured  

### Steps

1. Configure `opencode-go/kimi-k2.6`  
2. Run `openclaw models list --provider opencode-go`  
3. Attempt inference using the model  

### Expected

- Model appears as `configured`  
- Requests route successfully  

### Actual (before fix)

- Model shows `configured,missing`  
- Runtime error: `Unknown model`  

---

## Evidence

- [x] Reproduced `configured,missing` before fix  
- [x] Verified model resolution after fix  
- [x] Extension tests passing  

---

## Human Verification (required)

- Verified scenarios:
 - Model listing shows correct status  
 - Requests route without fallback  

- Edge cases checked:
 - Multiple new models missing from catalog  
 - Mixed valid + missing models  

- What you did **not** verify:
 - All provider/model combinations  
 - Future catalog sync behavior  

---

## Review Conversations

- [x] I replied to or resolved every bot review conversation I addressed in this PR.  
- [x] I left unresolved only the conversations that still need reviewer or maintainer judgment.  

---

## Compatibility / Migration

- Backward compatible? Yes  
- Config/env changes? No  
- Migration needed? No  

---

## Risks and Mitigations

- Risk:
 - Static catalog may drift from upstream dynamic catalog  

- Mitigation:
 - Static catalog acts only as baseline; dynamic catalog still applies when available

## Changed files

- `extensions/opencode-go/index.test.ts` (modified, +50/-0)

Code Example

Observed openclaw models list --provider opencode-go output:

🦞 OpenClaw 2026.4.21 (f788c88)

Model Input Ctx Local Auth Tags
opencode-go/glm-5.1 text 200k no yes configured
opencode-go/glm-5 text 200k no yes configured
opencode-go/kimi-k2.5 text+image 256k no yes configured
opencode-go/kimi-k2.6 - - - - configured,missing
opencode-go/mimo-v2-pro text 1024k no yes configured
opencode-go/mimo-v2-omni text+image 256k no yes configured
opencode-go/minimax-m2.7 text 200k no yes configured
opencode-go/minimax-m2.5 text 200k no yes configured
opencode-go/qwen3.6-plus text+image 256k no yes configured
opencode-go/qwen3.5-plus text+image 256k no yes configured
opencode-go/mimo-v2.5-pro - - - - configured,missing
opencode-go/mimo-v2.5 - - - - configured,missing

Observed runtime logs:

[diagnostic] lane task error: lane=main durationMs=12389 error="FailoverError: Unknown model: opencode-go/kimi-k2.6"
[diagnostic] lane task error: lane=session:agent:main:main durationMs=12392 error="FailoverError: Unknown model: opencode-go/kimi-k2.6"
[model-fallback/decision] model fallback decision: decision=candidate_failed requested=opencode-go/kimi-k2.6 candidate=opencode-go/kimi-k2.6 reason=model_not_found next=openai-codex/gpt-5.4 detail=Unknown model: opencode-go/kimi-k2.6
[model-fallback] Model "opencode-go/kimi-k2.6" not found. Fell back to "openai-codex/gpt-5.4".

Relevant docs observed at report time stated opencode-go/kimi-k2.6 is supported in the OpenCode Go catalog.

Impact and severity

    Affected users/systems/channels: users on OpenClaw 2026.4.21 configuring OpenCode Go models, specifically opencode-go/kimi-k2.6
    Severity: blocks workflow for this model
    Frequency: always, based on repeated observed lookups/runtime attempts in this environment
    Consequence: requests for opencode-go/kimi-k2.6 do not route and instead fail over to another model, which can change behavior and provider unexpectedly

Additional information
The same mismatch was also observed for:

    opencode-go/mimo-v2.5-pro
    opencode-go/mimo-v2.5

No observed evidence in this report establishes whether a newer OpenClaw version fixes the issue.
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

OpenCode Go catalog lists opencode-go/kimi-k2.6 in docs but OpenClaw 2026.4.21 resolves it as configured,missing and runtime model_not_found

Steps to reproduce

Configure OPENCODE_API_KEY for OpenCode Go in OpenClaw. Add opencode-go/kimi-k2.6 to agents.defaults.models. Run:

openclaw models list --provider opencode-go

Observe that opencode-go/kimi-k2.6 appears as configured,missing. Attempt to use opencode-go/kimi-k2.6 for a request. Observe fallback/error logs reporting Unknown model: opencode-go/kimi-k2.6.

Expected behavior

Based on the OpenClaw/OpenCode Go docs, opencode-go/kimi-k2.6 should be recognized as a supported OpenCode Go model and route normally when selected.

Actual behavior

Observed behavior in OpenClaw 2026.4.21:

openclaw models list --provider opencode-go shows:
    opencode-go/kimi-k2.6 - - - - configured,missing
Runtime logs show:
    FailoverError: Unknown model: opencode-go/kimi-k2.6
    Model "opencode-go/kimi-k2.6" not found. Fell back to "openai-codex/gpt-5.4".

OpenClaw version

2026.4.21 (f788c88)

Operating system

Windows 11 x64

Install method

npm/global install on Windows

Model

opencode-go/kimi-k2.6

Provider / routing chain

OpenClaw → opencode-go provider → OpenCode Go catalog

Additional provider/model setup details

OPENCODE_API_KEY was configured in openclaw.json. opencode-go plugin was enabled. opencode-go:default auth profile was present. Other OpenCode Go models in the same environment were listed as configured, including:

opencode-go/glm-5.1
opencode-go/glm-5
opencode-go/kimi-k2.5
opencode-go/mimo-v2-pro
opencode-go/mimo-v2-omni
opencode-go/minimax-m2.7
opencode-go/minimax-m2.5
opencode-go/qwen3.6-plus
opencode-go/qwen3.5-plus
<img width="979" height="256" alt="Image" src="https://github.com/user-attachments/assets/14e82489-44b5-4470-8585-3dab487792ff" />

Logs, screenshots, and evidence

Observed openclaw models list --provider opencode-go output:

🦞 OpenClaw 2026.4.21 (f788c88)

Model Input Ctx Local Auth Tags
opencode-go/glm-5.1 text 200k no yes configured
opencode-go/glm-5 text 200k no yes configured
opencode-go/kimi-k2.5 text+image 256k no yes configured
opencode-go/kimi-k2.6 - - - - configured,missing
opencode-go/mimo-v2-pro text 1024k no yes configured
opencode-go/mimo-v2-omni text+image 256k no yes configured
opencode-go/minimax-m2.7 text 200k no yes configured
opencode-go/minimax-m2.5 text 200k no yes configured
opencode-go/qwen3.6-plus text+image 256k no yes configured
opencode-go/qwen3.5-plus text+image 256k no yes configured
opencode-go/mimo-v2.5-pro - - - - configured,missing
opencode-go/mimo-v2.5 - - - - configured,missing

Observed runtime logs:

[diagnostic] lane task error: lane=main durationMs=12389 error="FailoverError: Unknown model: opencode-go/kimi-k2.6"
[diagnostic] lane task error: lane=session:agent:main:main durationMs=12392 error="FailoverError: Unknown model: opencode-go/kimi-k2.6"
[model-fallback/decision] model fallback decision: decision=candidate_failed requested=opencode-go/kimi-k2.6 candidate=opencode-go/kimi-k2.6 reason=model_not_found next=openai-codex/gpt-5.4 detail=Unknown model: opencode-go/kimi-k2.6
[model-fallback] Model "opencode-go/kimi-k2.6" not found. Fell back to "openai-codex/gpt-5.4".

Relevant docs observed at report time stated opencode-go/kimi-k2.6 is supported in the OpenCode Go catalog.

Impact and severity

    Affected users/systems/channels: users on OpenClaw 2026.4.21 configuring OpenCode Go models, specifically opencode-go/kimi-k2.6
    Severity: blocks workflow for this model
    Frequency: always, based on repeated observed lookups/runtime attempts in this environment
    Consequence: requests for opencode-go/kimi-k2.6 do not route and instead fail over to another model, which can change behavior and provider unexpectedly

Additional information
The same mismatch was also observed for:

    opencode-go/mimo-v2.5-pro
    opencode-go/mimo-v2.5

No observed evidence in this report establishes whether a newer OpenClaw version fixes the issue.

Impact and severity

No response

Additional information

No response

extent analysis

TL;DR

The issue can be resolved by updating the OpenClaw configuration to correctly recognize the opencode-go/kimi-k2.6 model or by checking for updates to the OpenClaw version that may include fixes for the model recognition issue.

Guidance

  • Verify that the opencode-go/kimi-k2.6 model is correctly listed in the OpenCode Go catalog and that the OpenClaw configuration is up-to-date.
  • Check the OpenClaw documentation for any specific requirements or configuration options for the opencode-go/kimi-k2.6 model.
  • Investigate whether updating to a newer version of OpenClaw resolves the issue, as the current version (2026.4.21) may contain a bug or outdated configuration.
  • Review the configuration of other OpenCode Go models in the same environment to ensure consistency and identify any potential patterns or differences that may be contributing to the issue.

Example

No code snippet is provided as the issue appears to be related to configuration and model recognition rather than a code-specific problem.

Notes

The issue may be specific to the opencode-go/kimi-k2.6 model or a subset of models, as other models in the same environment are listed as configured correctly. Additionally, the presence of similar issues with other models (opencode-go/mimo-v2.5-pro and opencode-go/mimo-v2.5) suggests a potential pattern or common cause.

Recommendation

Apply a workaround by checking for updates to the OpenClaw version or configuration that may resolve the model recognition issue, as the current version (2026.4.21) may contain a bug or outdated configuration.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

Based on the OpenClaw/OpenCode Go docs, opencode-go/kimi-k2.6 should be recognized as a supported OpenCode Go model and route normally when selected.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - ✅(Solved) Fix [Bug]: OpenCode Go catalog lists opencode-go/kimi-k2.6 in docs but OpenClaw 2026.4.21 resolves it as configured,missing and runtime model_not_found [1 pull requests, 1 comments, 2 participants]