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

Has anyone been successful at setting up Kimi K2.5 via NanoGPT? #8179

New Issue
Open
opened 2026-02-16 18:09:21 -05:00 by yindo · 5 comments
yindo commented 2026-02-16 18:09:21 -05:00
Owner
Copy Link
Copy Source

Originally created by @O-ELMA on GitHub (Jan 31, 2026).

Originally assigned to: @rekram1-node on GitHub.

Question

I am astonished to see that some have been successful in using seamlessly Kimi K2.5 (DeepSeek 3.2 too) via NanoGPT in Opencode.

It has not worked a single time since I have countless tried it. It's buggy:

  • it loops over in reasoning,
  • it fails to call tools,
  • it fires sub-agents then forgets about them, only to stop.

Has anyone figured out a setup that works? I am seeking, please, your advice.

Here is what I tried so far:

  • Disabling all my plugins (DCP & Oh-my-opencode)
  • Disabling the reasoning
  • Adding the "interleaved": { "field": "reasoning_content" }

Shall I just say that Kimi K2.5 works flawlessly via Opencode Zen.

  • Opencode version: 1.1.48-1
  • OS: Linux
  • Plugins: oh-my-opencode 2.14.0 and @tarquinen/opencode-dcp@latest
Originally created by @O-ELMA on GitHub (Jan 31, 2026). Originally assigned to: @rekram1-node on GitHub. ### Question I am astonished to see that some have been successful in using seamlessly Kimi K2.5 (DeepSeek 3.2 too) via NanoGPT in Opencode. It has not worked a single time since I have countless tried it. It's buggy: * it loops over in reasoning, * it fails to call tools, * it fires sub-agents then forgets about them, only to stop. Has anyone figured out a setup that works? I am seeking, please, your advice. Here is what I tried so far: * Disabling all my plugins (DCP & Oh-my-opencode) * Disabling the reasoning * Adding the `"interleaved": { "field": "reasoning_content" }` Shall I just say that Kimi K2.5 works flawlessly via Opencode Zen. --- * Opencode version: 1.1.48-1 * OS: Linux * Plugins: `oh-my-opencode 2.14.0` and `@tarquinen/opencode-dcp@latest`
yindo commented 2026-02-16 18:09:21 -05:00
Author
Owner
Copy Link
Copy Source

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

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

  • #11446: New Kimi 2.5 model is giving error about 'reasoning_content' field (CLOSED - fixed)
  • #11357: JSON Schema validation fails on empty tool parameters {} with Kimi K2.5 (strict mode error)
  • #11320: [BUG] Kimi K2 Rejects permissions Field in Agent Frontmatter
  • #11053: [BUG] Kimi k2.5 doesn't use the question tool
  • #11210: Kimi K2 via AWS BEDROCK stops execution
  • #11229: error when using kimi2.5 (similar JSON Schema issue)
  • #11128: [FEATURE]: nano-gpt provider - support Kimi K2.5

Your description mentions:

  • Loops over in reasoning
  • Fails to call tools
  • Fires sub-agents then forgets about them

These symptoms align with the known issues above, particularly #11357 (JSON Schema validation with empty parameters), #11053 (question tool not working properly), and #11210 (execution stopping).

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

@github-actions[bot] commented on GitHub (Jan 31, 2026): This issue might be a duplicate of existing issues. Please check: - #11446: New Kimi 2.5 model is giving error about 'reasoning_content' field (CLOSED - fixed) - #11357: JSON Schema validation fails on empty tool parameters {} with Kimi K2.5 (strict mode error) - #11320: [BUG] Kimi K2 Rejects `permissions` Field in Agent Frontmatter - #11053: [BUG] Kimi k2.5 doesn't use the question tool - #11210: Kimi K2 via AWS BEDROCK stops execution - #11229: error when using kimi2.5 (similar JSON Schema issue) - #11128: [FEATURE]: nano-gpt provider - support Kimi K2.5 Your description mentions: - Loops over in reasoning - Fails to call tools - Fires sub-agents then forgets about them These symptoms align with the known issues above, particularly #11357 (JSON Schema validation with empty parameters), #11053 (question tool not working properly), and #11210 (execution stopping). Feel free to ignore if none of these address your specific case.
yindo commented 2026-02-16 18:09:21 -05:00
Author
Owner
Copy Link
Copy Source

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

Can you share your config?

@rekram1-node commented on GitHub (Jan 31, 2026): Can you share your config?
yindo commented 2026-02-16 18:09:21 -05:00
Author
Owner
Copy Link
Copy Source

@O-ELMA commented on GitHub (Feb 1, 2026):

@rekram1-node - yes, sir.

Thank you a bunch for your time and effort.

oh-my-opencode.json
opencode.json
dcp.jsonc

@O-ELMA commented on GitHub (Feb 1, 2026): @rekram1-node - yes, sir. Thank you a bunch for your time and effort. [oh-my-opencode.json](https://github.com/user-attachments/files/24989105/oh-my-opencode.json) [opencode.json](https://github.com/user-attachments/files/24989106/opencode.json) [dcp.jsonc](https://github.com/user-attachments/files/24989110/dcp.jsonc)
yindo commented 2026-02-16 18:09:21 -05:00
Author
Owner
Copy Link
Copy Source

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

@rekram1-node From the current testing situation, suppliers providing services through OpenAI compatible interfaces always have various problems. The essence is the issue of adapting to different suppliers. My personal solution is to provide abnormal response detection as a fallback, and just retry once.

Image
@xiaobluesky commented on GitHub (Feb 1, 2026): @rekram1-node From the current testing situation, suppliers providing services through OpenAI compatible interfaces always have various problems. The essence is the issue of adapting to different suppliers. My personal solution is to provide abnormal response detection as a fallback, and just retry once. <img width="1668" height="462" alt="Image" src="https://github.com/user-attachments/assets/cb839cf0-5e31-4417-9c30-f0404286e769" />
yindo commented 2026-02-16 18:09:21 -05:00
Author
Owner
Copy Link
Copy Source

@Evengard commented on GitHub (Feb 7, 2026):

Is there any news on that? OpenCode is literally unusable right now with NanoGPT's Kimi K2.5

@Evengard commented on GitHub (Feb 7, 2026): Is there any news on that? OpenCode is literally unusable right now with NanoGPT's Kimi K2.5
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#8179
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?