Cursor Rewrote the GPU Kernel. Here's Why Your AI Coding Tools Will Too.
胡新宇
发布于 2026-08-16
Cursor open-sourced Mixture-of-Kittens (MoK), a fused MoE execution kernel that pushed multi-node signaling latency from 103us to 18us and lifted 512-GPU training throughput 41%. Why an IDE company rewrote the GPU kernel — and what it means for the rest of the AI stack.
Cursor Rewrote the GPU Kernel. Here's Why Your AI Coding Tools Will Too.
On August 7, 2026, Cursor open-sourced Mixture-of-Kittens (MoK) — a fully fused MoE execution layer that pushes token dispatch, cross-GPU communication, and expert compute into a single kernel on GB300 NVL72 racks. Two numbers from their benchmark explain why this matters: multi-node signaling latency dropped from 103 μs to 18 μs, and end-to-end training throughput rose 41% on 512 GPUs.
That second number is the headline. The first number is the story.
The bottleneck in modern MoE training is no longer bandwidth. It's the orchestration around it.
"Fast hardware" already stopped being the answer
In late July, NVIDIA disclosed that GB300 NVL72 hit 1,648 TFLOPS per GPU when training DeepSeek-V3 across 256 GPUs. The rack itself is wild: 72 GPUs in one NVLink domain, 130 TB/s of aggregate bandwidth. On paper, data should fly.
So why is anyone rewriting the kernel?
The honest answer is that MoE training doesn't look like a bandwidth chart. Each forward pass requires a sequence of cross-GPU operations: dispatch tokens to whichever GPU holds their assigned expert, run the grouped GEMM, combine the results back at the original token positions, then do the same three steps in reverse for backprop. Six communication-heavy steps per layer, every step.
