Tencent Breaks Its Conservative Mold: Hunyuan Hy4 Debuts With 770B MoE, Native Computer Use, and an Open-Weights Counterattack

Tencent Hunyuan officially unveiled Hy4, a 770B MoE flagship activating 49B parameters per token with 1M context and an Apache 2.0 open-weights roadmap; introducing native Computer Use tailored for Blender and CAD pipelines alongside a 65.7% SWE-bench Pro score and 0.3 RMB cached input pricing, marking an aggressive counterattack from China's traditional tech titan.
If you spent significant time inside global and domestic open-source developer communities over the past two years, you likely formed a rigid set of archetypes for frontier model creators. DeepSeek was revered by hackers as a sacred temple, regularly schooling Silicon Valley peers with hyper-optimized CUDA kernels and frugal algorithmic breakthroughs. Alibaba's Qwen functioned like a relentless assembly line, dropping full-suite open-weights across every conceivable parameter size onto Hugging Face every few weeks. Tencent, by sharp contrast, felt like a middle-aged corporate veteran sipping green tea in a quiet corner of the room. Despite sitting atop the largest social graph, gaming empires, and server infrastructures in Asia, Tencent appeared stubbornly conservative, almost lethargic, regarding public frontier models. When developers brought up Hunyuan, the standard verdict was a dismissive chuckle: pleasant enough for internal WeChat summaries and enterprise meetings, but hardly a player on the frontier stage.
That dismissive consensus shattered without warning this morning, when Tencent dropped an unannounced industrial titan onto the table and sent shockwaves through the global open-source community.
A Quiet Penguin Rolls Out a Heavy Armored Dreadnought
This morning, the Tencent Hunyuan engineering division officially unveiled the production release of Hy4. If you glanced solely at the version string, you might have easily mistaken it for another routine enterprise maintenance patch. However, a single look at the underlying architectural specifications and verified benchmark audits reveals that this notoriously defensive tech conglomerate just wheeled out every heavy piece of artillery in its armory.
The headline specifications are staggering: a total parameter footprint of 770 billion (770B) configured as a sparse Mixture-of-Experts (MoE) engine, activating just 49 billion (49B) parameters per processed token, backed by a native 1-million-token (1M) context horizon. Far more disruptive than raw scale alone, Tencent confirmed that complete model weights will roll out under a permissive Apache 2.0 open-source license, accompanied by an unprecedented capability rarely seen from domestic frontier laboratories: native Computer Use.
Right when industry observers assumed the open-weights arena had settled into a predictable equilibrium, the tech world's most deliberate defense-first player rolled an armored juggernaut out of its Shenzhen subterranean hangars.
Looking Past the 770 Billion Figure to the 49 Billion Active Gears

In an era of hyper-inflated parameter counts, touting hundreds of billions of theoretical weights no longer impresses seasoned engineers. What separates an unusable, cash-incinerating monolith from an indispensable production weapon is inference efficiency, sparsity discipline, and mechanical architectural elegance.
Hy4 approaches scale through a finely tuned Mixture-of-Experts topology. In essence, it deconstructs its 770-billion-parameter knowledge base into an expansive syndicate of domain-specialized experts. Yet, during any individual token generation step, the routing matrix selectively awakens a lean 49 billion parameters. This clever design yields the reasoning depth of a near-trillion-parameter frontier brain while maintaining the execution latency, throughput, and hardware profile of a mid-sized 50B workhorse.
The underlying structural innovations demand closer scrutiny from systems engineers: 1. Gated DeepSeek Sparse Attention (Gated DSA): Tencent integrated gated sparse attention mechanisms, actively assimilating cutting-edge architectural research on cross-layer sparse indexing and aggressive Key-Value cache sharing to ensure that processing 1-million-token source trees will not violently detonate GPU memory ceilings. 2. Identity Hyper-Connections (iHC): To overcome the vanishing gradient pathologies and cross-layer entropy decay endemic to massive neural structures, Hy4 engineers deployed direct inter-layer bypass highways, establishing the structural backbone that keeps its reasoning trajectories lucid across hundreds of autonomous tool steps. 3. Hardware-Software Co-Design Optimization: Far from an academic toy produced inside an isolated university computer cluster, Hy4 was forged directly across Tencent's punishing internal infrastructure, with custom kernel operators and ultra-low-latency interconnect pipelines tuned specifically for high-throughput inference serving.
The practical impact of these architectural investments shows up starkly across grueling engineering evaluation benchmarks. On SWE-bench Pro, widely considered the premier benchmark for verifying end-to-end bug resolution across messy multi-file codebases, Hy4 registered an elite 65.7% resolution rate. On the notoriously punishing DeepSWE engineering benchmark, its performance surged from the previous generation's 28.0 to an impressive 64.3. Meanwhile, on Terminal-Bench 2.1, which measures real-world command-line navigation and shell tool interaction, it achieved an 85.4% pass rate. These verified metrics prove that Hy4 has transitioned far beyond writing elementary sorting algorithms, operating instead as an autonomous engineering specialist capable of multi-file refactoring, diagnostic tracing, and continuous build validation.
Moving Computer Use from a Geek Toy into CAD and Blender Pipelines

While a 770B MoE architecture and top-tier code benchmarks satisfy frontier enterprise expectations, Hy4's most radical departure from convention lies in its implementation of Computer Use.
Over the previous six months, automated computer control features sparked intense curiosity across hacker circles, yet early adopters quickly discovered that practical utility rarely extended beyond brittle consumer demonstrations like ordering a delivery meal in a browser or firing off elementary git commands in bash. The instant an autonomous agent encountered intricate enterprise software—where an interface widget shifted by two pixels or an unpredicted operating system dialog intercepted execution—the workflow collapsed immediately.
Tencent approached the challenge with an intensely pragmatic, blue-collar industrial philosophy. Instead of wrapping Computer Use in abstract conceptual marketing, the team aimed its automation directly at two notoriously intricate production bottlenecks: Blender 3D mesh modeling and CAD mechanical design.
In verified workflow demonstrations and technical documentation, Hy4 showcases a dual-channel operating paradigm blending terminal command execution with direct graphical user interface steering. When presented with an instruction to construct a functional mechanical linkage from two-dimensional engineering blueprints, the model does not simply dump a raw Python script for the user to troubleshoot manually. Instead, it launches a dedicated Blender virtual container, issuing automated script calls to generate geometric vertices while concurrently inspecting viewport renderings, checking polygon topology, and adjusting coordinate axes directly through visual mouse-and-keyboard interactions.
This hybrid control architecture—combining programmatic shell logic with closed-loop visual validation—drags autonomous agent technology out of synthetic benchmark sandboxes and plants it firmly onto the demanding factory floor of modern industrial manufacturing, architectural design, and interactive game development.
The Economic Shock of Three Cents per Million Tokens
Hobbyists argue over benchmark scores, but enterprises make purchase decisions based strictly on financial ledger audits. Any technology that ignores compute economics fails to survive three quarters in industrial deployment.
Alongside the formal Hy4 release, Tencent Cloud TokenHub published a pricing schedule that sent immediate shockwaves through enterprise infrastructure budgets: 1. Standard Inference Input: 6 RMB per million tokens (approximately eighty-five cents). 2. Standard Inference Output: 18 RMB per million tokens (approximately two dollars and fifty cents). 3. Cached Input Ingestion: 0.3 RMB per million tokens (approximately four US cents).
Consider the mathematical reality of these figures for production environments. When a software engineering enterprise anchors a massive corporate repository comprising dozens of modules and hundreds of thousands of context tokens inside persistent key-value cache, the model can inspect, query, and refactor code for a mere 0.3 RMB per million tokens. Compared against proprietary overseas frontier APIs that demand tens or hundreds of dollars for comparable token volumes, this tariff amounts to an aggressive price war across enterprise compute.
Furthermore, everyday consumers do not need to register developer consoles or write API wrappers to access this horsepower. This morning, Tencent rolled out an automated background engine upgrade to the consumer Tencent Yuanbao mobile application. Ordinary users activating deep reasoning or image inspection are now interfacing directly with this 770-billion-parameter engine free of charge.
Deploying ultra-frugal infrastructure pricing to capture commercial developers on one side, distributing free consumer mobile applications to amass end-user mindshare on the other, and suspending an open-weights release above the industry like a sword of Damocles: this textbook ecosystem playbook exerts suffocating margin pressure on proprietary laboratories reliant on premium closed API revenues.
Sober Realities Behind the 770B Weight Footprint
Amid widespread enthusiasm across developer forums, responsible technology analysis requires an immediate cold-water audit: Hy4 is exceptionally powerful, but it is not a turnkey magic wand that every garage startup can casually self-host.
The first bottleneck is the formidable barrier to local on-premise deployment. Even when compressed through aggressive FP8 or INT4 quantization formats, a 770-billion-parameter footprint demands a staggering quantity of high-bandwidth video memory. For bootstrapped development teams or independent software vendors, running full local weights across personal workstations remains financially prohibitive without dedicated multi-GPU clusters equivalent to B200 class hardware. For the vast majority of practitioners over the coming quarters, consuming Hy4 through cloud API endpoints remains the only economically viable path.
The second operational reality is the latency penalty imposed by extensive self-verification loops. Early developer reports indicate that when tackling intricate multi-step tasks, Hy4 occasionally exhibits a compulsive need for recursive cross-checking, triggering iterative diagnostic runs and extended reflection chains. While this meticulous deliberative architecture underpins its 65.7% SWE-bench resolution score, it simultaneously elongates end-to-end execution latency and inflates intermediate reasoning token consumption on complex queries.
Nevertheless, this morning's release decisively redraws the competitive map for global and domestic frontier artificial intelligence: - For everyday consumers: Launching the Tencent Yuanbao app unlocks frontier reasoning, code diagnostics, and multimodal visual analysis without subscription fees or technical onboarding hurdles. - For software developers and startups: Abandon plans to purchase private server racks; leverage TokenHub's 0.3 RMB cached token pricing to construct lean agentic products across document analysis, code review, and Blender automation. - For the wider industry: The announcement shatters the assumption that open-weights leadership belongs exclusively to a few agile newcomers. When a battle-tested tech conglomerate sheds its conservative posture and deploys a 770B open-weights dreadnought, the real structural reallocation of compute capital has officially begun.