Moonshot AI model for Cline
Try Kimi K2.7 Code in Cline
Available in ClinePass
Kimi K2.7 Code is available in Cline. Choose Cline (usage-billing) or ClinePass as the provider, select Kimi K2.7 Code, and use it for scoped implementation tasks where Cline can inspect the repository, edit files, and run the relevant checks.
Best for
- Implementing a feature from an existing issue or specification
- Repairing a failing test suite and explaining the underlying defect
- Reviewing a focused patch for correctness and missing edge cases
Limitations
- Give it acceptance criteria and a bounded file area; vague repository-wide requests are harder to verify.
- Generated changes still need the project's formatter, type checker, and tests before they are accepted.
Set up in Cline
Choose the surface that fits your workflow: use the Cline IDE extensions, run Cline CLI in your terminal or CI, or configure the model in scripts and products with the Cline SDK. Then complete the provider-specific steps below.
- Sign in to your Cline account in the Cline IDE extension or CLI.
- Choose Cline (usage-billing) provider, or subscribe to ClinePass to use ClinePass provider.
- Select Kimi K2.7 Code from the model list and start with one of the example tasks below.
Example tasks
Use these as starting prompts and adapt them to your repository.
- Task 1: Implement cursor pagination for the activity endpoint, update its types, and add tests for the first and final pages.
- Task 2: Review the current branch against main and fix only correctness issues that can be demonstrated with a test.
Frequently asked questions
What is Kimi K2.7 Code best used for in Cline?
It is best suited to code generation, patch review, test repair, and other tasks with concrete implementation criteria.
How should I prompt Kimi K2.7 Code?
Name the desired behavior, relevant files, constraints, and checks to run so the result can be verified inside Cline.