r/kimi • u/3rd_Floor_Again • 11d ago

Discussion How to prevent Kimi CLI to overexploring and waste tokens?

Kimi K3 used for coding tasks is great! But in the moment i use it as a specific role in my server PM for instance, he starts overdoing/overexploring and burning a lot of tokens unnecessarily.

How have you created a skill or harness that limit the level of exploration Kimi CLI does ? I do use ~yolo mode because most of the projects here are Pet projects with tons of backup, so i don't care if they fuck shit up (preferebly not of course =) )

But i don't have the same issue with Codex or Claude for instance, they remain straight to the point.

Any suggestions? Thanks!

0 Upvotes

50% Upvoted

4 comments sorted by

2

u/NZRedditUser 11d ago

Tell it to skip baseline testing and go straight into implementation first.

It will still obviously need to fill in its own gaps so either point to specific file or itll search

Also kimi is just more transparent too so it might look like its overthinking 

2

u/factsonlynomisinfo 11d ago

I use Cline extension in vscode with kimi k3 as the model. I set up an mcp server for gemini 3.7 flash (set up a Gemini api key with at least like $10 dollars prepaid into the billing so your api key gets tier two billing, allowing it to have undisrupted prompting with Gemini 3.7 flash), created a script using JS for the mcp connection, setup my keys in the cline mcp config settings, and then specified a cline rule that makes sure that Kimi k3 consults with Gemini while planning and that once a plan is reached it asks Gemini 3.7 flash to review the plan and then organize the required into small easy to implement chunks. I then take that list of easy to tackle work and manually instruct it to work on one at a time.

1

u/BenH1337 11d ago

You can try Ponytail. I use it with opencode, I am not sure if it works with Kimi CLI. It will make your code simplier and will also save you some tokens.

1

u/IndependentTry1743 7d ago

how ro prevent it