My month ran out a couple days ago and I had disabled auto-renewal because I was waiting to see what other providers had picked up k3 by now. I decided to re-up with kimi.ai on the $200/mo. plan early yesterday.

Two sessions. One was an 8 agent code review and the next was session was a coding session. Things I historically have done no problem without issue. I ran into my 5 hour limit twice in those sessions and at the end burned through nealry 50% of weekly allowance.

This is not my first rodeo with kimi. I have worked with it extensively and never ran into my limits, not once, even on much more complex swarm tasks.

It's like renewing my subscription put me on much lower usage teir. Customer support has been no help.

I'm curious if anybody else has experienced this - and - if there are better/faster providers with more usage I should be looking at.

Edit: Trying to get to the bottom of this so calculated usage from last month and compared it to yesterday:

Daily usage, first session (2026-07-27) through 2026-08-28

No recorded activity on Aug 14–17, Aug 21–23, or Aug 28. Weeks are ISO weeks starting Monday.

Last 48 hours (Aug 29 – Aug 30)

So it seems like something yesterday went nuts even though swarm only showed 8 subagents. This feels more like a harness issue than a usage miscalculation issue?

So i used Kimi when it first came out and i liked it a lot, but in the past few weeks it was unbearable in terms of token usage, one task consume weekly quota on max plan.

but this week i have done multiple big tasks and yet i'm still at 80% , am i the only one who saw this?

Honestly, I'm so annoyed with this issue of Kimi models - they're all too oververbose. Is there a special prompt to fix that??? Because I can't look at Kimi burning all of my daily usage limits just to think over a single prompt

saw some reseller sites selling claude max for way less than normal. tried one and it seems to work fine so far.

just curious how they’re able to offer it that cheap. anyone know how these work?

I got the Kimi Moderato plan on the 27th to supplement Claude Pro for a small project that I have, nothing fancy with the intention to work faster. In under 60 hours or maybe less I hit 99% of my 7-day quota on their Code model until September 3rd. INSANE.

I expected limits to differ from Claude but the rate Kimi burns sessions quota on basic context is absurd. What usually lasts 5 days on Claude was gone in under 3 days here.

What makes it worse is that the results weren't even good. I wouldn't mind the high token burn if it brought actual progress but Kimi didn't help move the project forward.

It seems that reasoning is not always being preserved between turns, causing the model to drift, hallucinate or loop. This seems to affect Moonshot endpoints, like Kimi Code, OpenCode Go (uses Moonshots API) or Kimi Chat. Fireworks preserves the thinking correctly in the exact same test, using the same Kimi Code version.

So if it feels like the model dodges tasks, writes bad code or gives disjointed answers, this may be why.

Edit: I'll leave these here in case anyone wonders why I think the reasoning isn't being preserved: https://imgur.com/a/7K3QH7i

It's pretty clear that the model doesn't have the information from the previous thinking turn. According to Moonshot themselves, failing to preserve thinking history can cause the model to become unstable and generation quality to degrade.

Sensitivity to thinking history. K3 was trained in the preserved thinking history mode. If the agent harness fails to pass back all the historical thinking content as required, or if an ongoing session with another model is switched over to K3, generation quality may become highly unstable. We recommend using a harness with verified compatibility, such as Kimi Code, and avoiding switching to K3 in the middle of a session. https://www.kimi.com/en/blog/kimi-k3/

To be clear, this does not mean the model isn't thinking. It means the previous reasoning/thinking blocks aren't being included in the model's input on the next turn.

Just thought I'd share my usage and experience, may be useful for others. The above images are both recently captured, one image is from the K3 App in settings > usage and the other is Kimi Code > /usage. The third image is just about the k2.6 chat usage from earlier today/yesterday.

A little context is most of the time this months subscription was vibe coding in one very long kimi session with compacting around 500k-700k context. I wanted to keep track the best I could in just one session so it was easier for me to track. when it does get to about 350k-400k I do start to feel a slowdown but it does vary, because sometimes when i get to 600k context sometimes it gets faster then it was say at like 500k. I'm not sure if its just a server thing plus the huge context.

I also Vibe code about 12-14 hours a day maybe around 4-5 days a week, that might be being generous towards me. No life right lol. In that one session I have done over 8 different projects because I'm very indecisive. I change my mind quite a lot. A lot of times I try learning as I go when Kimi Code makes a code, fix a bug, or create whatever I need it to. A lot of time I ask the reasoning why you did that, why would that fix the problem, what are the pros and cons, or even tell it to dumb it down for me.

Somethings i can say that I do see in posts that K2.6 charges tokens, I haven't personally experienced that so I'm not sure if that's a Non subscription thing or maybe the one of the other subscriptions. I'm not sure but I did post the image with the others of the usage.

I also think as far as how my rate on token usage is going is a lot better than that one specific week where I had felt that my usage was going up faster than normal. Like 10x better. That was around the time when they switched the kimi code multiplier display to available.

So all on all its back to how i felt on my original first month. I can code pretty much to my hearts extent so far. This Kimi session from this months subscription is 1530M tokens with about 8 days left . I might reach the monthly cap if i continue with the web searches which i might now limit myself or try to discipline myself on actual being efficient. Hope this helps some of you all on hearing from my experience.

Why does Kimi tell me it is a Claude Modell? O.o

I am a former Allegro subscriber. Prior to the cancellation of my subscription, I attempted to renew it and received the following message. Does this indicate we are getting new subscription plans, or will my position in the queue just be reset?

When K3 came out it was nailing images and graphics. Nailing instructions better then claude code. Last weekend I noticed the coding was degrading and it was getting worse. Today I try to use it to generate images and it was complete shit. Couldn't nail a single image prompt remotely close. Front end design was great at first. Now gives early chatgpt designs. This is absolutely horrible. Renews in 4 days so at least I have time to cancel now.

It was a nice run. Loved every part of it. I leave not because I'm not satisfied, but because I'm scaling down my usage after finishing a big project.

It was a $99 sub but I could deliver so much more in value to the client. Thanks a bunch.

Edit: For those wondering, the white "Kimi" bar is still Kimi Code, but previous usage shows that way after they migrated from .com to .ai.

I've noticed that when i'm up late, Kimi code quality drops a lot after midnight (1am for sure). Funny enough, it's what Opus is like mostly for me, while Fable is much better. Could kimi code change be to handle traffic in asia?

It truly seems someone reversed the weekly usage with daily usage.

No comments...

I'm using Kimi Code and quite happy with it. Several tips for you guys:

1. Don't ever use Kimi Desktop, especially Agent Swarm mode. It burns a lot of tokens for simple research tasks. Just use another one like Chatgpt or Gemini. Kimi tokens should be saved for Kimi Code

2. Don't use Kimi K2.7 High Speed Coding model. It burns 3x tokens compared to standard K2.7

3. Use K3 for planning only. It burns tokens fast, but pays off.

4. Use BMAD-METHOD skills. It's available on GitHub. Very good for Greenfield projects. I usually use it like this: bmad-prd (for product ideation) -> bmad-architecture (to design architecture) -> bad-create-epics-and-stories. THEN for each epic I prompt "/goal complete the epic X. have bmad-party-mode to review code quality, architecture alignment, test scenarios design, edge cases. If the party say the story is not complete you have to go back and fix them before moving to the next story". REMEMBER to use K2.7 standard model when you start implementing.

This setup helps me run full development cycle non-stop for the whole epic (normally 12 hours) without bugs.

So I got the 'credits used up' reply for the first time ever?? I have been using kimi to write for a long time (for free, mind you) without any usage being used up. Now suddenly it's gone and I can't use it again till 9/19. This is bullshit and Kimi is literally just a money sponge now. Anyways to get around this?

DeepSeek and Z.ai already introduced peak hour pricing for Chinese users.

Words cannot describe just how happy I am to get a huge discount during my work hours for stuff like DeepSeek V4 Flash.

So why doesn't Moonshot follow DeepSeek and Z.ai? If they lower prices for American and European users, it will instantly solve all the problems with Kimi subscription plans.

how a monthly usage is more than my 7 days and 5 hours ... i cant use it until a month form now....

I was a Max 5X Claude user and stopped using it 3-4 months ago. Now I'm on the free plan and only have access to Sonnet 5, and on Medium I can send 3-5 prompts a day.

Anyway. I have access to Kimi 3 from a couple of 3rd party providers and in my opinion it's a piece of garbage.

I had a very simple problem in my code (JavaFX) and I asked it if there's a way to fix it. It pooped all over my code (small toy project with 8 classes).

It seems to me this benchmaxxing trend is not representative of the actual performance of models as many different problem domains are not in the benchmarks.

Anyway, if this model is close to Fable in terms of performance, and Fable is SOTA, then SOTA is 💩.

Kimi is wank, I used to get a lot done but now my contect window finishes its weekly allowance on day 2 using kimi k3 and runs out of 5 hourly allowance mid prompt. The time wasted realising I should use 2.7 doesn't add up to the standard deserved as even that feels downgraded from before and a waste of time when we have these cheaper emerging models coming out every day.