[FEATURE]: kimi k2.5 integration

Feature hasn't been suggested before.

I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

please add support for it.

using kimi for coding plan

This issue might be a duplicate of existing issues. Please check:

Missing Kimi model options: K2 turbo and K2 thinking turbo for coding #7314: Missing Kimi model options: K2 turbo and K2 thinking turbo for coding
[FEATURE]: Add Kimi K2 models to Groq provider #9135: Add Kimi K2 models to Groq provider
[FEATURE]:https://api.kimi.com/coding/ support #4124: Kimi API support through official coding API

Feel free to ignore if none of these address your specific case.

Kimi K2.5 integration is not supported via https://www.moonshot.ai/ API
or https://openrouter.ai/moonshotai/kimi-k2.5
. Please add support for Kimi 2.5.

I managed to add kimi k2.5 from moonshot.ai api platform, but while using it, in reasoning phase, I receive error: thinking is enabled but reasoning_content is missing in assistant tool call message at index 18

I tried this with Kimi Code subscription plan:

{
  "provider": {
    "kimi-code": {
      "name": "Kimi Code",
      "npm": "@ai-sdk/openai-compatible",
      "options": {
        "baseURL": "https://api.kimi.com/coding/v1",
        "headers": {
          "Authorization": "Bearer {env:KIMICODE_API_KEY}"
        }
      },
      "models": {
        "Kimi K2.5": {
          "id": "kimi-k2.5"
        }
      }
    }
  }
}

but no luck:

I successfully added kimi k2.5 from the moonshot.ai API platform, but when using it, I receive an error during the reasoning phase: thinking is enabled but reasoning_content is missing in the assistant tool call message at index 18

I managed to add kimi k2.5 from moonshot.ai api platform, but while using it, in reasoning phase, I receive error: thinking is enabled but reasoning_content is missing in assistant tool call message at index 18

Same issue

Kimi K2.5 model returns reasoning_content field for thinking/reasoning which causes error: "thinking is enabled but reasoning_content is missing in assistant tool call message"
The Kimi API uses thinking: {type: "disabled"} parameter format and returns reasoning in reasoning_content field alongside content.
Docs: https://platform.moonshot.ai/docs/guide/kimi-k2-5-quickstart

In my opencode.json it looks like this:
"moonshot": {
"npm": "@ai-sdk/openai-compatible",
"name": "Moonshot (Kimi)",
"options": {
"baseURL": "https://api.moonshot.ai/v1",
"apiKey": ""
},
"models": {
"kimi-k2.5": {
"name": "Kimi K2.5",
"thinking": {"type": "enabled"},
"temperature": 1.0
}
}
}
It's throwing that error even if thinking type is set to disabled

The Kimi K2.5 model returns a reasoning_content field for thinking/reasoning, which causes the error: "thinking is enabled but reasoning_content is missing in assistant tool call message". The Kimi API uses the thinking: {type: "disabled"} parameter format and returns reasoning in the reasoning_content field alongside content. Docs: https://platform.moonshot.ai/docs/guide/kimi-k2-5-quickstart

In my opencode.json it looks like this: "moonshot": { "npm": "@ai-sdk/openai-compatible", "name": "Moonshot (Kimi)", "options": { "baseURL": "https://api.moonshot.ai/v1", "apiKey": "" }, "models": { "kimi-k2.5": { "name": "Kimi K2.5", "thinking": {"type": "enabled"}, "temperature": 1.0 } } }

Same issue

Login with kimi for coding (opencode auth login), enter ur api key and then add

  "provider": {
    "kimi-for-coding": {
      "models": {
        "Kimi K2.5": {
          "id": "kimi-k2.5"
        }
      }
    },

in ur opencode.json.

thats wurk

Login with kimi for coding (opencode auth login), enter ur api key and then add
  "provider": {
    "kimi-for-coding": {
      "models": {
        "Kimi K2.5": {
          "id": "kimi-k2.5"
        }
      }
    },
in ur opencode.json.

thats wurk

That was smart, but it defaults to the generic "kimi-for-coding" model, aka Kimi 2 thinking:

what model are you?
I'm powered by the model kimi-k2-thinking (model ID: kimi-for-coding/kimi-k2-thinking).

Login with kimi for coding (opencode auth login), enter ur api key and then add
  "provider": {
    "kimi-for-coding": {
      "models": {
        "Kimi K2.5": {
          "id": "kimi-k2.5"
        }
      }
    },
in ur opencode.json.
thats wurk
That was smart, but it defaults to the generic "kimi-for-coding" model, aka Kimi 2 thinking:

what model are you?
I'm powered by the model kimi-k2-thinking (model ID: kimi-for-coding/kimi-k2-thinking).

Oh shit

PR merged to. models.dev and commited (anomalyco/models.dev#720), it is now on models.dev, so just run "opencode models" -- no need for adding it to the config.

The kimi-k2.5-free model displays the error “Extra inputs are not permitted, field: ‘reasoning’” in both Plan & Build modes. The Opencode version is 1.1.44 & Kimi is connected via the Opencode Zen provider.

Also have that issue with kimi 2.5 in the latest opencode (1.1.44)

JSON Schema not supported: could not understand the instance `{'description': 'Value to set. Must match field type from schema. For references: {_type: "reference", _ref: "id"}. For blocks: include _type.'}`.

Kimi 2.5 under the Moonshot provider works for me in OpenCode 1.1.44. The only issue now is the Read tool x media doesn't invoke vision api. There are two raised issues #11304 and #11306, and an attempted fix in #11323.

Anyone still having issues?
If so please give me your:

opencode version

plugins you are using

provider you are using

JSON Schema not supported: could not understand the instance {}.
1.1.40 no plugins opencode zen

Also hitting with with the Kimi K2.5 Free OpenCode Zen

This has been resolved, thank you.

@zhming0

Anyone still having issues? or good to close?

separately @zhming0 I saw ur pr ill look at it (kinda separate from this tho)

The kimi-k2.5-free model displays the error “Extra inputs are not permitted, field: ‘reasoning’” in both Plan & Build modes. The Opencode version is 1.1.44 & Kimi is connected via the Opencode Zen provider.

I'm getting this but only in plan mode, in 1.1.48

using kimi for coding plan
Anyone still having issues? or good to close?

This issue is for the Kimi Code Plan which far as I can tell does not provide api keys; so this issue is still completely unresolved? (maybe not fixable if kimi doesn't allow this, like recent claude change)

edit: After signup api keys can be created here https://www.kimi.com/code/console

@jonaustin

@jonaustin but they do provide keys? https://www.kimi.com/code/docs/en/more/third-party-agents.html#configure-the-kimi-code-model-1

And the model is available:
https://models.dev/?search=kimi-for-coding

@rekram1-node

@rekram1-node I have issues using kimi k2.5 because I have customized my "build" agent for Opus 4.5 max with certain permissions and a hardcoded variant. OpenCode is then throwing this error when I switch the model in the TUI:

2 request validation errors: Extra inputs are not permitted, field: 'variant', value: 'max'; Extra inputs are not permitted, field: 'permissions'

I think people already created a PR to fix the variant issue: #11410.

The permissions part of the problem persists.

Learned from #11320 that the permissions issue is a typo on my side.

@jonaustin but they do provide keys? https://www.kimi.com/code/docs/en/more/third-party-agents.html#configure-the-kimi-code-model-1

And the model is available: https://models.dev/?search=kimi-for-coding

Thanks, you're absolutely right; I must be blind or something doh. I'll edit my original post.

I cant enable reasoning for Kimi for Coding models in version 1.1.51. Can somebody repro this as well?

I cant enable reasoning for Kimi for Coding models in version 1.1.51. Can somebody repro this as well?

Yup, after the update it stopped working. I could switch modes before the update. Just tested and it happens from version v1.1.50 on 1.1.49 it still works.

We removed the high/max variants because k2p5 doesnt actually accept the token budgets, however doing this caused the reasoning to stop working properly (for kimi coding provider)

Kimi for coding (along w/ the other kimi 2.5 providers) only allow u to toggle reasoning on or off. Unlike the other providers kimi for coding actually defaults to thinking off. In the next release we will default to thinking on, and we also need to add variant to allow you to turn it off easily.

A workaround right now is using this: #12090 (comment)

Navigation Menu

Repository navigation

[FEATURE]: kimi k2.5 integration #10811

Feature hasn't been suggested before.

Describe the enhancement you want to request

25 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

[FEATURE]: kimi k2.5 integration #10811

Description

Feature hasn't been suggested before.

Describe the enhancement you want to request

Activity

ShivamB25 commented on Jan 27, 2026

github-actions commented on Jan 27, 2026

RS91Dev commented on Jan 27, 2026

sdelost commented on Jan 27, 2026

kamilchm commented on Jan 27, 2026

oldjs commented on Jan 27, 2026

sdelost commented on Jan 27, 2026

oldjs commented on Jan 27, 2026

alesha-pro commented on Jan 27, 2026

IM-001 commented on Jan 27, 2026

alesha-pro commented on Jan 27, 2026

kassieclaire commented on Jan 27, 2026

25 remaining items

dive commented on Jan 30, 2026

vladbesson commented on Jan 30, 2026

zhming0 commented on Jan 30, 2026

nerdyworm commented on Jan 31, 2026

rekram1-node commented on Jan 31, 2026

martinffx commented on Jan 31, 2026

jonaustin commented on Jan 31, 2026

rekram1-node commented on Jan 31, 2026

douglascamata commented on Feb 1, 2026

douglascamata commented on Feb 1, 2026

jonaustin commented on Feb 1, 2026

M0n7y5 commented on Feb 4, 2026

hayedewit commented on Feb 4, 2026

R44VC0RP commented on Feb 4, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions