Загрузка видео...

Не удалось загрузить видео

На главную

What can a 770B model actually build? Hy4 preview is making that question more practical. 770B total / 49B active Native 1M context Apache 2.0 Day-0 vLLM + SGLang Official FP8 ~1.5TB → ~214GiB with mixed per-layer quant The interesting part: reported accuracy barely moves vs BF16. Here’s Hy4...

12,224 просмотров • 16 дней назад •via X (Twitter)

Комментарии: 0

Нет доступных комментариев

Здесь появятся комментарии из оригинального поста

Похожие видео

I’ve been testing Hy4 preview in WorkBuddy, and the most interesting part is not simply the model size, it’s how much practical work it can handle with a relatively focused active parameter count. Hy4 preview brings together stronger code understanding, generation, and editing; improved document and information processing; workflow automation; web and game development; cross-tool collaboration; and more reliable completion of complex, multi-step tasks. In other words, it is designed for work that requires planning, tool use, iteration, and follow-through, not just a quick answer in a chat window. Compared with its initial release, the current Hy4 preview is noticeably faster and better-performing in practical workflows. Following an upgrade released yesterday, it can complete tasks with fewer conversation rounds and lower token usage, while reasoning more quickly and making the overall user experience feel smoother from the first instruction to the final result. For my test, I gave it a demanding Three.js game-prototyping task with a 770B-parameter model and 49B active parameters. The result was more revealing than a simple first-look demo: Hy4 preview handled the core logic, edge cases, and follow-up changes while maintaining the broader context of the project. That combination of capability, speed, context, and active compute is what makes its cost-effectiveness worth examining. A fair evaluation should use the same prompt and environment configuration across models, changing only the model itself. That makes it easier to assess task completion, planning quality, tool-calling stability, reasoning speed, token efficiency, and performance over longer workflows without confusing the result with different settings. If you want to test the model yourself, access Hy4 preview through WorkBuddy and see how it performs on a real coding, document, automation, or creative task: Tencent Hy Tencent AI WorkBuddy

Tyler Wayne

56,152 просмотров • 11 дней назад

I tested Tencent’s Hy4 preview model in WorkBuddy on a real frontend build, not a benchmark screenshot. I gave it one practical brief: create an original neon courier game in a single HTML file, with Canvas rendering, keyboard controls, collision detection, scoring, a countdown timer, a boost mechanic, sound effects, and reliable restart logic. The point was not to see whether it could describe a game. I wanted to see whether it could turn a creative idea into a coherent, playable result while handling the details that often break a quick prototype: state changes, movement, collisions, feedback, layout, and interaction flow. Tencent’s Hy4 preview is designed for stronger code understanding, generation, and editing, together with document and information processing, workflow automation, web and game development, cross-tool collaboration, and complex multi-step task completion. That makes it relevant not only for answering questions, but also for taking a task from brief to working output. The current preview version is faster and more effective than the first release. After the latest upgrade, the workflow takes fewer conversation rounds, uses fewer tokens, and reaches useful results more quickly. The difference is most noticeable in the handoff between idea, implementation, revision, and final testing: there is less waiting and less back-and-forth before the result becomes usable. For context, the reference materials describe Tencent’s Hy4 preview as a 770B-parameter model with 49B active parameters, a 1M-token context window, and Apache 2.0 weights. The practical question is how those capabilities translate into real work. In this case, I’m testing whether the model can produce a finished, playable game rather than just a promising code fragment. The one-minute video shows the complete process: selecting Tencent’s Hy4 preview model in WorkBuddy, submitting the build prompt, reviewing the generated result, playing the game, and checking the controls, collisions, score, timer, boost effect, sound, and restart flow. Try your own coding, frontend, document, or automation task in WorkBuddy: Tencent Hy Workbuddy Tencent AI

Rebecca Adson

61,820 просмотров • 4 дней назад

🚨 I just built a game with an open-source AI model. And honestly… I didn’t expect it to be this capable. Tencent Hunyuan just released Hy4 preview, and it’s already pushing into the top tier of open-source models. Three major releases in six months. That pace is crazy. Here’s what Hy4 preview brings: → 770B total parameters → 49B active parameters → 1M+ token context window → Fully open-source But the numbers aren’t even the most interesting part. Hy4 preview was built around one goal: real-world productivity. Coding. Engineering. Office work. Science. Gaming. Finance. Security. And Tencent didn’t build it in isolation. Hy4 preview was co-designed alongside real products like WorkBuddy, using expertise and real-world data from across Tencent’s ecosystem. So I decided to test it the way I actually like testing AI models: I gave it a game idea and let WorkBuddy help turn it into a playable experience. 🎮 From the initial concept to the actual game logic, it was surprisingly smooth. And the benchmark results back up the hype: 163 internal experts 203 engineering tasks Hy4 preview — 2.99/4 Kimi K3 — 2.94/4 GLM 5.3 — 2.92/4 It also beats GLM 5.2 on benchmarks and comes remarkably close to GLM 5.3. Then comes the part I really like: 💰 ¥6/M input tokens 💰 ¥18/M output tokens 💰 ¥0.30/M cache hits Flagship-level capability without the flagship-level price. And right now, you can try Hy4 preview FREE through WorkBuddy for the next two weeks. If you’re curious what it can actually do, don’t just read the benchmarks. Build something with it. 🔗 Tencent Hy Tencent AI

Aryan Rakib

63,296 просмотров • 11 дней назад

I wanted to see what Hy4 preview could actually do when I gave it a real creative project instead of another “write me some code” prompt. So I went with something I’d genuinely want to play: 🐬 a cute dolphin as the hero 🌊 colorful underwater worlds 💎 glowing pearls to collect 🐠 sea creatures and obstacles 🪸 coral reefs, bubbles & hidden treasure 🎮 smoother animations and progressively harder levels The result is this underwater platformer 👇 And this is where Hy4 preview gets interesting to me. Behind the scenes, we’re talking about 770B parameters, 49B active parameters and a 1M+ token context window. It’s also fully open-sourced. But big numbers only matter if they translate into something useful. What I’m really testing is how much actual work the model can take off my plate understanding the idea, handling the implementation, keeping all the moving parts connected, and getting from a blank canvas to something that feels like a real experience. And there’s another update that makes this even more interesting: Hy4 preview was upgraded yesterday to significantly reduce both conversation turns and token consumption. That means less back-and-forth, faster thinking, and a smoother overall experience when working through complex tasks. That’s also why the cost-effectiveness angle stands out to me. If a model can handle more of the workflow while using fewer tokens and requiring fewer iterations, the value isn’t just in the benchmark score. It’s in how much more you can actually build with it. This dolphin has me wanting to test Hy4 preview with some much crazier ideas next. 🐬👀 Tencent Hy Tencent AI ☞

Md Riyazuddin

63,562 просмотров • 12 дней назад

I wanted to see where Hy4 preview would stop, so I gave it a deliberately demanding prompt: “Build a working Cyber Incident Command Center.” Not a mockup. A real, responsive app with a live threat map, animated attack routes, incident simulation, filters, investigation panels, event logs, ownership controls, and working isolate/resolve actions. Hy4 preview planned the build, wrote the application, ran it locally, tested the interactions, checked the mobile layout, fixed issues, and opened the finished product for review. Then I clicked “Simulate.” A new incident appeared, the dashboard updated, I filtered it by severity, opened the evidence trail, isolated the affected system, and resolved it. The KPI counters changed with the action. That’s a much more useful coding demo to me than watching code appear in an editor. Hy4 preview is Hunyuan’s third major release in six months. It’s fully open-sourced, with 770B total parameters, 49B activated, and a 1M+ token context window. Tencent built it around productivity scenarios through close work with experts in software engineering, gaming, finance, and security, plus direct co-design with tools like WorkBuddy. In an internal blind test covering 203 engineering tasks and 163 Tencent experts, it scored 2.99/4—slightly ahead of Kimi K3 at 2.94 and GLM 5.3 at 2.92. And the pricing stays practical: $0.834/M input $2.501/M output $0.042/M cache hits If you want to test it yourself, Hy4 preview is free inside WorkBuddy for the next two weeks, for a limited time. Tencent Hy Tencent AI WorkBuddy

Clara Bennett

12,864 просмотров • 22 дней назад

Qwen3.8-27B running at full BF16 on a free Kaggle TPU is kind of ridiculous. No quantization. No tiny context window. No expensive GPU instance. Just Qwen3.8-27B running on a Kaggle TPU v5e-8. The reported numbers: ~130 tok/s decode ~10,000 tok/s prefill 262K context That prefill number is especially wild. You can throw a huge amount of code or context at the model and ingest it extremely quickly, while still getting around 130 tokens per second during generation. And because it’s running in full BF16, you’re not relying on an aggressive quant just to make the model fit. But the really interesting part isn’t even the raw throughput. You can expose it as an OpenAI-compatible endpoint. That means you can plug the model into tools that already understand OpenAI-style APIs. Claude Code. Codex. OpenCode. And other compatible clients. So the workflow becomes pretty simple: Spin up the Qwen3.8-27B endpoint on Kaggle. Point your coding tool at the API. And suddenly you have a 27B coding model sitting behind the same interface you’d normally use for hosted models. The 262K context is also a huge deal for agentic coding. Large repositories can fit into a single context. Long conversations don’t need to be constantly trimmed. And tools can feed much more information back to the model without hitting a tiny context ceiling. The fact that this can be built around a free TPU environment is what makes this especially interesting. We’re getting to a point where experimenting with serious open models doesn’t always require owning a $2,000 GPU or paying for a large cloud instance. Free compute + open weights + an OpenAI-compatible API + existing coding agents. That’s a pretty powerful combination. Qwen3.8-27B is already an interesting model. Running the full BF16 version at ~130 tok/s with 262K context on free Kaggle TPU compute makes it a lot more interesting.

FHILY👑

35,794 просмотров • 15 дней назад