Kimi Code provider: expose reasoning effort / thinking control (K3 low/high/max, K2.7 thinking toggle)
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 19.9k
- Forks
- 2.3k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 30
Description
The Kimi Code provider (kimi, OpenAI-compatible profile, https://api.kimi.com/coding/v1, default model kimi-for-coding) currently offers no way to control reasoning effort in jcode.
Per Kimi's official docs, the current models expose different thinking controls:
- Kimi K3: thinking is always on and accepts a top-level
reasoning_effortparameter with three levels:low/high/max(defaultmax). Docs: https://platform.kimi.com/docs/guide/kimi-k3-quickstart - Kimi K2.7: only supports a thinking on/off toggle, with no effort levels.
It would be great if jcode's effort selection worked for this provider:
- Map jcode effort levels onto K3's
reasoning_effort(e.g.low->low,high->high,xhigh/max->max). - For K2.7, map the effort choice onto the thinking toggle (e.g.
none-> thinking disabled, any effort level -> enabled).
Happy to help test. Thanks!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Kimi provider and jcode's effort-selection mapping; the issue identifies the kimi OpenAI-compatible profile and its API endpoint, but no files or tests. Confirm how K3 accepts reasoning_effort and how K2.7 represents its thinking toggle, then verify that each requested effort maps correctly for both model families.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- ai, api, cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100