Skip to content

fix(providers): advertise the Kimi Code CLI version 2.1.1 - #14842

Merged
diegosouzapw merged 1 commit into
diegosouzapw:release/v3.8.51from
HouMinXi:fix/kimi-cli-2-1-1
Sep 28, 2026
Merged

diegosouzapw merged 1 commit into
diegosouzapw:release/v3.8.51from
HouMinXi:fix/kimi-cli-2-1-1

Conversation

@HouMinXi

Copy link
Copy Markdown
Contributor

Summary

The Kimi Code CLI pin was still 0.26.0. OmniRoute sends that value in X-Msh-Version and User-Agent to api.kimi.com, so every Kimi Code request advertised a client two major versions behind the real one.

Bumped KIMI_CODE_CLI_VERSION to 2.1.1, captured from the CLI on 2026-09-25 (kimi --version prints 2.1.1, kimi upgrade reports already up to date). KIMI_CLI_VERSION still overrides the pin per deployment, so nothing changes for installs that set it.

Test plan

  • tests/unit/executor-kimi.test.ts, tests/unit/kimi-coding-apikey-quota-4435.test.ts, tests/unit/kimi-coding-model-discovery.test.ts: 20/20 pass. The six assertions that pinned 0.26.0 now expect 2.1.1, and they failed before the constant change.

The pinned constant was still 0.26.0, so the X-Msh-Version and User-Agent headers sent to api.kimi.com trailed the real CLI by two major versions. Captured from the 2.1.1 CLI on 2026-09-25 (kimi --version, kimi upgrade reports up to date). KIMI_CLI_VERSION still overrides the pin per deployment.

Signed-off-by: Minxi Hou <houminxi@gmail.com>
@diegosouzapw
diegosouzapw merged commit 20fbc40 into diegosouzapw:release/v3.8.51 Sep 28, 2026
11 of 16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants