[FEATURE]: kimi k2.5 integration #7720

Closed
opened 2026-02-16 18:08:01 -05:00 by yindo · 47 comments
Owner

Originally created by @ShivamB25 on GitHub (Jan 27, 2026).

Originally assigned to: @rekram1-node on GitHub.

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.

Originally created by @ShivamB25 on GitHub (Jan 27, 2026). Originally assigned to: @rekram1-node on GitHub. ### Feature hasn't been suggested before. - [x] 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.
yindo closed this issue 2026-02-16 18:08:01 -05:00
Author
Owner

@ShivamB25 commented on GitHub (Jan 27, 2026):

using kimi for coding plan

@ShivamB25 commented on GitHub (Jan 27, 2026): using kimi for coding plan
Author
Owner

@github-actions[bot] commented on GitHub (Jan 27, 2026):

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

  • #7314: Missing Kimi model options: K2 turbo and K2 thinking turbo for coding
  • #9135: Add Kimi K2 models to Groq provider
  • #4124: Kimi API support through official coding API

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

@github-actions[bot] commented on GitHub (Jan 27, 2026): This issue might be a duplicate of existing issues. Please check: - #7314: Missing Kimi model options: K2 turbo and K2 thinking turbo for coding - #9135: Add Kimi K2 models to Groq provider - #4124: Kimi API support through official coding API Feel free to ignore if none of these address your specific case.
Author
Owner

@RS91Dev commented on GitHub (Jan 27, 2026):

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.

@RS91Dev commented on GitHub (Jan 27, 2026): 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.
Author
Owner

@sdelost commented on GitHub (Jan 27, 2026):

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

@sdelost commented on GitHub (Jan 27, 2026): 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
Author
Owner

@kamilchm commented on GitHub (Jan 27, 2026):

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:

Image
@kamilchm commented on GitHub (Jan 27, 2026): I tried this with Kimi Code subscription plan: ```json { "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: <img width="1245" height="248" alt="Image" src="https://github.com/user-attachments/assets/8f8a77c9-ee14-4dd2-b280-7b9a704ce032" />
Author
Owner

@oldjs commented on GitHub (Jan 27, 2026):

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

@oldjs commented on GitHub (Jan 27, 2026): > 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
Author
Owner

@sdelost commented on GitHub (Jan 27, 2026):

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

@sdelost commented on GitHub (Jan 27, 2026): 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": "<cut>" }, "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
Author
Owner

@oldjs commented on GitHub (Jan 27, 2026):

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

@oldjs commented on GitHub (Jan 27, 2026): > 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
Author
Owner

@alesha-pro commented on GitHub (Jan 27, 2026):

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

@alesha-pro commented on GitHub (Jan 27, 2026): 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
Author
Owner

@IM-001 commented on GitHub (Jan 27, 2026):

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).

@IM-001 commented on GitHub (Jan 27, 2026): > 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).
Author
Owner

@alesha-pro commented on GitHub (Jan 27, 2026):

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

@alesha-pro commented on GitHub (Jan 27, 2026): > > 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
Author
Owner

@kassieclaire commented on GitHub (Jan 27, 2026):

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

@kassieclaire commented on GitHub (Jan 27, 2026): PR merged to. models.dev and commited ([https://github.com/anomalyco/models.dev/pull/720](https://github.com/anomalyco/models.dev/pull/720)), it is now on models.dev, so just run "opencode models" -- no need for adding it to the config.
Author
Owner

@RS91Dev commented on GitHub (Jan 27, 2026):

it is now on models.dev, so just run "opencode models"

PS C:\Users\dev> opencode model
INFO  2026-01-27T21:54:25 +110ms service=models.dev file={} refreshing
Error: Failed to change directory to C:\Users\dev\model

@RS91Dev commented on GitHub (Jan 27, 2026): > it is now on models.dev, so just run "opencode models" ``` PS C:\Users\dev> opencode model INFO 2026-01-27T21:54:25 +110ms service=models.dev file={} refreshing Error: Failed to change directory to C:\Users\dev\model ```
Author
Owner

@RS91Dev commented on GitHub (Jan 27, 2026):

I am getting this error now .invalid temperature: only 1 is allowed for this model

Image
@RS91Dev commented on GitHub (Jan 27, 2026): I am getting this error now .`invalid temperature: only 1 is allowed for this model` <img width="864" height="218" alt="Image" src="https://github.com/user-attachments/assets/f2a2a725-36d5-447c-800d-ec67ddc05abf" />
Author
Owner

@kevyyar commented on GitHub (Jan 27, 2026):

I am getting this error now .invalid temperature: only 1 is allowed for this model

Image

same getting the same error

@kevyyar commented on GitHub (Jan 27, 2026): > I am getting this error now .`invalid temperature: only 1 is allowed for this model` > > <img alt="Image" width="864" height="218" src="https://private-user-images.githubusercontent.com/32425286/541303028-f2a2a725-36d5-447c-800d-ec67ddc05abf.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Njk1NTU0NTMsIm5iZiI6MTc2OTU1NTE1MywicGF0aCI6Ii8zMjQyNTI4Ni81NDEzMDMwMjgtZjJhMmE3MjUtMzZkNS00NDdjLTgwMGQtZWM2N2RkYzA1YWJmLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNjAxMjclMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjYwMTI3VDIzMDU1M1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWRkNDBiMjcwM2JlY2I0MDIwN2ZkZWM4MzhlZjVmNTAzN2RjMWU1NGY4ZDk3YWFjNWZlNzA2NmVhYTYwYTk1MzUmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.mX3Zw150unwFh9bI2qWvPSUNnWso30YmN6Y7DIUgJd0"> same getting the same error
Author
Owner

@coloradosazulyanaranjados commented on GitHub (Jan 27, 2026):

I am getting this error now .invalid temperature: only 1 is allowed for this model
Image

I had the same problem. I solved with a new mode, you can create one with a different temperature, for example, in the folder of your project
create .opencode/modes/kimi.md
with the content

---
model: moonshot/kimi-k2.5-preview
temperature: 1.0
tools:
  write: true
  edit: true
  bash: true
  read: true
  grep: true
  glob: true
---

then you chan chose the mode using tab, it will appear as a Kimi mode. It's not ideal, but it works.

@coloradosazulyanaranjados commented on GitHub (Jan 27, 2026): > I am getting this error now .`invalid temperature: only 1 is allowed for this model` > <img alt="Image" width="864" height="218" src="https://private-user-images.githubusercontent.com/32425286/541303028-f2a2a725-36d5-447c-800d-ec67ddc05abf.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Njk1NTkzMzcsIm5iZiI6MTc2OTU1OTAzNywicGF0aCI6Ii8zMjQyNTI4Ni81NDEzMDMwMjgtZjJhMmE3MjUtMzZkNS00NDdjLTgwMGQtZWM2N2RkYzA1YWJmLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNjAxMjglMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjYwMTI4VDAwMTAzN1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWYxMzBmMGZmNzQ2NWU3ZDkzMTQzMmNlYTczMzBmOGQ0NDdmODZlNGJjODAxNGJiYmQ2ZGRhOTU5YzhjYmQwZDAmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.zFZZUelsW9Mp4Xygk5MtA06grfXGYKPDGu5qShjfD0M"> I had the same problem. I solved with a new mode, you can create one with a different temperature, for example, in the folder of your project create .opencode/modes/kimi.md with the content ```md --- model: moonshot/kimi-k2.5-preview temperature: 1.0 tools: write: true edit: true bash: true read: true grep: true glob: true --- ``` then you chan chose the mode using tab, it will appear as a Kimi mode. It's not ideal, but it works.
Author
Owner

@AndresCdo commented on GitHub (Jan 27, 2026):

I'm stuck in this error invalid temperature: only 1 is allowed for this model. When I add this configuration to opencode.json file

{
  "\$schema": "https://opencode.ai/config.json",
  "provider": {
    "moonshotai": {
      "models": {
        "kimi-k2.5": {
          "enableThinking": false,
          "reasoning": false,
          "options": {
            "temperature": 1,
            "parallel_tool_calls": false
          }
        }
      }
    }
  }
}

This error appears: thinking is enabled but reasoning_content is missing in assistant tool call message at index 2

@AndresCdo commented on GitHub (Jan 27, 2026): I'm stuck in this error `invalid temperature: only 1 is allowed for this model`. When I add this configuration to `opencode.json` file ``` json { "\$schema": "https://opencode.ai/config.json", "provider": { "moonshotai": { "models": { "kimi-k2.5": { "enableThinking": false, "reasoning": false, "options": { "temperature": 1, "parallel_tool_calls": false } } } } } } ``` This error appears: `thinking is enabled but reasoning_content is missing in assistant tool call message at index 2`
Author
Owner

@reesechou2014 commented on GitHub (Jan 27, 2026):

I'm stuck in this error invalid temperature: only 1 is allowed for this model. When I add this configuration to opencode.json file我遇到了这个错误。当我将此配置添加到文件中时

{
"$schema": "https://opencode.ai/config.json",
"provider": {
"moonshotai": {
"models": {
"kimi-k2.5": {
"enableThinking": false,
"reasoning": false,
"options": {
"temperature": 1,
"parallel_tool_calls": false
}
}
}
}
}
}
This error appears: 此错误已出现:thinking is enabled but reasoning_content is missing in assistant tool call message at index 2

me tool ,same question

@reesechou2014 commented on GitHub (Jan 27, 2026): > I'm stuck in this error `invalid temperature: only 1 is allowed for this model`. When I add this configuration to `opencode.json` file我遇到了这个错误。当我将此配置添加到文件中时 > > { > "\$schema": "https://opencode.ai/config.json", > "provider": { > "moonshotai": { > "models": { > "kimi-k2.5": { > "enableThinking": false, > "reasoning": false, > "options": { > "temperature": 1, > "parallel_tool_calls": false > } > } > } > } > } > } > This error appears: 此错误已出现:`thinking is enabled but reasoning_content is missing in assistant tool call message at index 2` me tool ,same question
Author
Owner

@labxwin commented on GitHub (Jan 27, 2026):

I'm stuck in this error invalid temperature: only 1 is allowed for this model. When I add this configuration to opencode.json file我遇到了这个错误。当我将此配置添加到文件中时
{
"$schema": "https://opencode.ai/config.json",
"provider": {
"moonshotai": {
"models": {
"kimi-k2.5": {
"enableThinking": false,
"reasoning": false,
"options": {
"temperature": 1,
"parallel_tool_calls": false
}
}
}
}
}
}
This error appears: 此错误已出现:thinking is enabled but reasoning_content is missing in assistant tool call message at index 2

me tool ,same question

That's weird. It's working for me.
Edit: After I asked more questions, such as checking the weather, it returned an error: "Thinking is enabled, but reasoning_content is missing in the assistant tool call message at index 2," just as others had mentioned previously.

Image Image
@labxwin commented on GitHub (Jan 27, 2026): > > I'm stuck in this error `invalid temperature: only 1 is allowed for this model`. When I add this configuration to `opencode.json` file我遇到了这个错误。当我将此配置添加到文件中时 > > { > > "$schema": "https://opencode.ai/config.json", > > "provider": { > > "moonshotai": { > > "models": { > > "kimi-k2.5": { > > "enableThinking": false, > > "reasoning": false, > > "options": { > > "temperature": 1, > > "parallel_tool_calls": false > > } > > } > > } > > } > > } > > } > > This error appears: 此错误已出现:`thinking is enabled but reasoning_content is missing in assistant tool call message at index 2` > > me tool ,same question ~~That's weird. It's working for me.~~ **Edit**: After I asked more questions, such as checking the weather, it returned an error: "Thinking is enabled, but reasoning_content is missing in the assistant tool call message at index 2," just as others had mentioned previously. <img width="299" height="193" alt="Image" src="https://github.com/user-attachments/assets/01da7f72-00ff-42b8-b6ef-9b015739089f" /> <img width="1823" height="347" alt="Image" src="https://github.com/user-attachments/assets/2ef61fbb-1098-4ddc-9f3c-ddf4e2688f5e" />
Author
Owner

@oldjs commented on GitHub (Jan 27, 2026):

I'm stuck with this error invalid temperature: only 1 is allowed for this model. When I add this configuration to the opencode.json file, I encounter this error.
{
"$schema": "https://opencode.ai/config.json",
"provider": {
"moonshotai": {
"models": {
"kimi-k2.5": {
"enableThinking": false,
"reasoning": false,
"options": {
"temperature": 1,
"parallel_tool_calls": false
}
}
}
}
}
}
This error appears: thinking is enabled but reasoning_content is missing in assistant tool call message at index 2

me too, same question

That's weird. It's working for me. Edit: After I asked more questions, such as checking the weather, it returned an error: "Thinking is enabled, but reasoning_content is missing in the assistant tool call message at index 2," just as others had mentioned previously.

Image Image

Oh, these Chinese models have way too many issues

@oldjs commented on GitHub (Jan 27, 2026): > > > I'm stuck with this error `invalid temperature: only 1 is allowed for this model`. When I add this configuration to the `opencode.json` file, I encounter this error. > > > { > > > "$schema": "https://opencode.ai/config.json", > > > "provider": { > > > "moonshotai": { > > > "models": { > > > "kimi-k2.5": { > > > "enableThinking": false, >>> "reasoning": false, >>> "options": { >>> "temperature": 1, >>> "parallel_tool_calls": false > > > } > > > } > > > } > > > } > > > } > > > } > > > This error appears: `thinking is enabled but reasoning_content is missing in assistant tool call message at index 2` > > > > > > me too, same question > > ~That's weird. It's working for me.~ **Edit**: After I asked more questions, such as checking the weather, it returned an error: "Thinking is enabled, but reasoning_content is missing in the assistant tool call message at index 2," just as others had mentioned previously. > > <img alt="Image" width="299" height="193" src="https://private-user-images.githubusercontent.com/227209734/541390114-01da7f72-00ff-42b8-b6ef-9b015739089f.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Njk1NzYwMDcsIm5iZiI6MTc2OTU3NTcwNywicGF0aCI6Ii8yMjcyMDk3MzQvNTQxMzkwMTE0LTAxZGE3ZjcyLTAwZmYtNDJiOC1iNmVmLTliMDE1NzM5MDg5Zi5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjYwMTI4JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmXC1BbXotRGF0ZT0yMDI2MDEyOFQwNDQ4MjdaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT04MTAzMjU1MzA5NjNkNTlhMmRhMWQxNmZiMjQ2ZjdiYWEyOTdiN2NmYzc1ZDQ3M2EzNjBhYjZhYzg4N2ExMGYwJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.AGXju0uM3-Tcjxy9sOh4bn_418yG5MJsG0KIRZ_toS0"> <img alt="Image" width="1823" height="347" src="https://private-user-images.githubusercontent.com/227209734/541390338-2ef61fbb-1098-4ddc-9f3c-ddf4e2688f5e.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Njk1NzYwMDcsIm5iZiI6MTc2OTU3NTcwNywicGF0aCI6Ii8yMjcyMDk3MzQvNTQxMzkwMzM4LTJlZjYxZmJiLTEwOTgtNGRkYy05ZjNjLWRkZjRlMjY4OGY1ZS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjYwMTI4JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI2MDEyOFQwNDQ4MjdaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT03ZjA2ODU0NDQzZmIxOTUyOWVhNGIxMjYyMDcwMGYzN2UzYmYwNDk3NTAyOWIyOWUyODEwOWQwNWZlYjhmN2JhJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.UaexvPhJ_M5bM8ZZCwPMuThDJis0Hme1i44iIBdJr-s"> Oh, these Chinese models have way too many issues
Author
Owner

@RS91Dev commented on GitHub (Jan 28, 2026):

I am getting this error now .invalid temperature: only 1 is allowed for this model
Image

I had the same problem. I solved with a new mode, you can create one with a different temperature, for example, in the folder of your project create .opencode/modes/kimi.md with the content


model: moonshot/kimi-k2.5-preview
temperature: 1.0
tools:
write: true
edit: true
bash: true
read: true
grep: true
glob: true

then you chan chose the mode using tab, it will appear as a Kimi mode. It's not ideal, but it works.

Image nice

@RS91Dev commented on GitHub (Jan 28, 2026): > > I am getting this error now .`invalid temperature: only 1 is allowed for this model` > > <img alt="Image" width="864" height="218" src="https://private-user-images.githubusercontent.com/32425286/541303028-f2a2a725-36d5-447c-800d-ec67ddc05abf.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Njk1NTkzMzcsIm5iZiI6MTc2OTU1OTAzNywicGF0aCI6Ii8zMjQyNTI4Ni81NDEzMDMwMjgtZjJhMmE3MjUtMzZkNS00NDdjLTgwMGQtZWM2N2RkYzA1YWJmLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNjAxMjglMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjYwMTI4VDAwMTAzN1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWYxMzBmMGZmNzQ2NWU3ZDkzMTQzMmNlYTczMzBmOGQ0NDdmODZlNGJjODAxNGJiYmQ2ZGRhOTU5YzhjYmQwZDAmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.zFZZUelsW9Mp4Xygk5MtA06grfXGYKPDGu5qShjfD0M"> > > I had the same problem. I solved with a new mode, you can create one with a different temperature, for example, in the folder of your project create .opencode/modes/kimi.md with the content > > --- > model: moonshot/kimi-k2.5-preview > temperature: 1.0 > tools: > write: true > edit: true > bash: true > read: true > grep: true > glob: true > --- > then you chan chose the mode using tab, it will appear as a Kimi mode. It's not ideal, but it works. <img width="848" height="328" alt="Image" src="https://github.com/user-attachments/assets/4e33adc3-cc30-4e42-b889-72c4c60f075f" /> nice
Author
Owner

@willy-scr commented on GitHub (Jan 28, 2026):

Why does Kimi 2.5 always throw errors like this?
I directly put it into the OpenCode login auth using the Kimi coding plan API

Is there any special config needed for Kimi on the coding plan?

Image
@willy-scr commented on GitHub (Jan 28, 2026): Why does Kimi 2.5 always throw errors like this? I directly put it into the OpenCode login auth using the Kimi coding plan API Is there any special config needed for Kimi on the coding plan? <img width="1039" height="277" alt="Image" src="https://github.com/user-attachments/assets/8e1965f6-7b7f-4b59-ac37-bdf69c31c511" />
Author
Owner

@zinglax commented on GitHub (Jan 28, 2026):

I am getting the temperature error using the Fireworks AI provider.

@zinglax commented on GitHub (Jan 28, 2026): I am getting the temperature error using the Fireworks AI provider.
Author
Owner

@zinglax commented on GitHub (Jan 28, 2026):

@willy-scr saw this comment here https://github.com/anomalyco/opencode/issues/10850#issuecomment-3808582965 about "reasoning_content", I am looking into this myself but the answer might be here https://github.com/anomalyco/opencode/issues/6040

@zinglax commented on GitHub (Jan 28, 2026): @willy-scr saw this comment here https://github.com/anomalyco/opencode/issues/10850#issuecomment-3808582965 about "reasoning_content", I am looking into this myself but the answer might be here https://github.com/anomalyco/opencode/issues/6040
Author
Owner

@iambaseddev commented on GitHub (Jan 28, 2026):

JSON Schema not supported: could not understand the instance {}.
I am using 1.1.40 and kimi 2.5 through opencode zen plan.

@iambaseddev commented on GitHub (Jan 28, 2026): JSON Schema not supported: could not understand the instance `{}`. I am using 1.1.40 and kimi 2.5 through `opencode zen` plan.
Author
Owner

@willy-scr commented on GitHub (Jan 28, 2026):

@willy-scr saw this comment here #10850 (comment) about "reasoning_content", I am looking into this myself but the answer might be here #6040

ahh thank uu

@willy-scr commented on GitHub (Jan 28, 2026): > [@willy-scr](https://github.com/willy-scr) saw this comment here [#10850 (comment)](https://github.com/anomalyco/opencode/issues/10850#issuecomment-3808582965) about "reasoning_content", I am looking into this myself but the answer might be here [#6040](https://github.com/anomalyco/opencode/issues/6040) ahh thank uu
Author
Owner

@rekram1-node commented on GitHub (Jan 29, 2026):

Anyone still having issues?

If so please give me your:

  • opencode version
  • plugins you are using
  • provider you are using
@rekram1-node commented on GitHub (Jan 29, 2026): Anyone still having issues? If so please give me your: - opencode version - plugins you are using - provider you are using
Author
Owner

@iambaseddev commented on GitHub (Jan 29, 2026):

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

@iambaseddev commented on GitHub (Jan 29, 2026): > 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
Author
Owner

@eusip commented on GitHub (Jan 29, 2026):

Is #10835 going to be merged in order to address this?

@eusip commented on GitHub (Jan 29, 2026): Is #10835 going to be merged in order to address this?
Author
Owner

@pavel-kirienko commented on GitHub (Jan 29, 2026):

K2.5 support has already been released in v1.1.42. It's nowhere close to Sonnet though despite the claims made in this thread above, FYI.

@pavel-kirienko commented on GitHub (Jan 29, 2026): K2.5 support has already been released in v1.1.42. It's nowhere close to Sonnet though despite the claims made in this thread above, FYI.
Author
Owner

@nerdyworm commented on GitHub (Jan 29, 2026):

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

Image
@nerdyworm commented on GitHub (Jan 29, 2026): > > 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 <img width="2484" height="1516" alt="Image" src="https://github.com/user-attachments/assets/f5ec7895-fefd-42b4-a0ac-da265c133e1a" />
Author
Owner

@cocotyty commented on GitHub (Jan 29, 2026):

When using the opencode zen provider with the Kimi K2.5 model, Thinking mode is triggered correctly. However, when switching to the Kimi For Coding provider with the same K2.5 model, Thinking mode is not triggered

@cocotyty commented on GitHub (Jan 29, 2026): When using the opencode zen provider with the Kimi K2.5 model, Thinking mode is triggered correctly. However, when switching to the Kimi For Coding provider with the same K2.5 model, Thinking mode is not triggered
Author
Owner

@Cheerwhy commented on GitHub (Jan 30, 2026):

When using the opencode zen provider with the Kimi K2.5 model, Thinking mode is triggered correctly. However, when switching to the Kimi For Coding provider with the same K2.5 model, Thinking mode is not triggered

ctrl + t

@Cheerwhy commented on GitHub (Jan 30, 2026): > When using the opencode zen provider with the Kimi K2.5 model, Thinking mode is triggered correctly. However, when switching to the Kimi For Coding provider with the same K2.5 model, Thinking mode is not triggered ctrl + t
Author
Owner

@dive commented on GitHub (Jan 30, 2026):

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.

@dive commented on GitHub (Jan 30, 2026): 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.
Author
Owner

@vladbesson commented on GitHub (Jan 30, 2026):

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.'}`.
@vladbesson commented on GitHub (Jan 30, 2026): 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.'}`. ```
Author
Owner

@zhming0 commented on GitHub (Jan 30, 2026):

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.

@zhming0 commented on GitHub (Jan 30, 2026): 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.
Author
Owner

@nerdyworm commented on GitHub (Jan 30, 2026):

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.

@nerdyworm commented on GitHub (Jan 30, 2026): > > > 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.
Author
Owner

@rekram1-node commented on GitHub (Jan 30, 2026):

Anyone still having issues? or good to close?

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

@rekram1-node commented on GitHub (Jan 30, 2026): Anyone still having issues? or good to close? separately @zhming0 I saw ur pr ill look at it (kinda separate from this tho)
Author
Owner

@martinffx commented on GitHub (Jan 31, 2026):

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

@martinffx commented on GitHub (Jan 31, 2026): > 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`
Author
Owner

@jonaustin commented on GitHub (Jan 31, 2026):

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 commented on GitHub (Jan 31, 2026): > 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
Author
Owner

@rekram1-node commented on GitHub (Jan 31, 2026):

@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 commented on GitHub (Jan 31, 2026): @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
Author
Owner

@douglascamata commented on GitHub (Jan 31, 2026):

@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: https://github.com/anomalyco/opencode/pull/11410.

The permissions part of the problem persists.

@douglascamata commented on GitHub (Jan 31, 2026): @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: https://github.com/anomalyco/opencode/pull/11410. The permissions part of the problem persists.
Author
Owner

@douglascamata commented on GitHub (Jan 31, 2026):

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

@douglascamata commented on GitHub (Jan 31, 2026): Learned from #11320 that the permissions issue is a typo on my side.
Author
Owner

@jonaustin commented on GitHub (Feb 1, 2026):

@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.

@jonaustin commented on GitHub (Feb 1, 2026): > [@jonaustin](https://github.com/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.
Author
Owner

@M0n7y5 commented on GitHub (Feb 4, 2026):

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

@M0n7y5 commented on GitHub (Feb 4, 2026): I cant enable reasoning for Kimi for Coding models in version 1.1.51. Can somebody repro this as well?
Author
Owner

@hayedewit commented on GitHub (Feb 4, 2026):

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.

@hayedewit commented on GitHub (Feb 4, 2026): > 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.
Author
Owner

@R44VC0RP commented on GitHub (Feb 4, 2026):

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: https://github.com/anomalyco/opencode/issues/12090#issuecomment-3849383039

@R44VC0RP commented on GitHub (Feb 4, 2026): 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: https://github.com/anomalyco/opencode/issues/12090#issuecomment-3849383039
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#7720