Fix：Add KimiExecutor to fix the error of reasoning_content is missing in kimi thing mode

[bypanghu]

Summary

• Describe the user-facing or operational change.

Related Issues

• Closes #
• Related to #

Validation

• npm run lint
• npm run test:unit
• npm run test:coverage
• Coverage is still >= 60% for statements, lines, functions, and branches
• SonarQube PR analysis is green or any remaining issues are explicitly documented below

Tests Added Or Updated

• List every changed or added automated test file.
• If no production code changed, state that here.

Coverage Notes

• If this PR changes src/, open-sse/, electron/, or bin/, explain which tests cover the change.
• If coverage moved down in any touched file, explain why and what follow-up task will recover it.

Reviewer Notes

• Call out any risky areas, migrations, feature flags, or manual validation that reviewers should know about.

[gemini-code-assist]

Code Review

This pull request introduces KimiExecutor to handle Kimi-specific request transformations, specifically ensuring reasoning_content is present in tool calls when thinking is active, and registers it under the "kimi-coding-apikey" alias. Feedback highlights a bug in applyKimiRequestDefaults that bypasses general provider defaults, incorrect provider registration and constructor arguments in index.ts, and a violation of the repository style guide due to missing unit tests for the new executor.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

In applyKimiRequestDefaults, if Kimi thinking is active and tools are present, the function immediately returns the result of ensureToolCallReasoningContent and completely bypasses applyProviderRequestDefaults. This means any other configured request defaults (such as temperature or max_tokens) will not be applied.

Furthermore, if thinking is enabled via the defaults rather than the initial request body, hasActiveKimiThinking will evaluate to false before the defaults are applied, missing the opportunity to inject reasoning_content.

To fix this, apply the provider request defaults first, and then perform the Kimi-specific check and transformation on the resulting object.

function applyKimiRequestDefaults(body: unknown, defaults?: JsonRecord | null): unknown {
  const withDefaults = applyProviderRequestDefaults(body, defaults);
  const record = asRecord(withDefaults);
  if (record && hasActiveKimiThinking(record) && hasTools(record)) {
    // 此处 kimi 开启了 thinking 功能且存在工具调用，确保 tool_calls 中包含 reasoning_content 字段以兼容老版本 Kimi 后端的要求
    return ensureToolCallReasoningContent(record);
  }
  return withDefaults;
}

[gemini-code-assist]

Currently, "kimi-coding-apikey" is registered using new KimiExecutor(), which defaults the internal provider name to "kimi-coding". This means any provider-specific checks or configurations matching "kimi-coding-apikey" will not be correctly resolved within the executor instance.

Additionally, the "kimi-coding" provider itself is not registered to use KimiExecutor, meaning it will not benefit from the reasoning_content fix when thinking mode is active.

To resolve this, pass the correct provider name to the constructor for both "kimi-coding" and "kimi-coding-apikey", and register both to use KimiExecutor.

Suggested change

	"kimi-coding-apikey": new KimiExecutor(), // Alias
	"kimi-coding": new KimiExecutor("kimi-coding"),
	"kimi-coding-apikey": new KimiExecutor("kimi-coding-apikey"),

[gemini-code-assist]

According to the Repository Style Guide (Rule 9), tests must always be included when changing or adding production code in open-sse/. Please add unit tests for KimiExecutor under the tests/unit/ directory (per Rule 1) to verify the request transformation and reasoning_content injection logic.

References

1. Rule 9: Always include tests when changing production code (src/, open-sse/, electron/, bin/). Rule 1: ALL unit tests, integration tests, ecosystem tests, or Vitest files MUST strictly be placed within the tests/ directory. ^(link)