Kimi K3 Coming out, Started implanting

[backryun]

No idea why these 2 seperated, I`m working now consolidating these elements into a single window where users can enter their login credentials and API key. Similar to Kiro Provider.

And Kimi Web will implant new models list and new parsing code.

Kimi coding will get upstream logic from CLI 0.26.0. https://github.com/MoonshotAI/kimi-code

It will be completed within a few hours, so you can look forward to it.

[backryun]

I've consolidated the scattered Kimi providers into three.
Kimi Code, Kimi Web, Moonshot AI
The existing Kimi Code Coding API Key has been merged into the connection selection window of the Kimi Code CLI.
And included every single K3 model.
With this improvement, the CLI provider's ban rate will be reduced, and routing will become much more accurate.

[backryun]

Kimi Web perfectly works.

[diegosouzapw]

@backryun -- this is great, and I can see it is already live as PR #7531 (feat(kimi): sync Code, Web, and Moonshot providers). Consolidating the scattered Kimi connections into Kimi Code / Kimi Web / Moonshot AI, folding the coding API key into the Kimi Code CLI connection selector, and pulling the K3 model list in one place is exactly the shape that lowers the CLI ban rate and makes routing more accurate -- so thank you for doing it end to end.

The review happens on the PR itself, so let's keep the technical back-and-forth there (it is UNSTABLE at the moment -- 82 files, +2951/-919 -- so the main thing will be getting CI green against release/v3.8.49; a gh pr update-branch if the base has drifted, and making sure the new provider entries carry the model-registry + tests the provider checklist expects). I will go through it there. Really appreciate you syncing the upstream logic from kimi-code 0.26.0 rather than hand-rolling -- that is the maintainable path. Excellent work.

[diegosouzapw]

Closing this as stale due to inactivity.

Thanks for sharing your progress. I’m marking this thread closed since there has been no follow-up for over 15 days after the last maintainer reply.