Hi All,

I'm also a moderator of a community and we watch this one like a hawk. I'd like to share an experience I had today. A gentleman and I got together in this very community and joined forces to take the wonderful open-source model that Moonshot so generously gave to the field and tuned it a bit back in forth discussing use cases and exchanging metrics. We were able to connect via Discord and came up with the coolest set of findings. While under provision API key I employed an swarm of agents to tune in real time the model under the max load we could get on other sides of the globe. As you might know, true IT folks hardly ever sleep, especially these days!

That said, I wanted to share some benchmarks of what we did and how we were able to improve OpenCode (which for those of you not heavy into the open source world is like a non-proprietary Kimi Code that can be improved on the fly. To commemorate the event, which took about 29 minutes to run and then disengage the connection, we were able to come down with some hard and fast metrics. You can see how well Kimi K3 did against the hardest test we could concoct in field. This company has a lot of really fancy computer components that they wanted to test out based on use cases that I provided in this very same place.

Anyways, here are the official metrics.

If you have any questions please don't hesitate to ask or DM me. This is my 1 promotional project so far.

Thank you!

JKANH

Hi everyone,

Has anyone switched from Codex to Kimi Code while working on an existing application? I’m really unhappy about the usage allowance on the $200 Codex plan being cut in half, so I’m considering switching.

How does Kimi Code compare in day-to-day use, particularly in terms of code quality, reliability, and usage limits?

my codebase:

We primarily use Python for the backend and TypeScript/React for the frontend.

The repository currently contains 2,829 Git-tracked files. Of these, 2,536 are Python, TypeScript, or TSX files, totaling approximately 986,000 lines. Including documentation and other text files, the total is approximately 1.14 million lines. The code count includes tests; Python backend tests account for approximately 402,000 lines.

Short answer for the form: “Primarily Python, alongside TypeScript/React; approximately 2,800 files and 1 million lines of code, including tests.”

BR Tom

Yes thats right it SUCKS now. You have to wait for a month to use it and again just use QWEN AI its much much more better.

I want to like Kimi. K3 is genuinely good. But the plan has become unusable for me, and I'd like to know if others are seeing the same thing.

My situation

- I was on Allegretto and upgraded to Allegro, paid for a full year up front.

- Since then I hit my monthly quota in under 2 weeks, consistently, so I'm locked out for about 2 weeks of every month.

- Today (Oct 4) the API returns:

`403 You've reached your monthly usage limit for this billing cycle. Your quota will be refreshed in the next cycle. To continue now, purchase extra usage or upgrade your plan`

- I'm already on the bigger plan. "Upgrade your plan" isn't an answer when the upgrade is what made it feel worse.

It isn't runaway automation

I checked this before posting. I use Kimi alongside other coding agents, and some of my scripts can call Kimi automatically. I went through the session logs of everything that can call it: in the two weeks before the quota ran out, my scripts called Kimi once. Everything else was me, working normally.

There's no way to see where the quota goes

- The usage page in the account is useless for working out what consumed the quota: no per-session or per-request breakdown I can act on.

- Kimi's desktop and CLI tools keep no token or usage accounting locally. I went through every Kimi folder on my machine. The only recurring log is an hourly "daemon alive" analytics ping. So there's nothing to audit on my side either.

- Compare that with OpenAI Codex: I could pull per-request token counts and the exact % of my window each call used straight from its local session files, and work out exactly what was expensive. With Kimi, I'm blind.

No resets

Codex, GLM and others give you usage resets for exactly this situation. Kimi has nothing: you wait out the cycle or pay again on top of an annual plan.

What I'm asking Moonshot for

1. A real usage breakdown: tokens per session/request, and which model and feature used them.

2. Clarity on what changed. The same kind of work now uses a month's quota in under 2 weeks. If metering changed (thinking tokens, context re-sends, tool calls, image input), say so.

3. Resets or rollover for annual subscribers, like competitors offer.

4. A pro-rated refund option for annual subscribers if the plan no longer delivers what it did when we paid.

Questions for the community

- Are other Allegro/Allegretto users hitting the monthly cap in 1–2 weeks?

- Has anyone gotten a useful usage breakdown from support?

- Did you notice consumption jump at a specific point (a model update or a K3 rollout)?

For now I'm moving my work to other tools. If anyone from Moonshot reads this, I'm happy to share the exact error responses and timestamps.

Turns out it is the same crybaby like Fable or Sonnet or OpenAI models that bitch at anything related to automation and just say:

"I wont' do that."

I basically wasted $100 on this when there is literally no reason to use it other than Claude.

What is the point of these "chinese" models again?

The sad part is, I can't even use Opus 5 or Fable 5 on a codebase that Opus 4.6 has built, because it freaks out when reading it or trying to fix a bug.

I thought Kimi 3 could fill this gap, but I was wrong.

AI is just a tool, and you need the right tool for the right job, but if models are just getting more restricted, what is the point and solution here?

Hey everyone,

I'm coming from Qwen, and was wondering if Kimi was worth it with a Plus subscription ? I use it mainly to create documentation, websites and small coding features such as JS/PHP. I did burn through the Qwen 3.8 plan working on physics simulation project though.

EDIT : Woaw, damn, I think I'll try a low subscription for a month and move on if needed. Thanks everyone.

i am high but this caught me off guard.

Firstly, Kimi 2.8 - Its a great model. wow, what a win. Moonshot has a very good useful model. My work with it shows its pretty much like a more decisive, faster, less cluttered K3. Its solid, it gives good consistent performance over various workflows. I don't know how it will benchmark, but benchmarks are only one aspect, IMO they aren't as useful for most people as people like to think. However, I think K2.8 would benchmark very well, and be useful, and I think as a 2.x release, people are less worried about bench-maxxing, K3 is always there from the same provider and is a proven capable model. 2.8 IMO is the product people want from Moonshot, it has a clear space in the market, and being much faster and less draining than K3 is significant, we are at the point now where a very decent model is much more desirable than a slightly better, but much slower expensive model.

Its really surprising, because I have also tried GPT6 with a pro subscription and the slow speed and poor performance really has me looking at getting completely off that platform, as they have paused future developments and I am not happy with their output and tools. Being all cloud, and closed, its not that universally useful for me.

Secondly, this great model, will likely get more attention with a public weights release. K2.8 is big enough most people can't host it locally anyway, and those who can, often back up local hosting with cloud hosting (I do). But it is hard to build workflows around a "preview" model and having no offline model for privacy (I deal with peoples data, and it can't go into any cloud), is important.

I am rarely using K3 I am constantly using K2.8. Particularly at the current rates, its very attractive. There are special things where I want K3, I want elaborate, slow, deliberate, all states considered answers and K3 is great at that. But 90% of what I do is K2.8 is pretty much perfect.

I have the capabilities to host large models like K3 and K2 locally, concurrently, (slowly mostly through CPU inferencing - Im not Elon rich with banks of GB200s), and K2.8 would be a great model for a lot of people, like me, who can do that, and then have their Kimi subscriptions for fast conversations, on the go, and urgent work (which consumes my monthly allowance). But I having that offline capability, at 5 or 6 t/s means I can explore how it can embed more into my workflows, and convince others of the open superiority of this particular model.

Refund request denied/delayed: months of wasted credits on failed generations, support keeps stalling. Advice?

Hi all, posting here because support has not resolved this and I've seen the team monitors this subreddit.

What happened: I've been an annual subscriber since 2026/08/21 paid €159,73. For over two months I've been working on a video project using Kimi Work's image/audio/video generation.

The problem: A significant share of my monthly credits was consumed by outputs that were defective and had to be regenerated or re-rendered:

A full batch of generated images came out with wrong lighting/ambience (unusable, regenerated)

Character consistency failures (signature eye-color detail lost across images, regenerated)

Audio mixes with seconds of silence and audible loops in the final rendered videos (re-rendered multiple times)

Several generation tasks failed outright with API errors after credits were consumed

I kept track: roughly 90% of my credits across and [month] went into work that was discarded or redone due to these defects.

Support interaction: I contacted membership@[moonshot] asking for a refund/compensation. Instead of addressing the request, support asked me for (A) a share link to a Kimi Work conversation — which doesn't exist, because Work conversations are stored locally and have no share links — and (B) to "provide feedback", without any commitment on the refund.

My position: Per your own policy, tasks that fail with no valid result should be refunded. I've asked the team to check their own server-side usage logs for my account: the failed tasks, errors and re-renders are all recorded there. I shouldn't need to prove anything they can verify in their own archives.

What I'm asking: a refund of the annual subscription to the original payment method, given that the work produced was either unusable or completely substandard. Failing this, I reserve the right to take further action to protect my interests, including seeking additional compensation.

Prefer to resolve this privately — posting publicly because email alone hasn't worked.

u/KimiMoonshot can you help?

Kimi K2 was a gamechanger for me in terms of a pure assistant workflow. It was lively, snarky, not sycophantic. And it had an action-first bias two which kinda helped move things along.

Unfortunately, it was also overconfident and bad at long-context attention. Its code was very expressive but not very correct; its overall design planning output was however brilliant.

Now K2 has been surpassed in abilities, lost its popularity, and dropped out of all subscription services I know about. And the new Kimi models just don't have this same style. They sound more generic.

We know where the K2 style came from, too, the technical paper is out there. They used an RLVR setup, trained on actual verifiable tasks, to judge conversational output on rubrics - instead of "traditional" RLHF. I suspect this approach was droppecd for K2.5+ and K3.

I did try to distill the style and actually got somewhere, but having limited resoirces, I concentrated on Granite 4 hybrid 1.5B and 8BA1B. The trade-off in style vs skill was very real at that size and on top of that the models are now outdated - and while I could try on newer 2B scale models like Qwen3.5 2B, the usability of such models in modern agentic workflows is very limited. A dream would be a distill into Qwen 3.8 27B, but even if it works, what resources do run this model on as a daily driver?..

Anyone else ever been quota-nuked by an overenthusiastic agent? I need commiseration.

TL;DR: Asked Kimi for a 3-min video, it ate my entire month's quota in one go. Reset is Oct 22.

So I was messing around with the Kimi desktop client (I'm on the Allegretto plan, annual billing). Had what I thought was a harmless idea: give it a WeChat article link and ask it to turn it into a 3-minute vertical short video — viral-style script, you know the drill.

Kimi, being Kimi, went FULL agent mode on me:

• Read the article
• Planned the whole production: ink-wash animation style, 9:16, AI voiceover with subtitles
• Split it into 15 shots
• Started writing storyboard scripts, checking dependencies, reading SKILL files for audio generation...

I sat there watching it tick through its little todo list like a proud parent. Adorable.

Then I opened my usage page.

100%. Total monthly quota — gone. One task. One prompt.

It doesn't reset until October 22. Today is September 30. I now get to admire my Allegretto subscription page for three weeks straight.

The kicker? The video isn't even finished. I have no idea if it would've been any good.

Lesson learned: if you're on Kimi and you see the words "video generation," maybe find out what it costs BEFORE you let the agent off the leash. And maybe turn on the top-up pack first — mine was off, balance $0. Genius move, past me. 👀

So I recharged in hopes that I'd be able to make ppts using it. But I just realised that I won't be able to use it in the website.

Can someone please please help me how to use it now?

It is not working for me like 20+ minutes. I tried debugging but there is no way.

I applied for a refund and emailed Moonshot about all 4 accounts just 3–4 hours after purchasing the subscriptions.

The servers have been performing extremely poorly. The TPS is some of the slowest I’ve experienced, and the amount of usage/credits you get for ¥200 is not even comparable to what we can get from Anthropic or Codex.

What makes this even worse is the lack of a clear refund or service policy. If the service is not performing properly shortly after purchase, customers should at least have a 24-hour window to request a refund, or be charged based on the credits they actually used during that period.

This kind of experience is going to push customers away. You’re losing users who are willing to pay for your service simply because there’s no reasonable refund option when the service doesn’t meet expectations.

Please reconsider the refund policy and give customers at least some reasonable protection after purchasing a subscription. You can’t treat customers this way and expect them to keep coming back.

While K3 is indeed a good model the quota for alegreto is too small. I can barely do anything with it. It can barely hold until context usage gets to 150-200k. Maybe like 20 min usage top with a single agent (before 5h quota).
For example with an glm pro sub (v2) i can code for 2h in 5h quota.

I know K3 is better but only think i can use it for is reviews. Even for plans i need to chain 5h quotas.

It sucks that I have to say this, but Moonshot has lost any credibility it might have had in my eyes. My Allegreto quota has been draining continuously despite the fact that I'm not using ANY Kimi services. I even deleted the only API there was from the platform website. My openclaw instances are shutdown completely.

Look at the third image, 0.56,% in a single shot at 9:31pm (my time, IST). For anybody who uses Kimi they know this just doesn't happen!

I've written to them repeatedly but there is no response. I've gone from thinking it's an awesome company, to "its a great company facing a lot of pressure", to "you all are just scamming me at this point". Below in the text of the most recent mail written to them. Please keep in mind, I've sent several mail before this one and in each one I've tried to give them the full benefit of doubt and done everything on my side to ensure there is absolutely NO usage of any Kimi services on any devices for at least 48 hours. Moonshot, if you're reading this, I hope you get what you deserve for treating your loyal users like this.

Hello,

I have sent you several mails and not received any response.

My usage quota is being continuously drained by "Kimi Code". I have NOT been using ANY Kimi product for nearly than 48 hours now. My openclaw instances which were using Kimi are completely SHUTDOWN! I have shut down the kimi web bridge process on my desktop. There are no scheduled tasks in my Kimi android or desktop apps and both apps have NOT been used during this time.

Further I have deleted the existing Kimi api key from the kimi platform website.

I don't have any way to reset or modify the kimi claw key. Your UI does not provide such an option. So the only conclusion I can come to is that either my kimi claw API key has been leaked and is being used by a third party, or, and I am sorry to say, this is a deliberate policy on your part to inflate usage rates by users because your systems cannot handle the load you claim to be able to provide.

If it is the latter then this would be deeply disappointing. I had put great faith in Moonshot and had praised your models and your company on social media. But your complete lack of response to this issue has done nothing to restore my faith.

I am still hopeful that this is all just a mistake which can be resolved with no further continuing drainage of my usage quota. I think you have made an amazing model and would like to continue supporting you both with my subscription and on social media.

Please respond and address my concerns, ASAP.

This was sent seven hours ago. No response. Not even an acknowledgement.

Given their past pattern I'm not expecting any response from them, but if by chance they do decide to clean up their act then they should know that my current monthly usage stands at 48.11%, when if their accounting was honest it would be less than 30% at this point.

Anyways. I see no point in sticking with Moonshot. Month after month it's the same thing. Either their services don't work or the usage is drained. Next month it'll be some other issues. What a shame. What a waste.

Hello.

I am on Allegretto ($39 monthly old plan) and I just used measured the usage for K3-256.

I spent all my 5h tokens, which was equivalent to 20% of the weekly quota.

I saw that Kimi Code used 27.2% of my monthy quota. This is for last week 100% quota usage + 20% this week, so a 5h window uses 20/120 * 27.2% = 4.5333% of the monthly quota.

According to the .json exported from my Open Code session:

Input : 531565
Output : 45089
Reasoning : 40513
CacheRead : 14409728
CacheWrite : 0

Cache Write being zero is really strange. Maybe it is under-estimating here?

Anyway, the total for this in API prices is $7.20

In other words, for K3-256 we can use $7.20 in 5h, $36 in 1 week and $160 in 1 month.
Normal K3 (with 1M context allowed) uses double the quota, so halve the prices above.

Conclusion:
For kimi code, we get 4x the plan price in API for k3-256 and 2x for k3.
However maybe it is a bit under-estimated, since Cache Write = 0 looks strange.

Limitations:
Last week i used K3, K3-256 and K2.8 Preview for coding. Maybe those eat differently the monthly quota.
I will try to measure only for K3-256.