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

error when using kimi2.5 #7995

New Issue
Open
opened 2026-02-16 18:08:53 -05:00 by yindo · 6 comments
yindo commented 2026-02-16 18:08:53 -05:00
Owner
Copy Link
Copy Source

Originally created by @pswd123456 on GitHub (Jan 29, 2026).

Originally assigned to: @rekram1-node on GitHub.

Description

JSON Schema not supported: could not understand the instance {}.

Plugins

No response

OpenCode version

No response

Steps to reproduce

No response

Screenshot and/or share link

No response

Operating System

No response

Terminal

No response

Originally created by @pswd123456 on GitHub (Jan 29, 2026). Originally assigned to: @rekram1-node on GitHub. ### Description JSON Schema not supported: could not understand the instance `{}`. ### Plugins _No response_ ### OpenCode version _No response_ ### Steps to reproduce _No response_ ### Screenshot and/or share link _No response_ ### Operating System _No response_ ### Terminal _No response_
yindo added the bug label 2026-02-16 18:08:53 -05:00
yindo commented 2026-02-16 18:08:53 -05:00
Author
Owner
Copy Link
Copy Source

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

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

  • #11053: [BUG] Kimi k2.5 doesn't use the question tool
  • #11134: Using Kimi K2.5 from Fireworks throws temperature related error
  • #8184: Strict JSON Schema validation fail on backends like SGLang (Missing required field in empty tool parameters)
  • #9233: LiteLLM Proxy: Vertex AI Gemini models fail for tools with empty parameters

The error 'JSON Schema not supported: could not understand the instance {}' appears to be related to how empty parameter schemas are handled for tools. Issues #8184 and #9233 specifically address this root cause.

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

@github-actions[bot] commented on GitHub (Jan 29, 2026): This issue might be a duplicate of existing issues. Please check: - #11053: [BUG] Kimi k2.5 doesn't use the question tool - #11134: Using Kimi K2.5 from Fireworks throws temperature related error - #8184: Strict JSON Schema validation fail on backends like SGLang (Missing required field in empty tool parameters) - #9233: LiteLLM Proxy: Vertex AI Gemini models fail for tools with empty parameters The error 'JSON Schema not supported: could not understand the instance `{}`' appears to be related to how empty parameter schemas are handled for tools. Issues #8184 and #9233 specifically address this root cause. Feel free to ignore if none of these address your specific case.
yindo commented 2026-02-16 18:08:53 -05:00
Author
Owner
Copy Link
Copy Source

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

provider: opencode zen free model

@pswd123456 commented on GitHub (Jan 29, 2026): provider: opencode zen free model
yindo commented 2026-02-16 18:08:53 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Feb 1, 2026):

Upgrade to latest, if u are using homebrew then install:
brew install anomalyco/tap/opencode

Instead.

should be fixed

@rekram1-node commented on GitHub (Feb 1, 2026): Upgrade to latest, if u are using homebrew then install: brew install anomalyco/tap/opencode Instead. should be fixed
yindo commented 2026-02-16 18:08:53 -05:00
Author
Owner
Copy Link
Copy Source

@mattgillard commented on GitHub (Feb 5, 2026):

I get the same error (for about a week)
I narrowed it down to an MCP being enabled causes the error.
I am using OpenCode Zen too.

"aws-billing": {
  "type": "local",
  "command": ["uvx", "awslabs.billing-cost-management-mcp-server@latest"],
  "environment": {
    "FASTMCP_LOG_LEVEL": "ERROR",
    "AWS_PROFILE": "xxx/ReadOnlyAccess",
    "AWS_REGION": "ap-southeast-2"
  }
}
@mattgillard commented on GitHub (Feb 5, 2026): I get the same error (for about a week) I narrowed it down to an MCP being enabled causes the error. I am using OpenCode Zen too. ``` "aws-billing": { "type": "local", "command": ["uvx", "awslabs.billing-cost-management-mcp-server@latest"], "environment": { "FASTMCP_LOG_LEVEL": "ERROR", "AWS_PROFILE": "xxx/ReadOnlyAccess", "AWS_REGION": "ap-southeast-2" } } ```
yindo commented 2026-02-16 18:08:53 -05:00
Author
Owner
Copy Link
Copy Source

@shaunpatel commented on GitHub (Feb 9, 2026):

I'm having the same issue even without any MCPs.

@shaunpatel commented on GitHub (Feb 9, 2026): I'm having the same issue even without any MCPs.
yindo commented 2026-02-16 18:08:53 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Feb 9, 2026):

@shaunpatel which provider and which version

@rekram1-node commented on GitHub (Feb 9, 2026): @shaunpatel which provider and which version
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 bug
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#7995
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?