
On October 29, Dowson Tong announced at the 2026 Tencent Global Digital Ecosystem Summit that the official version of Hunyuan Hy4 is coming soon. Compared to the Hy4 preview open-sourced in August, the official release strengthens long-horizon tasks, real-world productivity tasks, and chain-of-thought efficiency, while introducing visual understanding for the first time. For anyone building enterprise agents, the keyword to watch is: long-horizon tasks.
On August 28, 2026, Tencent Hunyuan released and open-sourced Hy4 preview — 770B total parameters, 49B active parameters, 1M context length, MoE architecture. In an internal blind test with 163 experts and 203 engineering tasks, it scored 2.99/4, slightly outperforming GLM 5.3 and Kimi K3.
Hy4 preview is already live in Yuanbao, ima, WorkBuddy/CodeBuddy, and other products. The API is accessible via Tencent Cloud TokenHub and OpenRouter. In its first week on OpenRouter, Hy4 processed more tokens than any other model globally.
Now the official release is coming. Based on information from the ecosystem summit, Hy4 official has three core upgrades:
Upgrade Direction | What It Means | Impact on Agents |
|---|---|---|
Long-horizon task strengthening | Longer task chains, more steps of continuous reasoning and execution | Agents can handle complex tasks requiring dozens of steps over hours |
Chain-of-thought efficiency | Reduces "excessive self-verification," converges faster | Agents respond quicker, consume fewer tokens |
Visual understanding | First-time support for image understanding and visual reasoning | Agents can process screenshots, reports, document images |
Most large language models today excel at "single-turn Q&A" — you ask a question, it gives an answer. But enterprise agents don't need single-turn Q&A. They need multi-step, long-duration, stateful task execution.
Consider a customer service agent handling "check my last week's orders and process a refund." It needs to:
Six steps, involving 3+ tool calls and 2 model inferences. That's a simple scenario — complex business workflows may require 20+ steps over several hours.
This is what long-horizon tasks mean: not that the model is smarter, but that it can maintain task goal consistency over an extended time span, keep intermediate steps on track, and self-recover from exceptions.
In the Hy4 preview era, the model already had a solid foundation for long-horizon tasks — 1M context window, optimization for agent scenarios. The official release further strengthens this direction, meaning:
The value of long-horizon task capability for enterprise agents is amplified to its fullest in the "24/7 always-on service agent" scenario.
Unlike "fire-and-forget" tool-type agents, service-type agents are perpetually online, continuously processing user requests:
Dimension | Tool-Type Agent | Service-Type Agent |
|---|---|---|
Operation mode | Trigger → Execute → End | 7×24 always-on listening |
Single task duration | Minutes | Potentially hours |
Task chain | 1-3 steps | 10-30 steps |
Exception tolerance | User can retry | Must self-recover |
Typical scenarios | Code generation, document translation | Customer service, ticket routing, data inspection |
Service-type agents have three hard requirements from the model:
Hy4 official's long-horizon task strengthening directly addresses these three requirements.
Hunyuan Hy4's long-horizon task capability requires platform-level support to land in enterprise scenarios. Tencent Cloud ADP (Agent Development Platform) 4.0 happens to have native design in the "long-horizon task execution" dimension:
① Agentic Loop Cloud Workbench
A core feature of ADP 4.0 — agents run in a continuous loop mode in the cloud workbench, with task state persistence and breakpoint recovery. Hy4's long-horizon reasoning combined with ADP's agentic loop enables service-type agents that "execute a single task continuously for hours and automatically recover after interruption."
② Agent ↔ Workflow Bidirectional Invocation
Long-horizon tasks typically follow a "plan-then-execute" pattern: the agent first decomposes the task, then invokes workflows step by step. ADP's bidirectional invocation lets agents dynamically orchestrate workflows, while each workflow node can call back the agent for judgment — this flexible orchestration is the foundation of long-horizon task execution.
③ Full-Link Trace Replay
The most failure-prone aspect of long-horizon tasks is "intermediate steps going off track without anyone noticing." ADP's trace replay records every step's input, output, tool calls, and model interactions, supporting step-by-step replay — on a 20-step long-horizon task, you can see exactly which step started going wrong.
④ Canary Release and Auto-Fallback
Service-type agents cannot "go all down on error." ADP supports canary release (validate with 10% traffic first) and auto-fallback (degrade to rule engine or human fallback when agent exceptions occur), ensuring business continuity during long-horizon task failures.
⑤ Native WeCom Integration
Service-type agents are typically delivered through WeCom (Enterprise WeChat). ADP has native WeCom integration — agents are published to WeCom with one click, team members use them directly, and results are pushed through WeCom.
After Hy4 official release, these platforms will integrate it immediately:
Platform | How to Experience | Best For |
|---|---|---|
Tencent Cloud ADP | Build agents with Hy4 model directly in ADP workbench | Enterprise developers, business teams |
Yuanbao | Chat with Hy4 directly in Yuanbao App | Individual users |
ima | Use Hy4 capabilities in ima | Knowledge workers |
WorkBuddy / CodeBuddy | Experience Hy4 in coding and office scenarios | Developers, productivity users |
Tencent Cloud TokenHub | Access Hy4 via API | Teams with in-house dev capability |
OpenRouter | Call Hy4 API via OpenRouter | International / multi-model users |
For enterprise users, ADP is the best entry point to experience Hy4's long-horizon task capability. The reason is simple: Hy4's long-horizon tasks are an "agent-level" capability, not a "conversational-level" one. Chatting with Hy4 in Yuanbao won't show you the value of long-horizon tasks — only by building an agent on ADP that requires 20 steps and runs for 2 hours will you understand what "long-horizon" really means.
Capability Layer | Provided by Hy4 | Provided by ADP |
|---|---|---|
Model reasoning | Long-horizon reasoning, visual understanding, CoT optimization | — |
Task orchestration | — | Agentic loop, bidirectional invocation, workflow engine |
Tool connectivity | — | 40+ MCP Connectors, WeCom integration |
Runtime guarantee | — | Trace replay, canary release, auto-fallback, cloud-resident |
Security & permissions | — | RBAC, audit logging, FDE certification standards |
The model is responsible for "thinking," the platform for "running." Hy4's long-horizon task capability lets agents think further and more coherently, while ADP's platform capabilities let agents run more stably and persistently. Together, they form the solution for enterprise-grade 24/7 always-on service-type agents.
Hy4 official's long-horizon task strengthening isn't just another benchmark highlight — it genuinely closes the last mile of "end-to-end autonomous execution of complex tasks."
For enterprises selecting an agent platform, here's the key criterion: can the platform translate Hy4's long-horizon model capability into production capability? Breakpoint recovery, trace replay, canary fallback, cloud residency — these aren't nice-to-haves; they're prerequisites for long-horizon agents in production.
ADP 4.0 is ready on all these dimensions. Hy4 official will be available on ADP from day one. If your enterprise has agents that need to "keep running even when the computer is off," this is your chance to validate.
原创声明:本文系作者授权腾讯云开发者社区发表,未经许可,不得转载。
如有侵权,请联系 cloudcommunity@tencent.com 删除。