Hi,
Thanks for the detailed feedback. Your ~93% calculation makes perfect sense if we are looking at a perfectly steady, evenly-paced month.
To clarify how the math works on our end, the full 100% monthly quota is entirely accessible. Because a 30- or 31-day month always spills into a 5th weekly reset window, users technically have the capacity to use that remaining quota in the final few days. However, we completely agree that expecting users to “burst” their usage in those last 2-3 days just to hit 100% isn’t an ideal or natural experience.
The 5x multiplier is specifically designed as a flexibility buffer for those extra days, ensuring that a strict 4x cap (which only covers 28 days) doesn’t completely lock you out before the month ends.
The real issue here is the shared pool. We know the current trade-off is frustrating because your quota isn’t just for coding. Since Kimi Chat and Kimi Work draw from this exact same pool, this pacing mismatch can unfortunately lead to Chat lockouts at the end of the month, even if you still have weekly coding capacity left.
Here’s how we are fixing it:
We are actively designing an updated membership structure, which includes a dedicated plan tailored specifically for developers. For users focused on coding, the limits will be optimized entirely to keep you in your flow without frustrating interruptions. This means moving away from the shared pool model altogether for this track, so your coding experience will no longer be tangled up with Chat limits.
Your feedback highlights exactly why we are prioritizing this change. We’ll share more details as soon as the new structure is finalized.