anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 18:25:32 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

Reasoning error when using Kimi K2 via Groq #1300

New Issue
Closed
opened 2026-02-16 17:30:21 -05:00 by yindo · 15 comments
yindo commented 2026-02-16 17:30:21 -05:00
Owner
Copy Link
Copy Source

Originally created by @goszczynskip on GitHub (Aug 14, 2025).

Originally assigned to: @rekram1-node on GitHub.

When I switch the model to "Groq Kimi K2 Instruct" and send a message to the model after a few initial answers, I'm getting

AI_APICallError: `messages[3].reasoning`: reasoning is not supported with this model
Originally created by @goszczynskip on GitHub (Aug 14, 2025). Originally assigned to: @rekram1-node on GitHub. When I switch the model to "Groq Kimi K2 Instruct" and send a message to the model after a few initial answers, I'm getting ``` AI_APICallError: `messages[3].reasoning`: reasoning is not supported with this model ```
yindo closed this issue 2026-02-16 17:30:21 -05:00
yindo commented 2026-02-16 17:30:21 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Aug 14, 2025):

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

  • #53: Similar Groq reasoning parameter error ("reasoning_effort is unsupported")
  • #1859: GPT-5 reasoning parameter unsupported error
  • #1742: Similar reasoning parameter format issues

The core issue appears to be that reasoning parameters are being sent to models that don't support them. If none of these address your specific case with Kimi K2, please let us know how this issue differs.

@github-actions[bot] commented on GitHub (Aug 14, 2025): 👋 This issue might be a duplicate of existing issues. Please check: - #53: Similar Groq reasoning parameter error ("reasoning_effort is unsupported") - #1859: GPT-5 reasoning parameter unsupported error - #1742: Similar reasoning parameter format issues The core issue appears to be that reasoning parameters are being sent to models that don't support them. If none of these address your specific case with Kimi K2, please let us know how this issue differs.
yindo commented 2026-02-16 17:30:21 -05:00
Author
Owner
Copy Link
Copy Source

@goszczynskip commented on GitHub (Aug 14, 2025):

This looks similar to the following issues, but it happens for a different model.

@goszczynskip commented on GitHub (Aug 14, 2025): This looks similar to the following issues, but it happens for a different model.
yindo commented 2026-02-16 17:30:21 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Aug 14, 2025):

Can replicate, I will look into this.

@rekram1-node commented on GitHub (Aug 14, 2025): Can replicate, I will look into this.
yindo commented 2026-02-16 17:30:21 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Aug 14, 2025):

I think this is an upstream issue with vercel ai sdk.

@rekram1-node commented on GitHub (Aug 14, 2025): I think this is an upstream issue with vercel ai sdk.
yindo commented 2026-02-16 17:30:21 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Aug 14, 2025):

open issue in vercel ai sdk: https://github.com/vercel/ai/issues/8056

once that gets fixed we can fix our support here

@rekram1-node commented on GitHub (Aug 14, 2025): open issue in vercel ai sdk: https://github.com/vercel/ai/issues/8056 once that gets fixed we can fix our support here
yindo commented 2026-02-16 17:30:21 -05:00
Author
Owner
Copy Link
Copy Source

@shreyv5678 commented on GitHub (Aug 15, 2025):

That issue has been fixed, any updates?

@shreyv5678 commented on GitHub (Aug 15, 2025): That issue has been fixed, any updates?
yindo commented 2026-02-16 17:30:21 -05:00
Author
Owner
Copy Link
Copy Source

@michabbb commented on GitHub (Aug 15, 2025):

not for me... still getting errors: AI_APICallError: messages[3].reasoning: reasoning is not supported with this model

@michabbb commented on GitHub (Aug 15, 2025): not for me... still getting errors: `AI_APICallError: messages[3].reasoning: reasoning is not supported with this model `
yindo commented 2026-02-16 17:30:21 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Aug 15, 2025):

@shreyv5678 @michabbb @goszczynskip run: rm -rf ~/.cache/opencode and then try again, this should reinstall your providers

@rekram1-node commented on GitHub (Aug 15, 2025): @shreyv5678 @michabbb @goszczynskip run: `rm -rf ~/.cache/opencode` and then try again, this should reinstall your providers
yindo commented 2026-02-16 17:30:22 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Aug 15, 2025):

And it will auto update the groq package, fixing issue.

lmk if that doesn't work, i tested locally and it did.

@rekram1-node commented on GitHub (Aug 15, 2025): And it will auto update the groq package, fixing issue. lmk if that doesn't work, i tested locally and it did.
yindo commented 2026-02-16 17:30:22 -05:00
Author
Owner
Copy Link
Copy Source

@michabbb commented on GitHub (Aug 15, 2025):

@rekram1-node confirmed! after deleting the cache, no more errors 💪 😘

@michabbb commented on GitHub (Aug 15, 2025): @rekram1-node confirmed! after deleting the cache, no more errors 💪 😘
yindo commented 2026-02-16 17:30:22 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Aug 15, 2025):

awesome

@rekram1-node commented on GitHub (Aug 15, 2025): awesome
yindo commented 2026-02-16 17:30:22 -05:00
Author
Owner
Copy Link
Copy Source

@michabbb commented on GitHub (Aug 15, 2025):

btw... these little tricks are usually nowhere in any documentation, so i suggest putting this stuff into a troubleshooting section somewhere 😏

@michabbb commented on GitHub (Aug 15, 2025): btw... these little tricks are usually nowhere in any documentation, so i suggest putting this stuff into a troubleshooting section somewhere 😏
yindo commented 2026-02-16 17:30:22 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Aug 15, 2025):

yes I completely agree! I will mention this to the team

@rekram1-node commented on GitHub (Aug 15, 2025): yes I completely agree! I will mention this to the team
yindo commented 2026-02-16 17:30:22 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Aug 15, 2025):

closing as completed, I sent a message to the team, thanks for your feedback as always @michabbb

@rekram1-node commented on GitHub (Aug 15, 2025): closing as completed, I sent a message to the team, thanks for your feedback as always @michabbb
yindo commented 2026-02-16 17:30:22 -05:00
Author
Owner
Copy Link
Copy Source

@shreyv5678 commented on GitHub (Aug 15, 2025):

thank you it works now!

@shreyv5678 commented on GitHub (Aug 15, 2025): thank you it works now!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#1300
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?