![[AINews] Kimi K3 2.8T-A50B: the largest open model ever released; Opus 4.8-class at Sonnet 5 pricing](https://substackcdn.com/image/fetch/$s_!xVk0!,w_1200,h_675,c_fill,f_jpg,q_auto:good,fl_progressive:steep,g_auto/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F7d22c3fe-fde7-4c91-9e50-83b1597fe747_1958x1160.png)
a great week for open models continues.
Z.ai GLM has been getting a bit too much love recently, so it’s time for Kimi K3 to fight back! It’s hard to put the scale of today’s open model release in perspective, so thankfully Moonshot AI did it for us:
Their vibe reel was entirely edited by Kimi K3 and worth a watch: You can read SimonW and Arena for standard takes and rankings, none of which will be particularly unexpected given the large size of the model, but this pic best summarizes the K2.5 to K3 jump:
AI News for 7/15/2026-7/16/2026. We checked 12 subreddits,
[544 Twitters]and no further Discords.[AINews’ website]lets you search all past issues. As a reminder,[AINews is now a section of Latent Space]. You can[opt in/out]of email frequencies!
AI Twitter Recap
Moonshot AI launched Kimi K3 as a frontier-class open-weights model, with official claims that place it near top closed models and above prior open competitors.
Moonshot officially introduced
Kimi K3 as**“Open Frontier Intelligence”** with2.8T total parameters,** 1M-token context**,** native multimodal input**,** Kimi Delta Attention (KDA), and Attention Residuals**, and said the model is live on Kimi.com, Kimi Work, Kimi Code, and API, with** open weights promised by July 27, 2026**@Kimi_MoonshotMoonshot also highlighted product positioning around
long-horizon agentic coding andself-evolving workflows, plus “vision in the loop” coding/game-building workflows that iterate between code and screenshots@Kimi_MoonshotBefore the formal announcement, multiple accounts circulated leaked or app-sourced details that K3 was
2.8T params, calling it the** largest open-weight model ever**if weights ship as promised@scaling01,@scaling01,@eliebakouchThe official Kimi blog went live later and was widely shared as the primary technical source
@Jianlin_S,@scaling01,@Yulun_DuMoonshot’s own phrasing acknowledged a limitation: despite being highly competitive overall, K3 still has a
“noticeable gap in user experience” versusClaude Fable 5 andGPT-5.6 Sol@scaling01Arena announced that
Kimi K3 entered Agent Arena, plus Text, Vision, Document, and Frontend Code Arena, with community evaluations to follow@arenaArena then reported a major early result:
Kimi K3 became #1 in Frontend Code Arena with 1679 points, surpassing Claude Fable 5 and jumping from**#18 (K2.6) to #1**, ranking**#1 in 6 of 7 frontend domains** and**#2 in Gaming**@arenaArena later added that K3 has a
76% pairwise win rate in Frontend Code Arena, versus63% for Fable 5 and58% for GPT-5.6 Sol@arenaIn Text Arena, K3 landed at
#9 with 1486 points, a jump from**#38**, with top-10 placements in** creative writing, coding, and instruction following**, and #1 in several occupation slices@arenaArtificial Analysis published an independent evaluation placing K3 at
57 on the AA Intelligence Index, calling it** comparable to Opus 4.8 and GPT-5.5**, but still** behind Fable 5 and GPT-5.6 Sol**overall@ArtificialAnlysAA also reported K3 at
1668 Elo on GDPval v2,** 53% / #1 on AutomationBench-AA**, and** 1547 Elo on AA-Briefcase**, with** cost per task of $0.94**, about** 21% fewer output tokens than K2.6**across the full Intelligence Index run@ArtificialAnlysThe launch immediately triggered strong reaction from engineers and model-watchers who framed K3 as an
open-model milestone comparable to earlier DeepSeek moments@kimmonismus,@nrehiew_,@eliebakouch
Technical details
Architecture and systems details
Official specs:
2.8T total parameters,** 1M context**,** native multimodal input**(text + images),** text output**,** open weights by July 27**@Kimi_Moonshot,@ArtificialAnlysK3 uses
Kimi Delta Attention (KDA), which Moonshot says enables** up to 6.3x faster decoding in million-token contexts**@Kimi_MoonshotIt also uses
Attention Residuals (AttnRes), claimed to deliver**~25% higher training efficiency at <2% additional cost**@Kimi_MoonshotCommunity readers of the blog highlighted additional architecture details:
LatentMoE / Stable LatentMoE,** 16 activated experts out of 896**, implying an activation ratio under** 2%**@nrehiew_,@eliebakouchMore community-extracted details from the blog/report discussion:
per-head Muon,** QB load balancing / quantile load balancing**, and a new activation function called** SiTU (Sigmoid Tanh Unit)**@eliebakouchOne engineer noted the architecture as notable for combining
KDA + LatentMoE + AttnRes while scaling more than 2x over prior Kimi models@teortaxesTexKDA had a long incubation cycle: design reportedly started in
Jan 2025 and took**~1.5 years** to reach frontier scale@zxytim
Inference and serving
K3 pricing was reported as
$3 / 1M input tokens and**$15 / 1M output tokens**, with** cached input discounted 90% to $0.30 / 1M**@scaling01,@ArtificialAnlysSeveral posters compared that pricing to
Sonnet 5, with some noting Sonnet was temporarily cheaper until end of August, after which prices align more closely@kimmonismusA blended estimate at
80% input / 20% output came out to**$5.40 / 1M tokens**, vs**$9 for Opus 4.8** and**$10 for GPT-5.5**@jaminballArtificial Analysis estimated
$0.94 average cost per Intelligence Index task, versus**$1.04 for GPT-5.6 Sol** and**$1.80 for Opus 4.8**@ArtificialAnlysEarly live serving observations:
~28 tok/s via Moonshot API on OpenRouter@scaling01, and another observer saw** 26 tok/s**, calling it slower than Opus and speculating that** speculative decoding wasn’t yet enabled**@nrehiew_,@nrehiew_Moonshot’s blog reportedly recommends deployment on
supernode configurations with 64+ accelerators for best inference efficiency@teortaxesTexvLLM said Moonshot contributed a
KDA prefix caching implementation directly to vLLM, with support available** day 0**for official release@vllm_projectMoonshot’s KDA contribution was cited as important because
KDA breaks assumptions behind conventional prefix caching, so upstream runtime changes were required@vllm_project
Benchmarks and evals
Moonshot’s official benchmarking message, as summarized by others, positioned K3
behind only Claude Fable 5 and GPT-5.6 Sol among tested models, and ahead of** Claude Opus 4.8**@scaling01,@Yuchenj_UWOne cited number:
1687 on GDPval-AA v2, above Opus 4.8 and behind GPT-5.6 Sol at** 1747.8**in that comparison@scaling01Artificial Analysis’ independent numbers:
AA Intelligence Index: 57GDPval v2 Elo: 1668AutomationBench-AA: 53%, #1AA-Briefcase Elo: 1547AA-Omniscience: +18, with** accuracy 46% vs 33% on K2.6**, but** hallucination rate worsening to 51% from 39%**@ArtificialAnlys,@ArtificialAnlys
AA also reported
132M output tokens consumed for K3 across the Intelligence Index, versus166M for K2.6, i.e.** 21% reductionwhile gaining 13 index points**@ArtificialAnlysArena’s frontend result was especially prominent because it is a
pairwise human-preference arena, not just a static benchmark, and K3’s**#1 frontend rank** became one of the main launch headlines@arenaCommunity posts also highlighted strong results on
kernel optimization tasks, with some saying K3 was matching or beating Fable in certain kernel/codegen settings@nrehiew_,@scaling01One benchmark caveat came from
ProgramBench author Ofir Press, who said Kimi used a metric theydo not recommend: averaging implementation percentage rather than counting** fully working programs**, which can overstate usefulness@OfirPress,@OfirPress
Facts vs opinions
Facts / directly sourced claims
Kimi K3 is officially announced by Moonshot
@Kimi_MoonshotOfficially disclosed specs include
2.8T params,** 1M context**,** native multimodal input**,** KDA**,** AttnRes**,** open weights by July 27**@Kimi_MoonshotArtificial Analysis independently scored K3 at
57 Intelligence Index, with detailed task, cost, token, and benchmark data@ArtificialAnlysArena independently ranked K3
#1 in Frontend Code Arena and later reported its76% pairwise win rate@arena,@arenavLLM confirmed Moonshot contributed runtime support for
KDA prefix caching@vllm_project Opinions / interpretations
“DeepSeek moment,” “beginning of the US-China AI race,” and “everything changed” are editorial interpretations from observers, not established facts
@kimmonismus,@scaling01,@kimmonismusClaims that K3 “beats GPT-5.6 Sol on 11 of 14 benchmarks” and “Fable on 6 of 14” are aggregated community summaries and should be treated as contingent on the benchmark set and exact methodology
@scaling01Assertions that this implies Dario/Anthropic margin pressure, a geopolitical turning point, or near-term superintelligence are speculative commentary
@teortaxesTex,@JasonSeveral “distillation” insinuations were explicitly framed as jokes or conjecture rather than evidence
@yacinelearning,@dejavucoder Different opinions
Strongly supportive
Many engineers called K3 a genuine
frontier open model, especially because it appears to be** better than Opus 4.8**while being priced near Sonnet and planned for open-weight release@kimmonismus,@cline,@nrehiew_Supporters emphasized that this is no longer “good for open source,” but simply
competitive with top public closed models@tokenbender,@TheAhmadOsmanSome framed the release as evidence that
open models are now within weeks or a couple months of the frontier@nrehiew_Others argued this materially raises the odds that
future AGI-level systems are open@MaorShlomo Supportive but technically cautious
Artificial Analysis gave a more restrained view: K3 is
comparable to Opus 4.8 and GPT-5.5, but** still behind Fable 5 and GPT-5.6 Sol**on overall intelligence@ArtificialAnlysSimon Willison described K3 as significant, but also pointed readers toward nuanced notes and benchmark caveats rather than simple leaderboard hype
@simonwEthan Mollick’s hands-on impression: very good open-weights model, but** not Sol Max or Fable**@emollickOne user said K3’s intelligence is strong, but it is
slow, sometimes** over-checks**, and still trails Claude on taste/aesthetics@nrehiew_
Critical / skeptical
Bindu Reddy warned that K3’s benchmark story might be overstated unless validated on
hidden / uncontaminated evals like LiveBench, and argued that if the model “thinks forever,” real cost could be less favorable@bindureddyProgramBench maintainers objected to Moonshot’s metric choice, saying it can
inflate partial-credit performance relative to fully working programs@OfirPressArtificial Analysis also flagged a real weakness:
hallucination rate regressed on AA-Omniscience despite accuracy gains@ArtificialAnlysMultiple users noted that K3 currently appears to
think a lot, preserve long reasoning history, and may require more careful harness support than simpler chat-first APIs@scaling01,@Xianbao_QIANSome skepticism focused on economics and deployability:
2.8T open weights is impressive, but practical self-hosting may still be limited to well-funded teams@mbusigin
Political / strategic interpretations
A broad cluster of tweets framed K3 as proof that
Chinese labs are no longer far behind and that the US lead is shrinking@tszzl,@kimmonismus,@scaling01Others counterweighted that K3 still appears to lag the very best Western models in
usability / productization, even if raw capability is close@RyanGreenblatt,@scaling01Some argued that open Chinese models function as
economic pressure on US labs by compressing margins and commoditizing capability@francoisfleuretOthers viewed the inevitable next step as more
competition on harnesses, products, and deployment systems, not just raw model weights@AravSrinivas,@theo
Context
Why this matters technically
K3 is notable not just for raw size but for
scaling a non-standard attention stack into a frontier-class model: KDA + AttnRes + sparse MoE drew repeated attention from technically literate observers@scaling01,@eliebakouchThe launch is also a systems story: long-context serving, prefix caching, KDA runtime support, and deployment on large accelerator supernodes all matter if the weights are to be practically usable
@vllm_project,@teortaxesTexThe emphasis on kernel optimization,** chip design**,** agentic coding**, and** environment simulationsuggests Moonshot is optimizing for AI-improving-AI workflows**, not just chatbot benchmarks@18jeffreyma,@yong_zhengxin
Why this matters economically
The strongest repeated theme:
frontier-ish performance at materially lower price than top closed models, though not at bargain-basement open-model prices@kimmonismus,@cline,@jaminballArtificial Analysis’ task-cost framing is especially relevant for practitioners: if K3 is near
GPT-5.6 Sol cost-per-task and belowOpus 4.8, the real question becomes where it slots into agent stacks, coding platforms, and self-hosted infra@ArtificialAnlysSome noted the paradox that “open weights” does not automatically mean “cheap to run”: a
2.8T model with64+ accelerator deployment guidance is frontier infrastructure territory@teortaxesTex,@mbusigin
Why this matters geopolitically
Many reactions explicitly tied K3 to export controls, US-China competition, and the narrowing gap between Chinese open labs and US closed labs
@scaling01,@tszzl,@kimmonismusSeveral commentators argued that K3 weakens the common narrative that Chinese models trail by
6–8 months, because it appears to outperform a closed US model from** late May**only weeks later@kimmonismusOthers stressed that “capability parity” is not the same as full-stack parity: product reliability, inference scale, deployment margins, and proprietary post-training may still favor US incumbents
@RyanGreenblatt Early hands-on signals
Users reported K3 building impressive
web experiences,** games**, and** shader/code artifacts**, reinforcing the Frontend Arena result@johnlindquist,@ChrissGPT,@intheworldofaiOne user said K3 generated a
CS:GO × Portal clone in3 shots using**~600k tokens**, costing**$3.24** by API pricing, compared with claimed higher costs on Fable and GPT-5.6 Sol@ChrissGPTAnother reported K3 continuously working for hours over near-
1M context to build aweb DOS emulator with low human intervention@bigeagle_xdAt the same time, several users noted it can be
verbose,** slow**, and heavily reliant on** thinking-history preservation**, implying that serving/harness defaults will matter a lot@nrehiew_,@Xianbao_QIAN,@bigeagle_xd
Open-source/open-weights debate The surrounding discourse included the usual complaint that “open weight” is not “fully open,” but several commenters pushed back that this distinction is often impractical at frontier scale and that inspectable, fine-tunable weights still matter
@Dan_Jeffries1,@ClementDelangueYulun Du said the delay before weight release was to ensure a
smooth rollout with inference partners, signaling that ecosystem readiness mattered as much as the checkpoint itself@Yulun_DuvLLM maintainers and others treated Moonshot’s upstream contributions as evidence that the launch is not just “marketing open,” but also includes meaningful OSS infra work
@vllm_project,@woosuk_k Benchmarks, contamination, and what to watch next
Several people cautioned that current public benchmark ecosystems saturate quickly, and that hidden evals or stack-level evals will be more informative
@bindureddy,@gdb,@WolfBenchAIObservers specifically asked for follow-up on
METR time horizons,** cyber ranges**,** FrontierMath T4**,** ARC-AGI-2/3**,** CritPt**,** token usage**, and broader long-horizon agent evals@scaling01The most credible near-term follow-up points are:
whether the
weights ship on time what
third-party serving stacks achieve for throughput/costhow K3 performs on
hidden evals and real production agent tasks whether Moonshot closes the
UX/post-training gap they themselves acknowledged@Kimi_Moonshot,@scaling01,@ArtificialAnlys
Open Models, Inference Stacks, and Retrieval Infrastructure
vLLM and serving ecosystem support landed quickly:vLLMsaid Moonshot contributed a** KDA prefix-caching implementation directly to vLLM**, enabling** day-0support once weights drop. This matters because KDA breaks some conventional prefix-caching assumptions. The post underscores that long-context architectural innovation increasingly requires coordinated systems work, not just model release.NVIDIA shipped a notable open retrieval release:NVIDIAlaunched Nemotron 3 Embed 8B**, claiming**#1 overall on RTEB**, and partners quickly made it deployable, includingBasetenandTurbopuffer. A more detailed community summary by@kimmonismusreports78.46 NDCG@10 on RTEB and75.45 on MMTEB Retrieval, with NVIDIA arguing stronger retrieval reduces downstream agent token usage. The release also includes** 1B BF16and 1B NVFP4variants, with the NVFP4 version reportedly offering up to 2× BF16 throughputon Blackwell while retaining >99% retrieval quality. LiteParse added a gRPC interface for backend document pipelines**:LlamaIndexintroduced** liteparse-grpc**, exposing PDF/Office/image parsing, rendering, and OCR-complexity estimation over gRPC with protobuf definitions and generated clients. This is a practical infra improvement for polyglot microservice stacks where REST isn’t ideal.Managed vector/search infra also expanded:Weaviateannounced** Managed Weaviate on DigitalOceanin public preview, running the unmodified open-source engine ( v1.37.1 at launch**) with HA, autoscaling, backups, forks, and control-plane observability.
Agents, Harnesses, and System Design Becoming the Real Product Layer
Harnesses were a recurring theme across builders: Harrison Chase’s conversation with Factory AI’s Eno Reyes was repeatedly shared as a case for why “the harness matters more than the model” (Harrison,LangChain). Chase later argued teams should “own the harness,” “own the context and memory layer,” and “own model optionality” rather than rent intelligence from a single provider (thread).There’s growing interest in open standards for memory and knowledge representation:Harrison Chasepromoted** OKF (Open Knowledge Format)as an “open standard for memory,” whileBrace Sprouldetailed OpenWiki’s adoption and the benefits for search, retrieval, and codebase memory.Agent self-improvement and scheduled multi-agent workflows are becoming mainstream topics:@omarsar0highlighted a survey on self-improving agentic systems**, and elsewhere described using an “LLM Council” with recurring scheduled research updates (thread). On the product side,Google AI Studioadded afree tier for Managed Agents, plus** max_total_tokensfor pausing/resuming long runs and native cron triggers**.** Perplexity’s infra direction was also notable**:NVIDIA AI Infrahighlighted Perplexity’s new** SPACEsecure sandbox platform, with early tests on NVIDIA Vera CPUshowing up to 1.9× faster sandbox starts**—a reminder that sandbox startup latency is now part of agent throughput engineering.
OpenAI and Anthropic: Safety, Productization, and Developer Workflow Updates
OpenAI acknowledged a dangerous Codex/GPT-5.6 failure mode around file deletion:Thomas Sottiauxsaid OpenAI investigated rare reports where** GPT-5.6 unexpectedly deleted files**, most commonly when** full access modewas enabled without sandboxing or auto review, and when the model attempted to override$HOME** for temp directories but mistakenly deleted**$HOME** itself. OpenAI says it is updating developer messaging, nudging users toward safer permission modes, and adding harness safeguards, with a detailed postmortem forthcoming.OpenAI continued to ship workflow features around Codex and PR review:OpenAI Devsadded** PR Chatand inline code editingin Codex for reviewing and editing pull requests in context. OpenAI also announced Office Hours around GPT-5.6, ChatGPT, and Codex**(source).** Anthropic upgraded Claude Code review depth**:ClaudeDevsintroduced** effort levels**for/code-review
, from low cost/low effort toultra, where a fleet of reviewer agents reproduces findings independently. Anthropic says low effort beats other code-review tools on findings per token, while high/ultra improve severe-issue recall and reduce false positives.Voice remains a major adoption vector:Sam Altmansaid he now talks to ChatGPT more than he types, calling the new voice model a threshold-crossing UX shift. Separately, OpenAI published GPT-Live usage limits in its help center, summarized by@athyuttamre:Pro users get unlimited daily usage, while Plus/Go and free tiers have bounded live minutes.
Multimodal Video, Real-Time Media, and Creative Tooling
Google pushed Gemini Omni into Vids:GoogleandGoogle WorkspacelaunchedGemini Omni for video generation/editing inGoogle Vids, plus** personal avatarsbuilt from a selfie and voice recording. Google says generated clips include SynthIDwatermarking and that avatars are restricted to a user’s own account/likeness (details).NotebookLM’s rebrand signals tighter Google product integration:Gemini Notebookannounced that NotebookLM is now Gemini Notebook**, with existing standalone behavior intact but deeper integration coming via the** Gemini appand eventually Search**. This looks like a packaging/integration move more than a model change.** Real-time and agentic media tooling kept advancing**:DecartAIintroduced** Lucy 2.5**, a more capable realtime live AI video editor;falmade** Lucy 2.5 Realtimeavailable over WebRTC for live video-to-video editing.falalso launched LTX-2.3 Reframefor aspect-ratio conversion with generated scene completion. Meta expanded media model distribution**:Meta,AI at Meta, andAlexandr Wangall announcedMuse Spark 1.1 onOpenRouter, reflecting continued demand for frontier-ish generative media models via neutral routing layers.
Robotics, World Models, and Embodied AI
A high-reliability robotics model stood out:Tony Zhaointroduced** ACT-2 Preview**, described as the first robotics model to unify broad generalization with high reliability. The headline claim is striking:a single fine-tuning example can teach Memo a new behavior that generalizes, withzero-shot, real unseen homes, 99% success rate.** Reka discussed world-model data operations at production scale**:Rekapointed to an episode on how a sub-100-person team prepares** petabytes of video datafor world model training**, emphasizing that the bottleneck is often data platform engineering, not just model architecture.** There’s continuing work on embodied world-model architectures**:@lixin4everhighlighted a DAMO effort using** tri-branch DiT**,** joint cross-modal attention**, and** 250M+ RGB frames with dense depth and optical flow annotationsto turn a video generation model into a 4D embodied world model**.
Top Tweets (by engagement)
Kimi K3 official release: Moonshot’slaunch postwas the day’s dominant technical tweet, combining model specs, architecture, and release timeline.Kimi K3 Arena breakthrough:Arena’s Frontend Code Arena #1 postdrew exceptional engagement because it framed K3 as not just strong “for open weights,” but directly ahead of a top closed competitor in a visible product task.OpenAI safety incident disclosure:OpenAI’s explanation of GPT-5.6 file deletionswas one of the most consequential engineering/safety updates, because it tied model behavior to permission modes, sandboxing, and harness safeguards.Anthropic’s multi-effort code review:Claude Code’s/code-review
effort levelsis a meaningful productization signal for agentic software engineering: not just “AI review,” but tunable cost/recall tradeoffs and subagent-based verification.
AI Reddit Recap
/r/LocalLlama + /r/localLLM Recap
1. Kimi K3 Launch and Frontier Benchmarks
(Activity: 399):Kimi K3 weights to be released on the 27th.The Commenters are excited about the open-weight release but expect local inference to be impractical due to the model’s apparent scale, joking that even if someone runs the rumoredannouncement imagestates that Kimi K3 is now available through kimi.com, the Kimi app, Kimi Work desktop client, Kimi Code, and the Kimi API, with the current default “thinking intensity” set to max / extreme. Per the linked official posts (WeChat,English blog), full model weights and additional technical details are scheduled for release by July 27, 2026, which is the main technical significance of the image.2.8T
-parameter model on a24 GB
VRAM laptop, it would be at unusably low throughput.Commenters highlight that
Kimi K3’s apparent2.8T
-parameter scale makes local inference impractical for nearly all consumer setups; one linked screenshot of the announcement/spec context ishere. The discussion frames the weights release as valuable for openness and research even if typical local hardware would be limited to extremely slow or unrealistic runs, e.g.“24 Gb VRAM laptop…0.01
*token per sec.”*A technically substantive workflow suggestion was to use
Kimi’s largest models for planning/strategy while pairing them with a smaller implementation model, similar toDeepSeek’s large/small model split. One commenter specifically asked for asub-300B
MoE or smaller MoonshotAI model for lighter coding workloads, noting that K2.7 Code appeared to improve overK2.6 andK2.5 for agentic coding use cases.
(Activity: 1057):Kimi K3 released on web and appKimi K3 was announced as available on web/app, with claimed specs of2.8T
parameters and1M
**context, and claims of leading performance in coding, agentic tasks, long-horizon reasoning, visual understanding, and agent-swarm workflows (**Commenters focused on deployment practicality: ascreenshot). No benchmark data, architecture details, license, or Hugging Face/open-weight release link were provided in the post.2.8T
model would be extremely difficult to run locally, with one noting even a1.58-bit
quant likely would not fit in512 GB
RAM. Others questioned whether it would become the largest open-weight model if uploaded to HF and said they were waiting for benchmarks.Discussion focused on the
hardware infeasibility of running Kimi K3 locally: commenters cite the reported2.8T
parameter size and note that even a1.58-bit
quantized version would likely exceed512 GB
RAM, putting it far beyond typical consumer or even workstation setups.Several users framed Kimi K3 as potentially one of the
largest open-weight models if released on Hugging Face, with interest centered on forthcoming benchmarks. One commenter compared anRTX 6000 Pro96 GB
card against the model’s memory requirements, estimating it is still more than12x
short, underscoring that even high-end single-GPU hardware is not sufficient.
(Activity: 1487):Kimi K3 BenchmarksThe image is a coding benchmark chart for Kimi K3 (image), comparing it with models such asGPT-5.6 Sol
,Fable 5
,Opus-4.8
,GPT-5.5
, andGLM-5.2
**across six coding evaluations. Kimi K3 is highlighted in blue and is shown leading Program Bench and SWE Marathon, while placing second on Terminal Bench 2.1, FrontierSWE, and Kimi Code Bench 2.0, suggesting very strong benchmark-level coding performance.**Commenters cautioned that the chart only reflects benchmark performance, not real-world usage, but one argued Chinese models appear “not even 6 months behind US models,” perhaps “6 days behind.” Another comment, “2TB VRAM Is All You Need,” appears to be a joke or jab about likely heavy inference hardware requirements.A commenter interprets the shared Kimi K3 benchmark image as evidence that
Chinese frontier models are nearly at parity with U.S. models, saying that based on benchmarks alone they appear*“not even 6 months behind US models”and possibly closer to“6 days behind”*. They explicitly caveat that this isbenchmark-only and may not reflect real-world usage quality or reliability.
(Activity: 854):KIMI K3 Beats Claude Fable and GPT 5.6 sol in arena.ai!!!The image is a Code Arena WebDev overall leaderboard screenshot (image) dated Jul 16, 2026, showing Moonshot’skimi-k3
ranked #1 with a score of1679
**, ahead of**`claude-fable-5`
**and**`gpt-5.6-sol-xhigh`
on front-end web development tasks. The post frames this as surprising because Kimi is beating “frontier” models described as**“too dangerous”**for public release; a commenter notes that on the broaderarena.ai text leaderboard, it is not #1 but still appears competitive withgemini-3-pro
andgpt-5.6-sol-xhigh
. Comments focus on whether this implies China is only*“6 days behind the west”*and whetherkimi-k3
will actually be released asopen weights, which would affect its practical significance beyond leaderboard placement.A commenter links the
arena.ai text leaderboard(https://arena.ai/leaderboard/text) and notes that** Kimi K3is not leading the main text arena, but is reportedly scoring in the same range as Gemini 3 Proand GPT 5.6 sol (xhigh)**, which they consider technically notable for a Chinese model release.There is uncertainty over whether
Kimi K3 will be released asopen weights, which is a key technical distinction for local deployment, fine-tuning, and reproducibility compared with API-only leaderboard performance.One commenter raises a benchmark-validity concern: if Arena users disproportionately judge models on generated
Three.js / 3D browser games, Kimi may have been optimized for that task distribution. They argue this could inflate perceived capability because visually impressive generated games may score well with casual evaluators even if they are not a robust measure of general coding or reasoning ability.
(Activity: 656):Kimi K3 achieves 3rd Place on ArtificalAnalysis, beating out Claude Opus 4.8Theimageis a technical benchmark chart from Artificial Analysis showing Kimi K3 in3rd
place on the Intelligence Index with a score of57
, narrowly ahead of Claude Opus 4.8 at56
and behind Claude Fable 5 (60
) and GPT-5.6 (59
). Commenters add that follow-up charts forcost per taskandoutput tokens per tasklook “super promising,” but the main technical caveat is whether the model sustains quality in long sessions at roughly Sonnet-like costs and around30 t/s
. The main skepticism is benchmark fatigue: one commenter says they’ve “seen enough bar-charts” and wants real long-session usage reports before accepting the ranking as meaningful.Commenters focused less on the headline rank and more on operational efficiency: one noted that at roughly
Claude Sonnet-level pricing and around30 tokens/s
, Kimi K3 would need to show stronglong-session reasoning efficiencyrather than just benchmark-bar performance. This frames the model’s ArtificialAnalysis placement as needing validation through sustained interactive workloads, not only leaderboard scores.A linked follow-up claimed Kimi K3 looks promising on
cost per task andoutput tokens per task, sharing ArtificialAnalysis-style charts:https://preview.redd.it/ayxi7od6bndh1.png?width=1753&format=png&auto=webp&s=14190215c0ae612463e1d7e9a7587b2d5e0c5b48. The discussion implies Kimi K3’s competitiveness may come from a favorable efficiency/price profile in addition to raw benchmark rank, especially if it is outperforming or approaching models likeClaude Opus 4.8.
Keep reading with a 7-day free trial #
Subscribe to Latent.Space to keep reading this post and get 7 days of free access to the full post archives.