Kimi K2.6: Advancing open-source coding

Original Article ↗ Hacker News Discussion ↗

Model performance vs frontier models

  • Many see Kimi K2.6 as near–frontier-level, especially for coding; some report it “feels” around Claude Sonnet 4.6 / older Gemini Pro quality.
  • Benchmarks cited: strong in coding and vision, weaker in reasoning/knowledge vs Opus 4.6. Publisher-chosen benchmarks are noted as potentially biased.
  • Some users say it rivals or beats Opus 4.6 in practice; others insist it clearly does not beat Opus and caution against over-trusting benchmarks.
  • Separate comparison work finds only modest gains over K2.5 and lower reliability on puzzle/trick questions and domain-specific exactness.
  • Failures on classic logic puzzles (e.g., wolf–goat–cabbage variants) are reported where Opus 4.7 succeeds.

Real-world coding and agentic behavior

  • Widely viewed as a strong coding model; several users find it competitive with Opus/Sonnet for everyday coding and planning tasks.
  • Others report “overthinking”: huge chains of internal reasoning tokens, analysis paralysis, loops in tool use, and broken refactors in long agentic runs.
  • Earlier K2.x models were seen as good for creativity and variation but unreliable on harder problems; K2.6 is viewed as a more serious generalist but still slower than some peers.

Open weights, size, and hardware

  • Open weights release on Hugging Face is considered “seismic” if performance holds, since it’s an ~1.1T-parameter MoE using native int4 for most weights.
  • Raw model shards total ~640GB; smart quantizations target ~150–512GB RAM/VRAM setups (e.g., high-RAM Macs, large servers).
  • Running locally is feasible for well-funded teams; personal use is possible but often slow (single-digit tokens/sec in some setups).

Pricing, quotas, and access

  • API pricing (~$0.95/M input, ~$4–5/M output; cheaper via third-party providers) is far below Opus, reinforcing perceptions of high margins at US labs.
  • Kimi’s own subscriptions are seen as more usable than low-tier Claude/Gemini chat plans; some still prefer frontier models if budgets allow.
  • Multiple access paths: Kimi’s API, OpenRouter, OpenCode, Ollama, and integration into tools like Cursor and Claude Code proxies.

Privacy, censorship, and geopolitics

  • ToS allows training on user content with an opt-out caveat “in accordance with applicable law,” prompting skepticism about enforceability, especially in China.
  • Some argue US companies are more legally constrained and auditable; others counter that US agencies also pressure providers and that rule-of-law gaps exist everywhere.
  • Kimi’s first-party API shows strong censorship on topics like Tiananmen; open-weight deployments via other providers appear less restricted.
  • Broader debate over Chinese vs US AI strategies: Chinese labs lean heavily into high-quality open-weight models, framed variously as marketing necessity, compute-saving “bring your own inference,” and a way to weaken US incumbents.

Licensing and ecosystem

  • License includes a “modified MIT” style clause: apps above 100M users or $20M/month must attribute “Kimi K2.6” in the UI; some see this as mildly non-open but a “good problem to have.”
  • Ecosystem experiments include SVG “pelican on a bicycle” tests, with Kimi often producing ambitious but imperfect visual/code outputs.