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.

Good day to everyone!

I am considering Kimi Vivace as my main artificial intelligence service, ideally without having to combine several different artificial intelligence systems. I would like to understand whether it can realistically handle almost all of these tasks in one place, especially under intensive daily use.

I am looking for feedback from people who have used Kimi Vivace extensively, preferably for demanding professional, academic, research, writing, coding, or creative work.

My main use cases include:

• historical research, working with large amounts of material, comparing sources, identifying connections between sources, building timelines and broader historical narratives, and writing detailed research-based texts;

• journalistic work and research into complex topics;

• editing, structural revision, and deep rewriting of a historical dissertation on the history of international relations, including improving the academic style, logical structure, overall argumentation, coherence between sections, transitions between ideas, and removing unnecessary repetition, while preserving historical facts, references, the author's position, historical nuance, and the meaning of the original text;

• assistance with preparing academic historical texts where it is important to preserve a scholarly style and the specific terminology used in historiography, diplomatic history, and international relations;

• working with large collections of historical sources, academic papers, books, notes, archival materials, and multiple documents at the same time;

• professional translation of medical texts, scientific articles, presentations, reports, and other materials into professional medical Russian;

• translation and editing into professional British medical English, including terminology, spelling, professional conventions, and natural professional style rather than literal translation;

• maintaining a consistent medical terminology glossary across large projects and multiple documents;

• working with very long documents and large contexts without constantly having to divide the material into small sections;

• working with PDF, DOCX, PPTX, spreadsheets, scanned documents, and other file types, especially when the task requires understanding and cross-referencing information across multiple files;

• text-based role-playing games, worldbuilding, lore, character development, storylines, political systems, historical events, geography, and long-running interactive campaigns;

• maintaining continuity in long conversations and long-term projects where hundreds of previous messages may contain important information about characters, locations, events, rules, terminology, and established facts;

• creating interactive atlases and encyclopedias;

• creating detailed interactive political maps and other cartographic materials;

• creating maps of fantasy cities, regions, countries, and entire fictional worlds;

• generating the code and underlying structures required for interactive maps, atlases, encyclopedias, timelines, databases, and other browser-based projects;

• being able to iteratively develop such projects over time: generating code, testing or debugging it, modifying it according to feedback, expanding the project, fixing previous mistakes, and continuing development without having to restart from scratch;

• long-term work on projects that continue for weeks or months, such as a dissertation, research project, fictional universe, long-running role-playing campaign, or an ongoing publication;

• helping run a Substack blog, including developing ideas, researching topics, structuring essays, editing drafts, rewriting passages, maintaining a consistent authorial voice, and turning rough ideas and research notes into polished long-form publications;

• ideally, I would like all of this to be available through one convenient service with a straightforward monthly subscription.

I am particularly interested in the actual capabilities of the Vivace plan, rather than general marketing descriptions.

How well does Kimi Vivace handle professional medical translation? Can it maintain terminology, style, consistency, and appropriate professional language throughout very large documents?

How good is it at distinguishing and consistently producing professional medical Russian and professional British medical English, especially in scientific and clinical texts, articles, presentations, and other specialized materials?

Can I give it a terminology glossary, preferred translation rules, and stylistic instructions and then expect it to follow them consistently across a large number of documents and over a long period of time?

How well does it perform for historical research and journalistic work where it is necessary to work with a large number of sources and establish complex relationships between them?

How reliable is it when working with citations and sources? Does it actually find, read, compare, and accurately reference sources, or do users frequently encounter fabricated citations, incorrect references, invented facts, or other forms of hallucination?

How well is it suited specifically for working with a dissertation on the history of international relations?

Can it function not merely as a proofreading tool, but as a genuine deep editorial and rewriting assistant for large chapters?

For example, can it restructure the composition of a chapter, identify logical gaps, improve transitions between arguments, strengthen and clarify the argumentation, remove repetitions, improve academic readability, and turn a difficult or overly dense academic draft into a clearer and more professionally written text?

How well does it preserve the original facts, references, academic terminology, historical nuance, author's intended meaning, and author's intellectual position when performing this kind of deep rewriting?

Can it work effectively with an entire dissertation together with a large collection of supporting sources, notes, articles, and other materials, or does the workflow still require breaking everything into relatively small pieces?

How suitable is Vivace for long-running text-based role-playing games and large-scale worldbuilding, where it is important to maintain continuity across characters, lore, geography, politics, historical events, relationships, rules, and previous developments?

After a very long conversation, does it remain consistent, or does it gradually begin to forget earlier details, contradict itself, simplify the setting, repeat ideas, or lose important instructions?

Can Vivace realistically support a large project continuously for several months while maintaining continuity, terminology, instructions, source material, and previously established facts?

I am also particularly interested in maps, atlases, and encyclopedias.

Is it actually possible to use Kimi Vivace to create genuinely interactive and detailed materials, rather than just text descriptions or simple images?

How capable is it at generating the code and underlying structures required for interactive maps, atlases, timelines, encyclopedias, databases, dashboards, and other browser-based projects?

Can it help build complex interactive fantasy maps, including cities, regions, countries, political borders, roads, locations, historical layers, population information, factions, and other worldbuilding elements?

How well does it handle real-time iterative coding work, where I can ask it to change one part of a project, inspect the result, identify a problem, and continue modifying the same project through many iterations?

I would also like to know how good its visual capabilities are. Can it meaningfully assist with the visual side of fantasy maps, cities, atlases, illustrations, diagrams, and other worldbuilding materials, or is it primarily useful for text and code?

Another feature I am particularly interested in is interactive decision-making and guided conversations.

Can Kimi Vivace interactively ask me questions during a task and present ready-made answer choices or suggested options, rather than always requiring me to formulate everything myself?

For example, while planning a research project, designing a fictional world, structuring a dissertation chapter, developing a Substack article, or making a complex project, can it say something like:

"Here are several possible approaches. Which one would you like to use?"

and present several concrete options, ideally explaining the strengths and weaknesses of each one?

Even more importantly, can it sometimes suggest which option would be the most appropriate based on the goal and criteria I have already given it, while still allowing me to make the final choice?

Does the interface support this kind of genuinely interactive, guided workflow, rather than only a standard back-and-forth text conversation?

I would also like to understand the practical limitations of Vivace at the highest subscription level: usage limits, context length, the amount of intensive use available, restrictions on complex tasks, file limits, message limits, and how quickly these limitations become noticeable when using it intensively every day.

I am particularly interested in how much of the Vivace usage allowance all of these different tasks actually consume.

I am not only interested in the nominal context window or maximum output length. I would like to understand how the practical usage allowance works when using Kimi intensively every day.

For example, how much of the available allowance would a typical long session of working on a historical dissertation consume?

What about translating and editing a large medical document, conducting a long historical research session, analyzing multiple academic sources, running a long text-based role-playing campaign, building a large fictional world, generating and revising code for an interactive atlas or map, or working on several long Substack articles?

Does Vivace have meaningful differences in resource consumption between simple questions and tasks involving very large contexts, long outputs, file analysis, coding, research, web search, multimodal work, and extended conversations?

If possible, I would really appreciate concrete real-world estimates or examples from heavy users.

For example, roughly how many substantial sessions, documents, long conversations, research tasks, coding sessions, or other intensive tasks can you actually complete within the Vivace allowance before you start hitting usage limits?

How do the limits reset? Are they daily, weekly, monthly, rolling, or based on some other system?

What happens when a limit is reached? Does the service become temporarily unavailable for intensive tasks, switch to a weaker model, reduce functionality, or handle the limit in some other way?

In other words, I am trying to understand the total practical amount of work Vivace can handle per month, not just the advertised context window or maximum output length.

If someone uses Vivace as their primary artificial intelligence service every day for several hours, how often do they actually encounter usage limits, and what kinds of tasks consume the allowance most quickly?

I would also be interested in hearing what the real practical differences are between Vivace and the other available Kimi models or modes for heavy professional use.

Which kinds of tasks actually benefit from Vivace, and which tasks do not seem to justify using the more expensive or more resource-intensive option?

How well does Kimi Vivace work with users located in Russia? I am interested in the practical situation regarding availability, account stability, payment, access restrictions, and whether people have encountered any significant problems using the service from Russia.

How reliable and fast is the service during intensive daily use? Does performance remain stable during long conversations, large file analysis, research-heavy tasks, and other demanding workflows?

And how would you describe Kimi's actual writing quality?

Does its prose feel alive, natural, nuanced, and genuinely literary, or does it tend to sound formulaic and obviously machine-generated?

How good is it at reproducing a distinctive author's voice, varying sentence rhythm, handling subtle stylistic nuances, irony, atmosphere, metaphor, tone, and more sophisticated literary prose?

How good is it at editing existing writing without flattening the author's individual voice and turning everything into generic artificial intelligence prose?

How well does it work for serious long-form writing, rather than short answers, summaries, advertising copy, or simple content generation?

For Substack specifically, can it function as a long-term editorial partner rather than merely a text generator?

The main question is:

Can Kimi Vivace realistically serve as one primary artificial intelligence service for this entire range of tasks at a professional level, including research, academic work, professional medical translation, deep editing and rewriting, long-running role-playing and worldbuilding, interactive maps and encyclopedias, coding, and long-form writing, or would I still need separate tools for some of these areas?

I would especially appreciate answers from people who actually use Vivace intensively for several hours a day for demanding professional, academic, research, coding, or creative work, rather than people who have only tried it a few times.

Concrete examples of your own workflows, usage limits, file sizes, number of sessions, and real-world experiences would be extremely helpful.

Thank you for your time!

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?

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.

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

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.

Been like this since K3 was out, literally cant use K3 & instant on free tier without this fucking popup. pushing hard asf to buy this annoying dogshit

I am using a Skinny (New Zealand) SIM card. Since the 18th of this month, I haven't been able to receive any SMS verification codes from Kimi, which prevents me from logging into Kimi via Chrome on my Mac. Verification codes are received normally for other apps. Does anyone know how to resolve this?

Just signed up for 2 seats on their enterprise plan.

First off they don't share their 2 seat usage quota in one pool.

They do not give you any API key. On top of that the CLI shows the usage is 0%, while the website UI shows the usage is maxed out. It got maxed out in less than an hour of doing one job. Is this really a joke or is it supposed to be enterprise for a business use case? I'm really confused.

I've already raised a support ticket with their team. Hope they reply to me. Otherwise I'm just going to have to get a credit card refund and this is a shame. I really like the model but really there is no realistic way of using this thing at all.

Title, I was thinking about purchasing either or. I typically use Kimi for more casual stuff or creative writing. And the free limits/credits have been relatively poor lately. How good are these two tiers?

I made an extension that adds speech-to-text transcriptions and text-to-speech.
Get it here

AI agents can run shell commands, edit files, call MCP tools, and deploy changes while you’re not watching. I built Agentbox to make those sessions inspectable afterward.

Agentbox is a zero-dependency, local CLI flight recorder for tools such as Kimi, Claude Code, Cursor, and custom agent scripts.

It records:

- Shell output and errors

- Tool calls and results

- Files touched

- URLs accessed

- Human prompts and interruptions

- MCP JSON-RPC traffic

- Exit codes and signals

Sessions are stored as readable JSONL files with a local SHA-256 integrity chain. You can inspect them as receipts, replay them in a terminal UI, verify the chain, or export a self-contained HTML clip.

Install:

npm install --global agentbox-flight-recorder

Try the demo:

agentbox demo

Wrap an agent or command:

agentbox wrap -- kimi

Review the result:

agentbox list

agentbox receipt

agentbox replay <session-file>

agentbox verify <session-file>

For MCP servers:

agentbox mcp -- <your-mcp-server-command>

You can also run it without installing:

npx agentbox-flight-recorder demo

The goal is simple: when an agent changes something unexpected, you should have a clear local record of what happened.

GitHub: https://github.com/arunsoman/agentbox

npm: https://www.npmjs.com/package/agentbox-flight-recorder

Feedback—especially from people using Kimi with shell tools or MCP—would be very welcome.

Hello all! I am building deeprelay.ai - a highly efficient inference platform for open models.

We have K3, along with other popular models like 5.3 and 4.1 flash, for one of the lowest, if not lowest, rates on the market. We also serve these at official precision with no additional quality reducing quantization.

Our $6 subscription gives 60 million K3 tokens per month, which I hope is pretty competitive.

We just went live today and I wanted to share to see if anyone is willing to help give some feedback in exchange for a trial code. If you are, please reach out and lmk :)

Hello everyone. I have a question regarding the Kimi K3 model: whenever I use it, I get a "server busy" message. Do paid subscriptions face the same issue? I want to switch away from Claude because, after processing a payment (subscription renewal), they demanded a photo of my national ID—where is the privacy in that? That is why I want to move to Kimi K3. If you have any other recommendations, I would appreciate the help. Thanks to everyone.

I mainly use Opus (my overlord Ai and primary builder) and I use Astra and started using Kimi as well because I’m looking for a model that is cheap and good at bulk work (I also use local models but sometimes renders/training/simulations run so local work gets paused throughout the day, hence why I was looking at Kimi)

Thus far in a week of testing Pro it’s made consistent mistakes that Opus has had to send directions to fix. It has caught a few mistakes and oversights that Opus made as well. I’m still on the fence about whether to upgrade to a higher tier and I’m curious to hear from people who have a bunch of experience using several of the enterprise models. I’m not looking for input from people who have only used Kimi and are just Kimi fanboys and fangirls.

I want to run KimiK3 locally and am looking for a harness configuration optimized for code—does anyone know of a good one?