Skip to content

Fix Kimi K3 temperature support for OpenCode Go - #3328

Closed
mihneaptu wants to merge 1 commit into
anomalyco:devfrom
mihneaptu:kimi-k3-temperature
Closed

mihneaptu wants to merge 1 commit into
anomalyco:devfrom
mihneaptu:kimi-k3-temperature

Conversation

@mihneaptu

Copy link
Copy Markdown

Summary

Mark OpenCode Go's Kimi K3 as temperature = false. The base model currently advertises temperature support, so clients send the field and OpenCode Go rejects the request upstream.

This does not change reasoning support; the resolved model still exposes the max effort variant.

Evidence

Validation

  • bun validate
  • Resolved catalog: temperature: false, reasoning effort values: ["max"]

@rekram1-node

Copy link
Copy Markdown
Collaborator

Superseded by #3331 (merged).

Provider-local temperature = false on OpenCode Go was the wrong layer — the base model incorrectly advertised temperature support. #3331 sets temperature = false on models/moonshotai/kimi-k3.toml so all providers inherit it, and stops the Vercel sync from reasserting temperature = true.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants