[Feature Request] Add Cline to the Kimi Code whitelist of supported coding agents

What feature would you like to see?

Summary

kimi-for-coding currently returns a 403 access_terminated_error when called from Cline (VS Code extension by Saoud Rizwan, saoudrizwan.claude-dev). The error message reads:

Kimi For Coding is currently only available for Coding Agents
such as Kimi CLI, Claude Code, Roo Code, Kilo Code, etc.

Environment

Root cause

Kimi Code's backend enforces a client whitelist by inspecting the User-Agent header. Cline currently sends a generic Node.js SDK user-agent, which is not on the whitelist. The identical request succeeds from Roo Code — a direct fork of Cline — which is already whitelisted.

Why this matters

Cline is among the most widely used open-source AI coding agents, with over 56,000 GitHub stars and active enterprise adoption. A large portion of developers who want to use kimi-for-coding are Cline users who are currently blocked with no workaround (aside from switching tools entirely).

There is an open issue on the Cline side tracking this: cline/cline#10307.

Requested change

Add Cline's identifier to the whitelist, so that Cline users can access kimi-for-coding under the same terms as Roo Code users.

Given that Roo Code is already supported and Cline is its upstream, the change on Kimi's side should be minimal — a single entry in the client allowlist.

Notes

• I am not requesting to spoof any user-agent. The expectation is that Cline adds its own stable identifier and Kimi whitelists it officially.
• Cline is open-source (Apache 2.0): https://github.com/cline/cline

Additional information

No response

Search the repository for the client allowlist and the existing Roo Code identifier, then trace how the User-Agent is checked for requests to the coding API. Confirm how Cline's stable identifier will be represented and verify that an allowlisted Cline request no longer receives the 403 access_terminated_error.