NousResearch/hermes-agent
OpenCode Go Kimi K2: thinking and reasoning_effort conflict (HTTP 400)
Cluster 31636 · agent. Data as of
2 open items. Fix attempted, not merged.
The short answer
0open issues
2open PRs
12items grouped
- Known?
- Yes. 12 related items grouped here, 5 issues already closed.
- Fix event
- No fix has been merged to main. 5 PRs closed without merging; see the attempts below.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- 0 issues and 2 PRs.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab task
Most members concern OpenCode Go requests for Kimi K2 models that reportedly include both thinking and reasoning_effort, producing an HTTP 400 error. Several pull requests propose making the two parameters mutually exclusive or omitting one; one also bundles a broader reasoning-fallback feature.
Open issues0
Open PRs2
5 PRs closed without merging
From the close comments: done elsewhere 2 · closed without comment 1 · duplicate 1 · superseded by another PR 1
-
#32292 fix(opencode-go): avoid sending both thinking and reasoning_effort for Kimi K2 · duplicate →
#31637 -
#32794 Fix OpenCode Go Kimi reasoning kwargs · done elsewhere →
03392b6,cb38ce2 -
#35180 fix(opencode-go): drop thinking toggle for kimi-k2 to avoid 400 error · done elsewhere →
03392b6 -
#37446 fix(opencode-go): send either thinking or reasoning_effort for kimi-k2, never both · superseded by another PR →
#34208 - #38020 fix(opencode-go): never send extra_body for Kimi K2 models · closed without comment
Closed issues · 5
- Closed#31636[Bug] opencode-go + kimi models: cannot specify both 'thinking' and 'reasoning_effort' (HTTP 400)
- Closed#32040[Bug]: Opencode Go issue with Kimi-k2.6
- Closed#32223opencode-go: Kimi K2 models fail with HTTP 400 "cannot specify both 'thinking' and 'reasoning_effort
- Closed#32327OpenCode provider sends both `thinking` and `reasoning_effort`, causing 400 invalid_request_error
- Closed#37439opencode-go + kimi-k2.5: HTTP 400 cannot specify both thinking and reasoning_effort
How this cluster was grouped
-
Link evidence (
partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text. - Members outside that structural core may belong to a different underlying problem.
-
Pairwise link density
0.18: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Subsystem
- agent
- Closed issues
- 5
- Attempts
- 5 PRs closed without merging