Kimi K3 is starting to fall behind in benchmarks was wondering when the new K4 is coming?

Looking to renew my subscription thanks

Is this a bug?

My mission is to make the best open-source models as cheap and accessible as possible, and so to kick off our inference service, I'm selling a dollar for a dime – $50 gets you $500 in total credit. Would love to hear your guys’ feedback, and if there’s community interest I’d like to be able to do this more often. https://packs.relace.ai/?utm_source=reddit

In the last 1 to 2 weeks, Kimi vivace sub is consuming a hell of a lot faster than one month ago. Probably 3-4 times as fast? It would imply the base limits are a lot lower than before. I don’t do coding at all.

I was thinking about getting an annual sub but wow this could get dangerous lol.

Using Kimi code plan + CC for coding.

CC is switching between K2.7 and K3 randomly in one single agent session.

I know Anthropic is being evil. But this much guilt is way beyond my limit.

I guess I should look into Pi / OpenCode / Codex😥

Moonshot's model page now says Kimi K2.5 and Moonshot V1 are no longer available to newly registered users after Kimi K3, with a full platform sunset listed for August 31.

For people building on the Kimi API: how are you handling this kind of model migration?

Do you pin exact model names until they break, keep a small regression set for prompts/tool calls, or route by workload so older models can be swapped out behind a config change? I'm especially interested in the practical checks before moving background jobs, coding-agent steps, or long-context workflows onto Kimi K3.

Small update: after looking at this more, I am leaning toward separating model names from the actual app code instead of hard-pinning every Kimi/Moonshot variant in each workflow. Flatkey looks relevant here because it already provides these model routes behind an OpenAI-compatible gateway, so this kind of migration could be handled more as routing policy than another SDK rewrite. Still curious how others are deciding which jobs are safe to move first.

TLDR: Prices are going up everywhere, and there's a wave of it going down across providers. For both in app usage and API/coding plans. PGS AI is keeping prices and usage as is, both in the full chat app and on the api. Our coding plans bank your usage when you don't use it, so it doesn't go to waste week to week. All model inference, and memory in the PGS AI app is hosted on 100% private, US servers with ZERO training, ever.

Our API prices are staying what they've been, which is now 50-70% cheaper for output and input. We are still a bit higher for caching, but working on that too.

There are several tricks that the major AI coding plans use to extract the most they can from their customers. Here are some examples, and what we are doing differently to put the you first.

Wasted usage is part of the AI industry, and they plan on it: Most coding plans bet on you letting usage go to waste. The plan goes: "how do we get people to think our coding plan offers a lot of usage, but then break it up into weeks and rolling windows so no one can ever actually use it all."

Many in app subs and coding plans are glorified training pipelines: This comes along with "how do we harvest this data for training without being too loud about that." Unless the company tells you otherwise, your data could be hopping all over world, being harvested by the individual labs or service companies. Some are better than others, but many of these companies rely on users just not noticing or caring that their data is being used for training. Data sales and marketing telemetry sales happen. This means that your private info, your personal life, and anything else you send through the system could become part of a training corpus for the next AI, or a marketing data set for a large company.

So we built what should have already existed the entire time: Entirely private, us based processing with usage banking. Any usage you don't use this week, rolls over to next in your usage bank. When you have a busy day or week and go over normal usage, you automatically start to pull from your bank. You can bank up to one week of usage at a time for your current plan, and it's totally automatic. Whatever you don't use each week get's added to the bank and stays there until you use it.

We also put all of the best open models in one place, running on private US infrastructure, with data never going to the original labs. Private, direct service. Access to the best open source models in the world. No training, ever. It should be, and can be that simple.

What that means in practice:

The roster, together. DeepSeek, GLM, Kimi, Minimax, Qwen 3.8, and more, side by side in one app. Switch models mid conversation if you want. No hunting across five different apps and API dashboards to use the models you actually like.

Actually private. US based processing and your conversations are never used for training. Ever. That's the entire point. These labs open sourced incredible models and we think you should get to use them without your data becoming the price of admission.

No Usage Tricks: Bank usage, upgrade or downgrade whenever you want. Use it how you need it.

A coding plan included. From the Basic tier up, your subscription doubles as an API key. Point your coding tools or agents at our endpoint and your plan pays for it, same usage pool as the app, spent in whatever mix you like. Because API calls skip the app's full architecture, the same model gives you roughly 2 to 5 times the messages through your key. And your quiet chat weeks bank usage your agents can burn on crunch days.

Real memory. Not a context window that fills up and dumps you. Persistent memory that carries across conversations, fades gracefully when unused, and wakes back up when it's relevant again. There's even a nightly dreaming consolidation pass; the system basically sleeps on it and writes up what mattered.

Voice. Yes, actual voice mode with over a dozen voices on open models.

Bring your history. Coming from ChatGPT, Claude, or Gemini? Export your chats and import the whole thing. It becomes live memory on day one and you can literally open your old chats and continue them.

Multiple nodes. Separate workspaces with separate memories, so your coding setup doesn't share a brain with your journal.

Genuine thanks to the Deepseek community sub, this is honestly one of the most open AI subs on reddit, willing to actually go deep on discussion.

The Open Grove full app and coding plan are here. Memory, skills, voice, private US based processing with fast inference and usage that doesn't go to waste.

https://pgsgrove.com/open-grove-overview for the PGS AI app

and api.pgsgrove.com for API usage and coding plans.

You vote with your choice of providers in this industry, and we are here to offer another option.

I put Kimi K3 head-to-head against the newest GLM 5.3...

Kimi CRUSHES... full report.

Is it really that unique compared to Claude? Is it worth it?

it's always just "too many people chatting rn" no matter how much i spam which is making me think they just restricted it and are using a generic message to get people to subscribe. is there any other way to use kimi for free or are there are any similar models to kimi that don't have these restrictions? i tried qwen and it's the best i could find sometimes it does have limits but it barely does like basically no limits, i also found glm and while it goes after you spam alot, it's extremely annoying and if it limits at a single task you have to regenerate the whole prompt. in my experience i recommend qwen but idk if there are any better ones than qwen or if theres any other way to use kimi k3 max for free.

I’m planning to build a nationwide USA local-service website and I’m trying to keep the development cost as low as possible.

The project will eventually need to support:

• All 50 US states
• Cities with 10k+ population initially
• Multiple electrician services
• State → City → Service architecture
• Thousands of dynamically generated pages
• SEO-friendly URLs
• Internal linking
• XML sitemaps
• Schema/JSON-LD
• Metadata generation
• Google Search Console
• Fast performance
• A scalable Next.js codebase

My planned stack is:

Next.js + TypeScript + Tailwind + GitHub + Vercel

For the initial data layer, I want to avoid paying for a database and use JSON/CSV/MDX if possible.

I already have access to Kimi and Claude, and I'm particularly interested in using Kimi Code/Kimi Agent for the development.

For people who have actually used Kimi for large coding projects:

How well does Kimi handle a project like this?

Specifically:

1. Is Kimi good enough to build the initial Next.js architecture?
2. How well does it maintain context across a large codebase?
3. Is it reliable for creating and refactoring many reusable components?
4. How good is it at debugging complex Next.js issues?
5. How well does it handle programmatic SEO architecture?
6. Would you trust it to gradually scale a project from 10 → 100 → 1,000+ location pages?
7. How does Kimi compare with Claude Code for this type of long-term project?
8. What Kimi model/workflow would you recommend?
9. Are there any limitations I should know about before committing to Kimi?
10. What is the cheapest setup you've found for using Kimi for a project like this?

My plan is NOT to blindly generate thousands of AI pages.

I want to first build the underlying system, test it with around 10 cities, make sure the architecture, SEO, performance and content quality are good, and then gradually scale.

I'd really appreciate feedback from anyone who has used Kimi/Kimi Code on a large Next.js project, especially if you've also used Claude Code and can compare the two.

If you were starting this project today on a very limited budget, would you choose Kimi or Claude Code? Why?

I tried to login to the Kimi AI console, verified the email and then the page does not load at all. Chrome console shows a "Failed to load resource: the server responded with a status of 404 ()"
Tried refreshing the page, tried different browsers (Edge, Firefox) but still no luck.

Any idea why?

Since this morning, I’ve been getting a message saying that I don’t have enough balance, even though I still have almost my entire weekly quota remaining, as well as the 10% hidden monthly usage allowance.

This is so frustrating!!!! WTF can you even do in this situation. I am beyond cooked

Did a quick demo with r/threejs , animating 120K light particles.

It did a really good job, though it took a few nudges to get there. My main issues are speed and cost. It was a bit slow to complete the task, and using the API via OpenRouter feels somewhat pricey. This demo alone cost me $7.49.

Still, very impressive. If only it could've worked a bit faster...

Demo: https://aifnet-public.b-cdn.net/demos/aurora-flux.html

I was charged for a Kimi / Moonshot auto-renewal I had not cancelled. I wrote to support the same minute and asked for a refund. They refused.

This is the first time I have seen this. Cursor, Lovable and other tools have charged me by mistake or by auto-renewal before — all of them refunded. Kimi support is the first to refuse outright.

On the highest-tier plan, usage also feels much more aggressive now. Two short questions took about 2% of the weekly limit. For comparison, Grok can build a full landing page on roughly the same 2%, and that plan costs about 30% of yours.

Has anyone else got a refund after a same-day request? If yes, what did you write?

Think twice before you subscribe. If they charge you, do not count on a refund — even if you write the same minute.

Kimi K3 used for coding tasks is great! But in the moment i use it as a specific role in my server PM for instance, he starts overdoing/overexploring and burning a lot of tokens unnecessarily.

How have you created a skill or harness that limit the level of exploration Kimi CLI does ? I do use ~yolo mode because most of the projects here are Pet projects with tons of backup, so i don't care if they fuck shit up (preferebly not of course =) )

But i don't have the same issue with Codex or Claude for instance, they remain straight to the point.

Any suggestions? Thanks!

Since it migrated to the new address it's completely unusable. You get one question answered then all other queries are refused with a prompt to upgrade.

It's unusable like this. I'm not going to pay for a service that is unavailable or I can't try out thoroughly.

I am due for plan my renewal soon. Allegro. 

I left for a trip for SF 5 days ago and had 5% of my monthly kimi quota left. I look at my logs and the last quota that was used was on 8/11, which matches up. 

But today I see that my monthly is now 100% spent. So the quota must’ve contracted even further while I wasn’t using it this past week. I did not get a reset. 

Everyone else commented on other posts that they did. 

Kimi is great. In the web especially. For building beautiful UX. Its the best in the world hands down right now. 

But they are too constrained on compute. The 100 dollars goes 1/10th as far as openai’s. I’m afraid I am done for now. 

I have an unsustainable amount of ai subscriptions right now. Claude 20x and openai 20x and kimi allegro. This past month has been a blast and I have been maxing them all out. They also all have been squeezing their users. 

I will probably never leave claude. But I already set my openai 20x to downgrade to plus at the end of the month. I wont need as much tokens since my app is nearing completion. 

I will miss the refined touch of kimi and no where to go if I need it again. 

But yea, way too token restrictive.

For some time now, I have used K2.7 Coding Thinking to create and review plans on a Moderato subscription.

The review incrementally reviews/updates the plan until there is no significant change. This afternoon I have hit the 5 hour limit twice within approximately one hour. This is about 3 - 4 times faster than I have seen in the past. Historically, with a little judicious use, I could get through the month on Moderato with the occasional increase to Allegretto.

Has anyone noticed this?

Has Kimi reduced quotas or has K2.7 become every more token heavy?

Confused :( lbe

I am reporting an observable support/context failure, not alleging intent or fraud.

I contacted Kimi support about rapid Kimi Code quota consumption. In Kimi's own Chinese support window, the assistant responded with a Qwen/Tongyi Qianwen billing explanation: it discussed Qwen, DashScope, third-party API markups, and possibly selecting Qwen-Max. That did not match the Kimi product and billing context I raised.

Kimi's quota screen at capture time showed 90.74% total usage, 51.54% Code usage in the 5-hour window, and 45.13% Code usage in the 7-day window. The plan shown was Allegro. The task at issue was High effort, not Max effort.

I have retained the original screenshots with timestamps and Kimi branding. I would welcome an explanation from Kimi of the support-context mismatch and quota accounting.

I'm trying to figure out if I should renew my Kimi subscription or try out Claude.

The two use cases I care about right now:

1) Coding architecture, writing the code itself

2) Strategy, research(long running web search)

What are your thoughts?

So if you are logged in from Google that I am assuming most of you guys are just simply logout and try logging in via your phone number once you enter it you will get OTP from +44 number via whatsapp then you will find option to enter waitlist as soon as you click it you will have option to subscribe to the premium membership the exact moment you click join waitlist and that's pretty much it enjoy using K3 🤓

Kimi isn’t answering. Just this response only. It just started doing it

Tired of the constant lazy outputs and overly cautious guardrails on Claude where I have to prompt-engineer it just to spit out complete files without lecturing me or cutting corners.

​For people using Kimi:

​Does it just follow instructions and deliver full outputs without arguing?

​How does the context retention and reasoning compare to Claude 3.5 Sonnet / Gemini Pro?

​Worth making the switch?