[zpljd258]

Summary

Add a dedicated kimi_coding provider for Kimi Coding Plan's Anthropic Messages API endpoint.

Changes

• Register kimi_coding with the Anthropic backend and default base URL https://api.kimi.com/coding/v1.
• Add providers.kimiCoding config support with a separate KIMI_CODING_API_KEY, so it does not collide with Moonshot/Kimi's OpenAI-compatible provider.
• Add provider-level default extra headers and use them from the factory. Kimi Coding now sends the required Claude-compatible User-Agent by default, while user extraHeaders can still override it.
• Document setup in the configuration reference and provider cookbook.
• Add regression tests for the default header and override behavior.

Usage

{
  "providers": {
    "kimiCoding": {
      "apiKey": "${KIMI_CODING_API_KEY}"
    }
  },
  "modelPresets": {
    "kimiCoding": {
      "provider": "kimi_coding",
      "model": "kimi-for-coding"
    }
  },
  "agents": {
    "defaults": {
      "modelPreset": "kimiCoding"
    }
  }
}

If your Kimi account requires a different Claude-compatible User-Agent, override it with providers.kimiCoding.extraHeaders.User-Agent.

Closes #4463

[chengyongru]

Automated PR review by nanobot. This is not a human maintainer review or approval.

Side-effect analysis for adding the Kimi Coding Plan provider:

1. Schema and registry registration — kimi_coding is added as a new ProviderConfig field with default_factory=ProviderConfig, so existing configs without a kimiCoding block are unaffected. The provider spec uses backend="anthropic", routing requests through AnthropicProvider.

2. Separate env key — Uses KIMI_CODING_API_KEY instead of MOONSHOT_API_KEY, correctly separating the two Kimi/Moonshot platforms (Anthropic Messages API vs OpenAI-compatible). No collision risk.

3. User-Agent requirement — The endpoint requires extraHeaders.User-Agent set to a Claude-compatible value (e.g. claude-code/0.1.0) to avoid HTTP 403. This is left to user configuration rather than hardcoded, which is consistent with how other providers handle extraHeaders. Worth noting in docs that this header is effectively mandatory, not optional.

4. Parallel tool call dedup — Since this provider uses the Anthropic backend, the tool_use ID dedup from #4474 applies here. Without #4474 merged, Kimi's parallel tool calls may still collide. The two PRs are complementary but not hard-dependent.

5. README news entries — The diff removes two recent news entries (v0.2.2 release and 2026-06-21 SDK entry) and moves two older entries into the visible section. This appears to be a branch divergence artifact. These README changes should be reconciled with current main before merge.

No blocking concerns on the provider code itself. The README diff may need rebasing.

[chengyongru]

The User-Agent header is effectively mandatory for this endpoint (403 without it). Consider documenting it as required rather than optional, since users who skip it will hit a confusing 403.

[Re-bin]

LGTM. This adds Kimi Coding as a dedicated Anthropic-backend provider with separate credentials from Moonshot/Kimi, clear configuration docs, and CI coverage.

I also pushed a small follow-up so the required Claude-compatible User-Agent is declared as provider metadata and applied by the factory by default. That keeps WebUI key-only configuration usable while still allowing users to override providers.kimiCoding.extraHeaders.User-Agent when needed.