Repository navigation
HuggingFace provider: reasoning_details not stripped from conversation history for Kimi-K2.5 #13002
Description
Description
When using moonshotai/Kimi-K2.5:together via the HuggingFace provider, the model returns reasoning_details in its responses. On subsequent turns, OpenCode passes this field back in the conversation history, causing a 400 error from the API:
Extra inputs are not permitted, field: 'messages[2].reasoning_details',
{
"$schema": "https://opencode.ai/config.json",
"provider": {
"huggingface": {
"options": {
"headers": {
"X-HF-Bill-To": "my-lisa"
}
},
"models": {
"moonshotai/Kimi-K2.5:together": {
"name": "kimi k2.5 together",
"reasoning": true,
"interleaved": {
"field": "reasoning_details"
}
}
}
}
}
}
What I've tried (none worked)
Adding "interleaved": { "field": "reasoning_content" } (per #6040)
Setting "reasoning": true with interleaved
Setting "reasoning": false
Starting fresh sessions after each config change
Clearing session cache
Expected behavior
OpenCode should strip reasoning_details from assistant messages before sending them back to the API, or properly map them using the interleaved config.
Environment
OpenCode: v1.1.53
OS: Ubuntu (Linux)
Provider: HuggingFace
Model: moonshotai/Kimi-K2.5:together
Plugins
No response
OpenCode version
OpenCode: v1.1.53
Steps to reproduce
No response
Screenshot and/or share link
Operating System
Ubuntu (Linux) 22.04
Terminal
No response
Activity
github-actions commentedon Feb 10, 2026
This issue might be a duplicate of existing issues. Please check:
If your issue is distinct from these, please clarify how it differs.
OpeOginni commentedon Feb 11, 2026
@DeviousCardi This seems to work well for me
{ "$schema": "https://opencode.ai/config.json", "provider": { "huggingface": { "options": { "headers": { } }, "models": { "moonshotai/Kimi-K2.5:together": { "name": "kimi k2.5 together", "reasoning": true } } } } }have you tried it?
DeviousCardi commentedon Feb 11, 2026
@OpeOginni
still getting error
OpeOginni commentedon Feb 11, 2026
@DeviousCardi From your screenshots you are not making use of the
kimi k2.5 togethermodel, you are just making use of thekimi k2.5one, please make sure you are choosing the right model and try againI think with this change, you can add in the
If you want the model to get the reasoning on every request, and it should still work
github-actions commentedon Apr 13, 2026
To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.