r/LocalLLaMA · past month

Kimi K3

Community sentiment from 10 posts · 381 comments · collected September 27, 2026 · generated September 27, 2026

Kimi K3 scores 59/100 overall in the r/LocalLLaMA community benchmark, collected September 27, 2026 from 10 posts and 381 comments. Its strongest category is Intelligence at 70/100, and its weakest is Price / value at 50/100.

59/ 100

Confidence: medium — The sample of 10 posts and 381 comments (past month) has decent volume, but most threads are tangential to K3 — hardware builds, a provider-scam exposé and meta-discussions about AA benchmarks. K3-specific quality feedback is limited to the Terminal Bench thread, the GB10 cluster thread and a handful of comments; there is no data at all for instruction following, writing quality or multimodality, and reliability is only evidenced at the serving-stack level.

Category scores

Intelligence

70

43.8 on the Artificial Analysis Intelligence Index keeps K3 at the top of the open-model pack ('nosing out GLM-5.3 (44.9) and Kimi K3 (43.8)'), and heavy users insist 'Anyone that has used them extensively knows they are very capable models.' The counterweight: weak specialized results (2% on Program-Bench), a vocal camp that reads K3's public-benchmark profile as 'benchmaxxed', and defenders who blame training-data contamination instead ('is it not suspect that glm 5.3 flash and qwen 3.8 flash are better than k3? I promise you they are not.').

Speed

60

Impressive for a 2.8T model: on a 16x GB10 cluster it sustains '~30 tok/s (peaking around 38 tok/s) during heavy code generation and agentic tasks', 87 t/s at C8 concurrency (137 t/s peak) and 750-910 tok/s prefill, which the OP calls 'a speed similar to what kimi k3 api provides'. The catch is that it takes roughly $100k of hardware to get there.

Coding quality

55

Terminal Bench v4: 'Kimi-K3 did pretty bad in this benchmark for its size' (12.6% vs 41.9% for GLM-5.3), and 2% on Program-Bench; users comparing big models conclude 'For coding tasks often GLM5.3 will win'. Defenders answer that the public eval tasks are contaminated and that extensive real-world use shows 'they are very capable models'.

Instruction following

no data

No data in the sample — none of the 10 posts or 381 stored comments discuss Kimi K3's instruction following, prompt adherence or refusal behavior.

Long context

58

The GB10 thread reports 'Stable multi-hundred-thousand token context runs agentic workfows with multiple 500k compaction', but K3 is also said to share the symptom of 'this linear-like symptoms in longer context outside for general chat purpose (K3 has this too) that mixes up timeline and/or state changes in the context'.

Price / value

50

K3 is listed among the 'expensive models' (sold at $2/$10 in/out by the exposed CrofAI wrapper) and self-hosting is prohibitive: 'That model requires ~802GiB even at the lobotomy level quantization of Q2_K', plus '~100k of hardware with a daily operating cost of ~10 bucks a day in electricity'. No praise for its price anywhere in the sample.

Reliability & uptime

60

Only serving-level evidence exists: the GB10 setup 'handle[s] multiple concurrent user requests smoothly without dropping token generation rates or starving KV cache memory' across stable multi-hundred-thousand-token runs. There is no data on provider uptime or the model's own failure modes.

Creativity & writing

no data

No data in the sample — no user comments rate Kimi K3's writing, persona or creative output; the writing-related praise in the sample concerns other models.

Multimodal & vision

no data

No data in the sample — there are no mentions of Kimi K3 vision or multimodal capabilities at all.

Agentic & tool use

57

Built for agentic work: 30 t/s decode 'during heavy code generation and agentic tasks' and stable 500k-compaction agentic workflows on a 16-node cluster. But the agentic benchmarks present in the sample rank K3 poorly for its size (Terminal Bench v4 12.6%, Program-Bench 2%) — a gap defenders attribute to contamination of public eval tasks.

Summary

Kimi K3, Moonshot's 2.8T-parameter flagship, appears in this month's sample as a top-tier open-weights-class model on aggregate leaderboards: 43.8 on the Artificial Analysis Intelligence Index, just behind GLM-5.3 (44.9) and Qwen3.8 Max (45). At the same time the community is deeply divided on what those numbers mean: on Terminal Bench v4 K3 'did pretty bad in this benchmark for its size' (12.6% versus 41.9% for GLM-5.3) and scored 2% on Program-Bench, and the most upvoted take in the sample accuses newer models of contamination — 'is it not suspect that glm 5.3 flash and qwen 3.8 flash are better than k3? I promise you they are not.'

Running the full 2.8T model locally is possible but extreme: a 16x GB10 cluster (roughly $100k of hardware) sustains ~30 tok/s of coding throughput with 87 t/s at C8 (137 t/s peak) concurrency and stable multi-hundred-thousand-token contexts, which the OP describes as 'a speed similar to what kimi k3 api provides'. Commenters call the rig 'a beautiful kind of overkill' and point out the model 'requires ~802GiB even at the lobotomy level quantization of Q2_K', so K3 remains 'out of reach for many businesses let alone prosumers'.

Direct K3-specific quality feedback is sparse and mixed. Enthusiasts stress that extensive use shows 'they are very capable models', and the GB10 thread's author expects the upcoming K3.1 to be 'subtantially better' on the same architecture. The clearest negative data point is long-context behavior: K3 reportedly shares the symptom that 'mixes up timeline and/or state changes in the context' in longer general chat. In coding comparisons the community mostly prefers the competition: 'For coding tasks often GLM5.3 will win'.

K3 also features in the sample's biggest provider-scam story: the exposed CrofAI wrapper sold 'kimi-k3' at $2/$10 in/out while silently routing requests to GLM 5.3 Flash, and its claim of running K3 on RTX Pro 6000s was debunked because the model 'requires ~802GiB even at the lobotomy level quantization of Q2_K'. Trust in aggregate indexes is low across the sample ('AA for AI eval is like userbenchmark for CPUs'), so the 43.8 index score should be read with caution. No data in the sample covers instruction following, writing quality, or multimodality.

Pros and cons

Pros

  • Top-of-the-pack open-weights-class intelligence (43.8 on the AA Intelligence Index, behind only GLM-5.3 and Qwen3.8 Max)
  • Full 2.8T model runs locally at usable speed: ~30 tok/s coding decode and 87-137 t/s concurrency peaks on a 16x GB10 cluster, 'at a speed similar to what kimi k3 api provides'
  • Stable long agentic sessions: multi-hundred-thousand-token contexts with multiple 500k compactions and no KV-cache starvation
  • Defended as genuinely capable by heavy users despite weak public-benchmark scores ('Anyone that has used them extensively knows they are very capable models')
  • Strong momentum — the upcoming K3.1 is expected to be 'subtantially better' on the same architecture

Cons

  • Weak agentic benchmark results for its size (12.6% Terminal Bench v4, 2% Program-Bench) fueling 'benchmaxxed' accusations
  • Effectively unrunnable at home: '~802GiB even at the lobotomy level quantization of Q2_K' and ~$100k of hardware for ~30 tok/s — 'out of reach for many businesses let alone prosumers'
  • Long-context complaints: 'mixes up timeline and/or state changes in the context' in longer general chat
  • Coding comparisons mostly favor GLM-5.3 ('For coding tasks often GLM5.3 will win')
  • Provider and benchmark trust issues: the exposed CrofAI scam sold fake 'kimi-k3' at $2/$10, and K3's index placement swings with reweighting ('down into the gutter')

Top quotes

  • “is it not suspect that glm 5.3 flash and qwen 3.8 flash are better than k3? I promise you they are not.”
    lemon07r · 47 points positive view on Reddit ↗
  • “Kimi-K3 did pretty bad in this benchmark for its size.”
    Ok_Warning2146 (OP) · 171 points negative view on Reddit ↗
  • “It's a sign that Kimi is a benchmaxxed model, not that the benchmark is bad lol. Terminal Bench 4.0 is one of the best benchmarks to measure models today.”
    BankruptingBanks · 3 points negative view on Reddit ↗
  • “Nor does it suggest that K3 or DS4 have no utility. Anyone that has used them extensively knows they are very capable models.”
    jld1532 · 3 points positive view on Reddit ↗
  • “It is not any agent, it is the huge 2.8T Kimi K3 locally at a speed similar to what kimi k3 api provides.”
    ciprianveg (OP) · 5 points positive view on Reddit ↗
  • “Faster, yes, better, no.. And I think the soon to be released Kimi k3.1 will be subtantially better and hopefully same architecture”
    ciprianveg (OP) · 5 points neutral view on Reddit ↗
  • “it has this linear-like symptoms in longer context outside for general chat purpose (K3 has this too) that mixes up timeline and/or state changes in the context.”
    NandaVegg · 3 points negative view on Reddit ↗
  • “I run GLM5.3, DSv4.1Flash, Qwen3.8Flash, Qwen3.8-2.4T, KimiK3 and MiniMaxM3. Performance is great, a single RTX 6000 or M3 Mac Studio wish they could.”
    segmond (OP) · 1019 points positive view on Reddit ↗
  • “That model requires ~802GiB even at the lobotomy level quantization of Q2_K.”
    SorosAhaverom (OP) · 852 points neutral view on Reddit ↗
  • “16 GB10s, dual 400G switches, custom NCCL patches... all so a coding agent can stream 30 tok/s. Honestly, that's a beautiful kind of overkill.”
    Muhlwa_Sholanke · 3 points neutral view on Reddit ↗
  • “Kimi-K3, Qwen3.8-Max, Gemini-3.8, and Grok 4.6 go down into the gutter”
    crusaderky (OP) · 90 points negative view on Reddit ↗

Top sample posts

Top 5 of 10 posts by score

FAQ

What is Kimi K3's overall community score?
59 out of 100, with medium confidence: The sample of 10 posts and 381 comments (past month) has decent volume, but most threads are tangential to K3 — hardware builds, a provider-scam exposé and meta-discussions about AA benchmarks. K3-specific quality feedback is limited to the Terminal Bench thread, the GB10 cluster thread and a handful of comments; there is no data at all for instruction following, writing quality or multimodality, and reliability is only evidenced at the serving-stack level.
How was the Kimi K3 benchmark collected?
From 10 posts and 381 comments on r/LocalLLaMA sampled over the past month window.
Which categories does the Kimi K3 report score?
Intelligence, Speed, Coding quality, Instruction following, Long context, Price / value, Reliability & uptime, Creativity & writing, Multimodal & vision, Agentic & tool use.
What are the main community pros and cons for Kimi K3?
Top pros: Top-of-the-pack open-weights-class intelligence (43.8 on the AA Intelligence Index, behind only GLM-5.3 and Qwen3.8 Max); Full 2.8T model runs locally at usable speed: ~30 tok/s coding decode and 87-137 t/s concurrency peaks on a 16x GB10 cluster, 'at a speed similar to what kimi k3 api provides'. Main cons: Weak agentic benchmark results for its size (12.6% Terminal Bench v4, 2% Program-Bench) fueling 'benchmaxxed' accusations; Effectively unrunnable at home: '~802GiB even at the lobotomy level quantization of Q2_K' and ~$100k of hardware for ~30 tok/s — 'out of reach for many businesses let alone prosumers'.
When was the Kimi K3 data collected?
Collected on September 27, 2026; the report was generated on September 27, 2026.

Collected from public r/LocalLLaMA posts and comments via Reddit JSON API on September 27, 2026.

Related models