MoonshotAI / MoonshotAI/kimi-code

子模型的思考模式无效

Open
#3,261 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
TypeScript
Stars
7.5k
Forks
1.2k
Avg merge
11h 53m
Merged PRs (30d)
350

Description

What version of Kimi Code is running?

0.38.0

Which open platform/subscription were you using?

OS: Windows

Which model were you using?

opencode/deepseek

What platform is your computer?

x64

What issue are you seeing?

Kimi Code CLI version: 0.38.0
OS: Windows

Problem:
A global [thinking].effort is automatically written into config.toml
when switching the main model through /model. This globally overrides
default_effort configured for aliases in [secondary_model.models].

What steps can reproduce the bug?

Steps to reproduce:

  1. Define two aliases for the same model:
    • one with default_effort = "low"
    • one with default_effort = "high"
  2. Add both aliases to [secondary_model.models].
  3. Configure:
    [thinking]
    enabled = true
    and omit the effort field.
  4. Start or reload the TUI.
  5. Switch the main model through /model without explicitly changing
    the thinking effort.
  6. Check config.toml.

Actual:
[thinking].effort = "xhigh" is written back automatically.
Subagents then use the global xhigh value instead of their alias-level
default_effort.

What is the expected behavior?

Expected:
Switching the main model should not create a global thinking.effort
unless the user explicitly changes the global default. Per-model
default_effort variants in the secondary model pool should continue
to work.

Additional information

No response

Contribution
  • I am willing to submit a PR for this bug fix myself (please wait for maintainer approval in this issue first)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue with config.toml, [thinking], [secondary_model.models], and the /model command described above. Trace the configuration update performed when switching the main model, then verify that an omitted global effort remains omitted and that aliases with low and high default_effort retain their respective behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.