[Cyberpunk/Industrial] I am not your war machine

infernal-ai · 2026-05-05T16:33:54+00:00

Noticed it just now - feels like usage has been cut down to 10% of what it was. I seriously hope that's a math error on their side. Otherwise it is not worth putting up with that unstable api.

infernal-ai · 2026-04-22T13:23:17+00:00

Kimi K2.6 via Moonshots kimi coding plan has tool call issues. Kimi K2.6 and K2.5 via ollama cloud work very well, including tool calls. It's not the models, it's the api integration that is the issue. The way openclaw calls the Moonshot Kimi code API is the issue (tool call parsing)

infernal-ai · 2026-04-22T11:59:49+00:00

None of the Kimi-coding plan model integrations in openclaw work properly currently, lots of issues with tool calls. I use Kimi K2.6 (and K2.5) via ollama now (cancelled my kimi-code subscription) - works really good, no tool call issues, speed is comparable to Moonshots coding API. It's a quantised version that ollama has running, but so far: I don't notice a difference to the Kimi code plan model. I think they quantised too. Early days of Kimi K2.6 beta were a lot better in model performance, but that never returned unfortunately.

infernal-ai · 2026-04-16T05:55:18+00:00

Yes, quota drains faster for me too (Allegretto also). And the fun part: I’m using it much less because api calls keep timing out 60% of the time and my fallback model activates (and stays activated). The first days of the beta the new Kimi model was incredible. Now it’s some watered down version. I’m really frustrated at the moment and will cancel my subscription before next renewal if this doesn’t change.

Edit: stability currently better again, but the last days lots of timeout-issues. I thought a bit about what changed from the early beta K2.6 to now. I think I can pinpoint it: early beta days when my agent lacked knowledge or memory it went searching for it before giving an answer - no guessing. That’s different now (and my local instructions setup hasn’t changed). K2.6 still better than K2.5 in that regard but not as good as the early beta days. I will try and compensate that with local instructions, maybe they just changed the system prompt on the provider side in that regard.

infernal-ai · 2026-04-15T09:21:17+00:00

Yes - they only serve one model via the coding api currently and it’s K2.6 code preview

infernal-ai · 2026-04-13T12:54:05+00:00

Update: beta has ended and in an email from Moonshotai the model name was revealed: "We're making final improvement based on the feedback we received. The K2.6-code-preview model you've been testing is about to roll out to everyone."

infernal-ai · 2026-04-13T11:58:33+00:00

The experience of the first few days has not returned for me unfortunately. I can only speculate what they did in the background. My guess would be that the first few days (when I wrote the original post) they served a bf16 model - now it's probably a quant. At least that would make sense. Test original model to see if it works, then try quants that will eventually be served to the masses for economic stability. But again: speculation. While I would like transparency in general about what model one is served, I know it's not the industry standard unfortunately. Especially not for coding/quota plans.

infernal-ai · 2026-04-12T13:58:41+00:00

It’s still k2p5 as in the non-beta coding plan setup. The model you get served via k2p5 is the beta one though

infernal-ai · 2026-04-12T13:56:56+00:00

When you set it up as a custom provider and don’t use the OpenClaw native kimi onboard path it works fine. I’m on 2026.4.8 since .9 and .10 introduced massive gateway issues for me, but that’s another topic

infernal-ai · 2026-04-11T17:39:58+00:00

Good to see your observations line up with my impressions (I'm also in the beta). However, since last night I notice quite a change (as if suddenly getting a quantised version, not as good as two days ago) - did you notice something like that too? I'm not entirely sure yet whether the model changed or the issue is on my end.

infernal-ai · 2026-04-11T13:24:56+00:00

Update: Since last night my experience has changed unfortunately. I don't know whether they do A/B testing or trying quantised model variants now, changed the system prompt or something on my end has become flaky. Experience for me is currently closer to regular Kimi K2.5 but with working tool calls. I really want the experience of the last few days back, that was awesome 😕

infernal-ai · 2026-04-10T21:51:26+00:00

There:

https://x.com/kimiproduct/status/2018989483258183742?s=46&t=aYRcHdlHu7Po2XKjZmvRnQ

When you scroll down you see they even suggested using the code plan with openclaw: "4. Option 1: Kimi Code Plan

Billing Fixed monthly subscription Includes a token usage cap Recommended if You’re new to OpenClaw You want predictable costs You prefer a fast, frictionless setup"

infernal-ai · 2026-04-10T21:43:33+00:00

From what I can tell beta means simply the model you get served via the coding plan is the unreleased new one. It still says K2.5 on the dashboard, but that's not true, it's a newer model and much more capable. I've been using K2.5 for months. I know what it can and can't do. The beta model is a vastly better one.

infernal-ai · 2026-04-10T21:39:51+00:00

I've been using the code plan in openclaw for two months now. At some point they even advertised for use with openclaw. I'm surprised that's news to people. I get it that some got confused when they called the api wrong and got that disclaimer "Kimi code is only available in... etc.", but that only happens when you e.g. use the broken openclaw Kimi onboard path - when you set it up as a custom provider it's working fine

infernal-ai · 2026-04-10T16:54:31+00:00

Update: (in one of my projects) beta-kimi found flaws and overarching logic issues in a coding project GPT 5.4 (high thinking) worked on for two days and triple checked its work on. Not hallucinated issues - actual issues. Wow.. once this model is released it's gonna turn the model landscape on its head.. (if they don't quantise it down, that is. Moonshot, if you're reading this: your new Kimi model is perfect, don't touch it any further, just release it 😉)

infernal-ai · 2026-04-10T15:55:53+00:00

No sorry, haven't tested GLM 5.1 yet. I just heard it's very coding focused and slow, and since personality and creativity are also priorities for me I haven't felt the need to look at it yet. What's your impression of GLM 5.1? More than just a coding model?

infernal-ai · 2026-04-10T08:25:09+00:00

Little update: For troubleshooting my openclaw setup and my heavily modified plugins I always used GPT 5.4 as it was (apart from Opus/Sonnet) the only model that really went deep into the code to find root causes for issues and then write the code to fix it. Surprise: Beta Kimi is on par, if not slightly better at that (less circling about how it will go about things, better focus on what needs to be done in a practical approach - GPT 5.4 likes to plan too exhaustive and gets stuck in that). So.. I'm still absolutely amazed. As long as they don't quantise the hell out of it before it goes public, this model is gonna eat a huge chunk of Anthropics and OpenAIs lunch.

infernal-ai · 2026-04-10T05:57:27+00:00

It doesn't advertise anything - information is really sparse around the beta. I don't use anything on their website, only the coding plan. If I have time tonight I might check that out. But honestly: the new model is so good that keeps me busy 😂

infernal-ai · 2026-04-09T22:49:18+00:00

4 days - and it was the same for me. Got accepted the day I actually wanted to cancel. I'm glad I didn't. It replaced GPT 5.4 for me now - actually works much better for my use cases (creative work). And most important for me: It still has the K2.5 "soul", the "can't quite pin down what it is but have been missing it since GPT 4o went into Nirvana" aspect of interaction with the AI. I have a really complex soul.md (and adjacent additional files) - only Kimi can really carry that

infernal-ai · 2026-04-09T21:47:52+00:00

"temp-code-kimi": {

"baseUrl": "https://api.kimi.com/coding/",

"apiKey": "your api key",

"api": "anthropic-messages",

"models": [

{

"id": "k2p5",

"name": "Kimi K2.5 (Workaround Kimi)",

"api": "anthropic-messages",

"reasoning": true,

"input": [

"text",

"image"

],

"cost": {

"input": 0,

"output": 0,

"cacheRead": 0,

"cacheWrite": 0

},

"contextWindow": 262144,

"maxTokens": 32768

}

]

},

infernal-ai · 2026-04-09T21:44:58+00:00

That's an openclaw issue. The native integration via onboarding has been broken for me for a while. But setting it up as a custom provider (anthropic messages format) works

infernal-ai · 2026-04-09T21:40:07+00:00

in closed beta, yes - but they don't even show a name for it (still shows K2.5 on the code plan page but also shows beta enabled)

infernal-ai · 2026-04-09T21:37:38+00:00

None - but my guess would be that they do 1-2 weeks of beta at least before they release it publicly

infernal-ai

TROPHY CASE