The case for keeping kimi-cli (Python) alive alongside kimi-code (Node.js)

[biaks]

Hi team,

I wanted to share some thoughts on the recent shift from kimi-cli to kimi-code, specifically regarding the underlying platform change from Python to Node.js.

Why Python matters
I originally chose kimi-cli specifically because it is Python-based. This is a significant advantage for many of us who work in environments where Python is readily available and customizable, but Node.js is not an option. The ability to easily hack on, extend, and integrate the tool into existing Python workflows was a major selling point.

Different platforms, different use cases
Under the hood, these are fundamentally different platforms. kimi-cli (Python) and kimi-code (Node.js) serve overlapping but distinct audiences. Dropping the Python version entirely would leave a gap for users who rely on its specific ecosystem advantages.

On convergence with Claude Code
I also have a concern about strategic differentiation. If kimi-code is moving to Node.js, it starts to look very similar to the leaked Claude Code project (which is also Node.js-based). This raises a question: what is the unique value proposition of a separate agent if it ends up closely mirroring an existing tool's architecture and approach?

My ask
I believe there is real value in continuing to develop kimi-cli as a Python-native tool. It doesn't have to be the primary focus, but keeping it alive as a maintained alternative would serve a community that specifically needs a Python-based solution.
Would love to hear the team's thoughts on whether there is a roadmap for the Python version, or if the plan is to fully consolidate on Node.js.

Thanks for the great work so far.