You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Kimi K2.5 frequently gets in a reiteration loop #14343
I'm also having problems using Zen's Kimi K2.5. The Free version of Kimi K2.5 worked as expected, but the paid version somehow behaves strangely when used with the same tasks. It feels like the two models are completely different, even though that shouldn't be the case.
UPD: The free version worked until it disappeared from the desktop app.
I don’t know enough about all this to tell whether this is a proper fix or just a workaround, but setting frequency_penalty to 2.0 (the maximum) and temperature to 0.3 made Kimi K2.5 usable for me.
Activity
github-actions commentedon Feb 19, 2026
This issue might be a duplicate of existing issues. Please check:
If your issue is distinct from the above, please clarify what makes it different.
rekram1-node commentedon Feb 20, 2026
What provider?
berenddeboer commentedon Feb 20, 2026
Opencode Zen.
yuriy-merkudinov commentedon Feb 20, 2026
I'm also having problems using Zen's Kimi K2.5. The Free version of Kimi K2.5 worked as expected, but the paid version somehow behaves strangely when used with the same tasks. It feels like the two models are completely different, even though that shouldn't be the case.
UPD: The free version worked until it disappeared from the desktop app.
moritzruth commentedon Mar 16, 2026
I don’t know enough about all this to tell whether this is a proper fix or just a workaround, but setting
frequency_penaltyto2.0(the maximum) andtemperatureto0.3made Kimi K2.5 usable for me.{ "provider": { "openrouter": { "models": { "moonshotai/kimi-k2.5": { "options": { "frequency_penalty": 2.0, "temperature": 0.3, }, }, }, }, }, }github-actions commentedon Jul 4, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.