Kimi K2 way better via ACP than via Open AI-compatible route?

[bobosola]

I've just installed the new Kimi CLI which supports ACP and is thus directly callable in Zed in the External Agents list when you create a new AI thread. I also have Kimi K2 installed via the Open AI-compatible route directly to the Moonshot API. Both are using kimi-k2-0905-preview, and both work great for text and agentic use.

But I am seeing much more useful (and very different!) responses when using the model via the ACP interface as opposed to the regular route. I even get very different responses when asking it to enumerate the available tooling. I asked it via Open AI-compatible to suggest improvements to my main.rs. It did a great job in a couple of minutes and came back with some solid suggestions. But when I asked it to do the same via ACP it really went to town over 20 mins or so and massively re-wrote the code for the better, split up main.rs into several more files, added a config.toml, added tests, compiled, corrected bugs, re-compiled, the whole 9 yards.

Is there any reason for this huge difference? I'm guessing it's something to do with the Kimi CLI (via ACP) somehow making better use of the model (thinking mode, context handling, settings etc.)? The difference between the two modes is striking. I just wondered if there any general conclusions to be had here regarding using ACP mode over AI-compatible mode?

The only downside of ACP I can see is that there is as yet no history (though I note you can save the responses as Markdown).

[yodacom]

did you find an answer for this. I am still trying to add Moonshot K2 to my ZED but not having any luck. What is the best approach?

[bobosola]

What's worked for me is:

Set up Kimi CLI

• get a Moonshot API key - you will need to sign in first (I used my Google account)
• save the key somewhere (or to clipboard)
• install Kimi CLI
• run kimi in a terminal
• on the first run it will prompt you for a platform, choose Moonshot AI Open Platform (moonshot.ai)
• at the next screen, paste in your key
• then choose your model. I suggest Kimi K2 Thinking it's now the same price as Kimi K2 0905

Set up Zed
The Kimi CLI link above also has an ACP section further down the page. Copy the example to your Zed settings file. Then if you click for a new AI thread in Zed, you should see an option for a new Kimi CLI thread:

I just wrote a blog entry on vibe coding in Zed with Kimi K2 and the Kimi K2 thinking if you have a spare 5 mins.

[yodacom]

Thank you so much! Will check out your blog. You happy with it? I will see what you say in the blog!

[yodacom]

love your blog post and kickin images!

[bobosola]

Heh, thanks! I'm late to the AI party but Zed and Kimi K2 Thinking is a great combo for the stuff I do without breaking the bank.

[yodacom]

A I is freaking awesome... so much boilerplate is just handled but still need to do a log of debugging on large projects. But it gets better every week! No joke. Estimate it gets you 85% there and then you spend a month debugging it to end up with a finished product the way you want it. At least with code bases of 1,000's of lines of code. All the best, Jeremy Yoda of YodaCom ***@***.*** www.yodacom.com

…

On Wed, Nov 12, 2025 at 4:20 PM Bob Osola ***@***.***> wrote: Heh, thanks! I'm late to the AI party but *Zed* and *Kimi K2 Thinking* is a great combo for the stuff I do without breaking the bank. — Reply to this email directly, view it on GitHub <#41646 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAMMRQPYVKZ6F4RYYWRWTL334O6FFAVCNFSM6AAAAACKY7CO5SVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTIOJVGMYDANY> . You are receiving this because you commented.Message ID: ***@***.***>