Cairn

Kimi thinking/reasoning parameter handling fixes

NousResearch/hermes-agent · cluster 18823 · agent

Data as of

Nothing open on GitHub. Fix merged in #67391. Check it covers your case.

The short answer

0open issues
0open PRs
5items grouped
Known?
Yes. 5 related items grouped here, 2 issues already closed.
Fix event
A fix was merged to main in PR #67391. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
Nothing open on GitHub.

Multiple issues and fixes addressing how thinking, reasoning_effort, and related parameters are sent (or incorrectly blocked) for Kimi and Kimi-coding Anthropic endpoints. The work spans guard clause scoping, parameter forwarding, and adaptive thinking behavior.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #67391 fix(anthropic): preserve signed thinking blocks on Kimi-family replay (#66948 salvage)

    merged to main

    files: agent/anthropic_adapter.py, contributors/emails/[redacted:email], tests/agent/test_anthropic_kimi_signed_thinking_replay.py

2 PRs closed without merging

From the close comments: closed without comment 1 · superseded by another PR 1

  • #18898 Enable thinking/reasoning for kimi-for-coding via anthropic_messages · closed without comment
  • #56730 fix(anthropic): scope Kimi thinking guard to /coding endpoint only · superseded by another PR → #67228, #13848, #67391, #56727
Closed issues · 2
  • Closed#18823Kimi Coding: reasoning_config ignored due to _is_kimi_coding guard — thinking parameter never sent
  • Closed#56727Kimi /coding endpoint thinking is incorrectly blocked (was PR #49143)
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.34: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means 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 Lab

At a glance

Subsystem
agent
Merged PRs
#67391
Closed issues
2
Attempts
2 PRs closed without merging
Fix link checked
19 Jul 2026

For your agent

The same facts, typed.

cluster/18823.json
cluster/18823.md