Context if you missed Part 1: Allegretto plan user. Kimi Code 2.6 broke the weekly token cap scaling. Weekly cap binds at ~11% of monthly, not the expected ~25%. Support sent a generic FAQ that literally contradicted their own “Absolutely, spend all credits on one feature” policy. I roasted them here. It was therapeutic.
But oh friends. Oh dear, sweet readers. The saga continues. And it got worse.
THE FORUM SAVIOR
After my first post gained some traction, a kind support person on the forum slid into the thread.
"…the fastest and most secure way to get them sorted out is to drop an email directly to our dedicated team at [email protected]"
My heart soared. A human! A path forward! The “correct” email! Surely this would bypass the FAQ-bot and get me to someone who could actually read numbers.
I emailed immediately. Professional. Concise. Referenced the forum thread. Re-attached my math.
I waited.
And waited.
A near week later: absolute radio silence.
But here is the punchline. Are you ready?
THE “CORRECT” EMAIL THEY SENT ME TO WAS THE SAME DAMN [email protected] THAT SENT THE RIDICULOUS FAQ IN THE FIRST PLACE.
The forum person, with the best of intentions, directed me back into the exact same void. It is like being told “the doctor who misdiagnosed you is actually the specialist, go see him again.” I walked in circles. I emailed a black hole. And that black hole? It already ate my first email and burped out a copy-paste.
THE ACTIVE DAMAGE WHILE THEY GHOST ME
But wait, it gets better. Because while they are ghosting me for a full week - while the “correct” support channel is stone silent - I am actively being throttled in real time.
Let me give you the current carnage:
-
Week 3 of my monthly cycle
-
100% weekly quota burned in 3 days
-
~50% monthly credits STILL REMAINING, SITTING UNUSED
-
Locked out again. Waiting for reset.
Do you understand what this means? I have paid for a monthly pool. HALF of it is still there. But I cannot touch it. A weekly cap - calibrated so absurdly low that a solo dev doing normal multi-project work burns through it in 72 hours - is standing guard over my own subscription like a bouncer who does not know I am on the list.
I am not mining Bitcoin. I am not running a bot farm. I am one guy writing code across multiple repos in Kimi Code, the feature they literally advertise as their flagship IDE assistant. And that usage pattern - the exact workflow they market - consumes 100% of my weekly allowance in three days.
Meanwhile, 50% of my monthly budget rots in the dashboard, a number that mocks me while my IDE assistant is disabled.
THE KAFKAESQUE LOOP
Let me map the absurdity of this support journey so far:
-
Notice the bug: weekly cap too aggressive, monthly % a lie
-
Email support: get generic FAQ contradicting their own policy
-
Post on forum: get told to email the “correct” address
-
Email the “correct” address: realize it is the same address that sent the FAQ
-
Wait a week: zero response. They vanish.
-
Meanwhile: burn 100% weekly in 3 days, 50% monthly untouched, locked out again
I am not in a support queue. I am in a trap. A loop. A corporate ouroboros where the tail eats the head and nobody answers the phone.
The forum person tried to help. I believe that. But the organization behind them is structured so that “correct support” and “FAQ-bot that contradicts policy” are literally the same inbox.
WHY THIS MATTERS BEYOND MY FRUSTRATION
I need to say this again because it is the tragedy of the whole thing:
Kimi Code 2.6 is an epic engine. I am not here because the product is bad. I am here because the product is so good that being locked out of it feels like having your Ferrari towed because you drove it too fast on the highway.
The context awareness. The multi-file reasoning. The refactor suggestions. It is genuinely the best coding assistant I have used. I WANT to pay them. I WANT to evangelize. I WANT to recommend Allegretto to every dev I know.
But I cannot, in good conscience, tell someone to subscribe to a plan where:
-
The weekly cap is a hidden boss that defeats the monthly cap
-
Support sends policy-contradicting FAQs
-
The “correct” support email ghosts you for a week while the bug actively costs you work days
-
Your dashboard shows 50% remaining while your hands are tied
This is not a pricing complaint. I am happy to pay for Allegretto. This is a system design and customer service failure that makes the pricing irrelevant because I cannot actually use what I bought.
THE ASK, AGAIN, BUT LOUDER THIS TIME
Moonshot / Kimi:
-
Respond. A week of ghosting from the “correct” support channel is unacceptable.
-
Fix the weekly cap scaling. Monthly / 4 = weekly. This is not advanced math. A single dev on your flagship coding feature should not burn 100% of a weekly quota in 3 days.
-
Stop the runaround. If
[email protected]is both the FAQ-bot AND the “correct” escalation channel, you do not have a support system. You have a lottery. -
Honor your own policy. “Absolutely, spend your entire pool on one feature” is a promise. The weekly cap breaks it. Pick one - the promise or the cap - because both cannot exist.
And to the kind forum person who tried to help: thank you. I know you tried. But your organization is eating its own tail.
TL;DR: Part 1 was about broken math and bad FAQ templates. Part 2 is about being ghosted by the “correct” support email for a week while burning 100% weekly quota in 3 days with 50% monthly credits still locked behind a broken weekly wall. The engine is still godlike. The infrastructure around it is crumbling.
/endrant²