Frontline Hotspot
Frontline Hotspot

Meituan Open-Sources LongCat-2.0: A 1.6T Coding Model Trained on Chinese Chips, Secretly #1 on OpenRouter

Meituan open-sources LongCat-2.0, a 1.6T sparse-MoE coding model trained entirely on Chinese ASIC with zero Nvidia GPUs, that secretly topped OpenRouter under the codename Owl Alpha for about two months. It beats Qwen3.6-27B across coding benchmarks, with three takeaways for everyday developers.

Published July 29, 20265 min read
<!-- meituan-longcat2-china-chip-hotspot | hotspot | Meituan Open-Sources LongCat-2.0: A 1.6T Coding Model Trained on Chinese Chips, Secretly #1 on OpenRouter -->

A food-delivery company open-sourced a 1.6-trillion-parameter coding model, trained start to finish without a single Nvidia GPU, that had been secretly sitting at #1 on OpenRouter for two months. Not a joke. It happened at the end of June 2026. The company is Meituan, and the model is LongCat-2.0.

1. What Happened: A Delivery App Open-Sources a 1.6T Coding Model

On June 30, 2026, Meituan open-sourced LongCat-2.0. Yes, that Meituan, the super app for food delivery and local life, not some AI lab.

The hard numbers: 1.6 trillion (1.6T) total parameters, sparse MoE architecture; each generated token activates only about 48 billion parameters, dynamically floating between 33 and 56 billion depending on query complexity. That means inference cost is far below what the headline 1.6T suggests. It has a native 1-million-token context window, achieved through the team's own linear-complexity attention mechanism, not by brute-forcing it with VRAM.

The most counterintuitive part: training ran entirely on Chinese-made AI chips (ASIC), zero Nvidia. This is confirmed by multiple sources, not just one party's marketing.

Then there's the backstory. Before going public, LongCat-2.0 served anonymously on OpenRouter under the codename "Owl Alpha" (owl-alpha) for about two months, quietly topping the usage charts. Plenty of developers had already been using it without knowing it came from Meituan, trained on domestic chips. Pricing is aggressive too: $0.038 per million tokens, free on cache hits.

2. Why It Matters: Three Things Proven at Once

First, Chinese compute can compete. A company that isn't even an AI lab trained a 1.6T frontier coding model on domestic ASIC, and the whole chain held together. Running without Nvidia and still landing in the top tier used to be "theoretically possible." Now it's "already happened."

Second, the open-source coding landscape shifted. The anonymous chart-topping run shows users vote with their feet: they don't care whether you're a closed-source giant or an open-source newcomer, as long as it codes well. That's a real dent in the moat of closed coding models.

Third, coding agents are the new battleground. Stop staring at general-reasoning scores. Terminal-Bench and SWE-bench Pro, the agent-style tasks, are where coding models actually compete in 2026. These benchmarks measure the ability to fix bugs, run tests, and complete multi-step tasks in a real engineering environment, far more meaningful than answering a multiple-choice question. A model can ace GPQA, but if it can't hold its own in a terminal, it won't help you write code.

Then there's cost. MoE keeps activation at 48 billion, and pricing lands at $0.038 per million tokens with free cache hits. That means a coding-agent workflow with its many round-trips and long contexts won't blow up the bill. Whether a model is usable is one question; whether you can afford it is another, and LongCat-2.0 offers something on both counts.

3. How to Read the Benchmarks: A Table vs Qwen3.6-27B

Per Reddit r/LocalLLaMA and digitalapplied, LongCat-2.0 versus Qwen3.6-27B:

BenchmarkLongCat-2.0Qwen3.6-27B
SWE-bench Pro59.553.5
Terminal-Bench 2.170.859.3
SWE-bench Multilingual77.371.3
RWSearch78.877.3
Writing Bench83.885.2
IMO-AnswerBench81.880.8
GPQA-diamond88.987.8

The lead shows up in coding and agent tasks, especially Terminal-Bench where it opens an 11.5-point gap. Writing Bench actually trails by 1.4 points. So it's a specialist coding model, not a generalist. On general reasoning (GPQA-diamond) the two are neck and neck; the real separation only appears on frontier coding tasks.

One caveat on sourcing. Information circulating in developer communities and on X (from a post by X user @VaibhavSisinty, single source, not multi-verified, so don't treat it as hard fact): training used 50,000+ domestic ASICs; OpenRouter processed 10.1 trillion tokens last month, up 242% month over month; it ranked #1 on Hermes Agent, #2 on Claude Code, #3 on OpenClaw; trained on 35 trillion tokens with no major rollbacks. These numbers sound impressive, but they're single-sourced, so treat them as leads, not facts.

4. Three Takeaways for Regular Developers

First, stop watching only the closed-source leaders. You thought coding models were the exclusive turf of a few closed labs, then a food-delivery company running on domestic chips topped the charts for two months without you noticing. Widen your view, the open-source camp may already have a usable contender.

Second, open-source coding models are good enough. SWE-bench Pro 59.5 and Terminal-Bench 70.8 would have been closed-flagship territory a year ago. If your coding-agent workflow is still waiting for "the next closed flagship" before you act, you can test an open model now, save on API costs, and keep things locally controllable.

Third, watch real benchmarks, not marketing numbers. 1.6T parameters and 35T training tokens are clickbait. What actually decides your coding experience is performance on agent tasks like SWE-bench Pro and Terminal-Bench, plus the per-token active parameter count (which sets inference cost). Next time a model drops, flip to the benchmark table first, skip the keynote.

The biggest signal from LongCat-2.0 isn't the parameter count, it's the identity. A food-delivery company, using domestic chips, trained a coding model that anonymously topped the charts. The barrier to frontier models is being lowered in a way nobody predicted. Models and compute are decoupling faster than most assumed, and the next player to emerge from an unlikely lane may already be on the way. Next time a "non-AI company" releases a frontier model, don't scroll past it, check the sources first.


References

This article is AI-assisted and human-edited. Last updated: 2026-07-29

Related

Frontline Hotspot

One API Endpoint Just Sold for $7 Billion: Stripe Swallows OpenRouter, and Model Routing Becomes the Toll Booth of the AI Era

Bloomberg reported Aug 16 that Stripe is acquiring OpenRouter for $7B+ - a 5.4x premium over its May $1.3B Series B valuation (PayPal's rival bid stalled; Stripe declines comment). OpenRouter = one API endpoint fronting 400+ models, 8M users, with Chinese-origin models capturing 46% of its US enterprise token usage per CNBC. Stripe's trilogy clicks shut: Metronome metered billing (Jan, ~$1B) + the MPP machine payments protocol (Mar 18, with Tempo) + OpenRouter routing. Three developer effects: routing neutrality in question, stronger motives for self-hosted gateways, and the call-and-charge gate closing in. Backdrop: SpaceX's $60B Cursor close and OpenAI's $1T IPO groundwork. Figures are media-reported; not investment advice.

Aug 18, 20268 min read
Frontline Hotspot

One prompt to final cut: JianYing Hub closes the AI video loop

According to a 9-21 report by Qbit, ByteDance's JianYing launched JianYing Hub, a one-stop AI video creation entry point on PC, whose product move is not about model parameters but about workflow, welding generation and editing into a single entry. Official positioning is a PC-side one-stop AI video creation workbench; the official page lists nine core functions (AI image and asset generation, storyboard scripting, module wiring and asset management, batch storyboard prompt generation, multi-model video generation with preview, direct hand-off to editing, AI post-editing, the JianYing Assistant Agent, and ByteDance asset import) along with a 14-step onboarding path and an official comparison table against Jimeng AI (source-side framing, not independently retested here). Two real changes stand out: generation results are not exported and re-imported but jump straight via "More Editing" into JianYing's multi-track timeline for AI extend, upscaling, frame interpolation, color grading, removal and vocal separation, an in-project closed loop replacing file exchange; and the JianYing Assistant Agent turns repetitive work into a single sentence by calling Skills for cutting voiceover, adding narration, fixing subtitles and batch production. The article's own judgment is that a workbench solves the last mile from asset to publishable cut rather than the ceiling of image quality, and that Hub is an orchestration layer rather than a generation engine, with three costs of the loop, ecosystem lock-in, tight asset-and-account coupling, and opaque pricing. Pricing, free quota, concurrency, credit rules, regional availability and duration or resolution limits are all unpublished and are stated as following the official app, with no invented numbers, and the launch timing is only a second-hand report.

Sep 22, 20267 min read
Frontline Hotspot

From 2.8s to 2.3s: can Qwen3.8 steal the interpreter's job?

In September 2026 Alibaba's Qwen team released Qwen3.8-LiveTranslate, a real-time simultaneous interpretation model opened through the Qwen AI platform and Alibaba Cloud Bailian as a WebSocket streaming API that can be embedded in meeting systems, live streams and support desks. Headline figures: average lag (LAAL) cut from 2.8 to 2.3 seconds; recognition input in 60 languages and speech output in 29; three capabilities, real-time speaker diarization plus voice cloning, source and translation emitted in the same frame, and long-context disambiguation, with video and audio input helping resolve ambiguity. Technically it rests on an Interleave single-stream architecture that caches already-heard audio and already-emitted translation instead of reprocessing each sentence, plus a Hybrid MoE Thinker-Talker pair, where the Thinker arranges video, audio, source and translation into one causal sequence and the Talker fuses translation with source audio into speech that keeps the original speaker's timbre. The article keeps its figures honest: 2.3 seconds is average lag rather than end-to-end first-packet latency, 60 and 29 are different units, the vendor comparison table is not independently retested, an unpublished metric is not the same as a bad one, pricing, rate limits, concurrency and regional availability are not invented, and the model is an API service rather than open source.

Sep 21, 20267 min read