Tencent Hy3 is an open 295B-parameter MoE model (21B active per token, 256K context), available as tencent/Hy3 on Hugging Face under Apache 2.0 and served on OpenRouter as tencent/hy3. The key message for Mac users: Hy3 is not a local Mac model — Tencent recommends serving it on eight large GPUs. This article explains what that means in practice and how you can still use Hy3 from your Mac.
What Mac users need to know
Tencent Hy3 is an open 295B-parameter Mixture-of-Experts model for reasoning, coding, agents and long productivity workflows. On OpenRouter, you use it as tencent/hy3; the actual open-weight model is available as tencent/Hy3 on Hugging Face. The most important point for Mac users is simple: Hy3 is open and released under Apache 2.0, but it is not a normal local Mac model. Tencent recommends serving it on 8 GPUs such as H20-3e or comparable large-memory GPUs. On a Mac mini, MacBook or normal Mac Studio, Hy3 is realistically an OpenRouter, cloud API or server workflow — not something you run like a 7B or 14B Ollama model.
What is Tencent Hy3?
Hy3 is a large Mixture-of-Experts model from the Tencent Hy Team. The final release follows Hy3 Preview, which Tencent introduced in late April 2026. According to the model card, Tencent collected feedback from more than 50 products, scaled up the post-training pipeline and fixed several real-world product and agent workflow issues.
The focus is not generic chatbot copy. Hy3 is positioned for tasks where the model has to stay reliable across many steps:
- coding agents and repository work
- tool calling and structured outputs
- document processing
- financial modeling
- office and productivity tasks
- frontend design
- game development
- multi-step agent runs
- long contexts with changing constraints
Tencent presents Hy3 as a reliable and cost-effective model option for real productivity tasks. Hy3 is best understood as an open MoE model aimed at agents and long workflows; that positioning does not establish a blanket comparison with individual closed models.
Key facts for Tencent Hy3
| Property | Tencent Hy3 |
|---|---|
| Official model name | tencent/Hy3 |
| OpenRouter slug | tencent/hy3 |
| Free OpenRouter slug | tencent/hy3:free |
| Developer | Tencent Hy Team |
| Architecture | Mixture of Experts |
| Total parameters | 295B |
| Active parameters | 21B per token |
| MTP layer parameters | 3.8B |
| Experts | 192 experts, top-8 activated |
| Layers | 80, excluding the MTP layer |
| Context window | 256K tokens on the model card; OpenRouter displays 262K |
| Precision | BF16; FP8 variant available |
| License for final Hy3 | Apache License 2.0 |
| Local Mac use | Not realistic for normal Macs |
| Realistic Mac use | OpenRouter, cloud API or your own GPU server |
The “262K” value on OpenRouter and “256K” on the model card are not really a contradiction: 256K commonly means 262,144 tokens. Keep each value attributed to the source that lists it.
Why Hy3 is not simply a local Mac model
Hy3 is open, but huge. This is where AI articles often go wrong: open weights does not automatically mean MacBook-friendly.
The Hugging Face card includes Docker Model Runner and quantization links. But for actual serving, Tencent points to vLLM or SGLang and says Hy3 has 295B parameters in total; to serve it on 8 GPUs, Tencent recommends H20-3e or other GPUs with large memory capacity.
For Mac use, that means:
- Hy3 does not simply run locally with Ollama on a Mac.
- Having 21B active parameters does not make a Mac mini sufficient by itself.
- GGUF or MLX support has to be checked for a specific runtime and quantization.
- A blanket recommendation of 16, 24, 32 or 64 GB unified memory would not be reliable.
For Mac users, the practical framing is:
Hy3 is an open server/cloud-class model. On Mac, it makes sense as an API model through OpenRouter or a hosted GPU setup. For private offline workflows, smaller Qwen, Gemma, Mistral or Llama models remain more realistic.
OpenRouter: how to read tencent/hy3
OpenRouter lists the final version as tencent/hy3. It describes Hy3 as a 295B MoE model with 21B active parameters, 192 experts with top-8 routing and a focus on reasoning, agentic workflows and production use. In the Aug 16, 2026 live check, the OpenRouter model page showed $0.1254 per 1M input tokens and $0.5016 per 1M output tokens for tencent/hy3, with a 5% discount displayed. The public OpenRouter models API lists $0.132 / $0.528 for the same slug before that page discount. There is also tencent/hy3:free as a free slug. OpenRouter pricing, limits and providers can change. Check the current OpenRouter listing before production use.
| OpenRouter slug | Role | Price at the OpenRouter live check on Aug 16, 2026 |
|---|---|---|
tencent/hy3 | standard slug | $0.1254 input / $0.5016 output per 1M tokens (5% discount; API list price $0.132 / $0.528) |
tencent/hy3:free | free slug | free, subject to OpenRouter limits and availability |
tencent/hy3-preview | older preview version | $0.18 input / $0.60 output per 1M tokens |
For new integrations, start with tencent/hy3; tencent/hy3-preview is the older preview release.
API setup on Mac
OpenRouter is OpenAI-compatible. On Mac, many OpenAI-compatible clients can keep using the same SDK while changing only the base URL, API key and model name.
export OPENROUTER_API_KEY="your_openrouter_key"
import os
from openai import OpenAI
client = OpenAI(
base_url="https://openrouter.ai/api/v1",
api_key=os.environ["OPENROUTER_API_KEY"],
)
response = client.chat.completions.create(
model="tencent/hy3",
messages=[
{
"role": "system",
"content": "You are a precise Mac and coding assistant. Keep answers concise, flag uncertainty and do not invent benchmarks."
},
{
"role": "user",
"content": "Explain when I should use a local Mac model and when Tencent Hy3 through OpenRouter makes more sense."
}
],
temperature=0.7,
)
print(response.choices[0].message.content)
Important: this code uses Hy3 through OpenRouter. It does not download the model to your Mac and it does not run inference on Apple Silicon.
Reasoning modes: do not blindly use the deepest mode
Hy3 supports configurable reasoning according to OpenRouter and the model card. The model card shows reasoning_effort through chat_template_kwargs for local OpenAI-compatible servers:
no_think: direct answer, default in the example configurationlow: lighter reasoning modehigh: deeper reasoning for math, coding and complex multi-step tasks
Do not publish full chain-of-thought traces. What matters is the outcome: better planning, more stable tool use and less task drift. Reasoning modes are latency, cost and quality controls, not magic quality switches.
What improved over Hy3 Preview?
The final Hy3 release is not just a renamed preview. Tencent names several improvements from product feedback and post-training:
| Area | Improvement according to Tencent |
|---|---|
| Tool calling | More stable tool calls, better error recovery and more reliable structured outputs |
| Agent scaffolds | Better generalization across setups such as CodeBuddy, Cline and KiloCode |
| Hallucinations | Internal hallucination rate reduced from 12.5% to 5.4% |
| Commonsense errors | Internal error rate reduced from 25.4% to 12.7% |
| Long context | Better coreference resolution, ellipsis recovery and multi-turn constraint tracking |
| Product feedback | Feedback from more than 50 Tencent products used in the final update |
These are vendor claims, not independent measurements. They are useful signals, but they do not replace your own tests on real workflows.
Benchmarks: strong, but read them carefully
The Hugging Face page shows several evaluation results for Hy3, including:
| Benchmark | Hy3 score on Hugging Face | Interpretation |
|---|---|---|
| SWE-bench Verified | 78 | coding agents / real GitHub issues |
| SWE-bench Pro | 57.9 | harder coding benchmark |
| DeepSWE | 28 | coding and agent-adjacent evaluation |
| GPQA Diamond | 90.4 | hard scientific reasoning |
These numbers are useful context, but they do not establish a general model ranking. Benchmarks depend heavily on the harness, scaffold, tool access, prompting, reasoning mode, timeout and scoring logic. That is especially true for SWE-bench-style evaluations. They prove neither that Hy3 beats Claude nor that it is the best coding model or better than every local Mac model.
For real Mac workflows, the deciding question is whether Hy3 is reliable, affordable and acceptable from a data-handling perspective in your own tooling.
When Hy3 makes sense for Mac users
Hy3 can be useful if you work on a Mac but consciously accept cloud or server inference.
Good use cases:
- reviewing a large repository
- planning a multi-file refactor
- structuring an agent run with tools
- analyzing data or spreadsheet logic
- summarizing technical documentation
- keeping long chat or project context stable
- designing frontend components
- testing browser or research agents
Poor use cases:
- private documents without cloud processing
- offline work on a train or at university
- small everyday questions where a local 4B to 14B model is enough
- sensitive customer code without clear data approval
- tasks where latency matters more than model strength
Hy3 vs local Mac models
| Task | Hy3 through OpenRouter | Local Mac model |
|---|---|---|
| Private notes | Only after data review | Usually better |
| Large repository | Strong if cloud is allowed | Limited by RAM and context |
| Offline work | No | Yes |
| Tool-based agents | Good fit | Depends on model and runtime |
| Cost control | Token-dependent | Hardware and power, no API bill |
| Privacy | Cloud/provider decision | More controllable |
| Mac hardware use | Mac is the client | Apple Silicon runs inference locally |
The best workflow is hybrid: local models for private, fast and offline tasks; Hy3 for large agentic tasks where cloud processing is acceptable.
Hy3 vs Hy3 Preview
Hy3 Preview was the April 2026 preview. OpenRouter still lists it separately as tencent/hy3-preview. For new integrations, use the final tencent/hy3 release.
| Property | Hy3 Preview | Hy3 |
|---|---|---|
| Release | April 22, 2026 | July 6, 2026 |
| Parameters | 295B total / 21B active | 295B total / 21B active |
| Context | 256K | 256K |
| License | Tencent Hy Community License Agreement | Apache License 2.0 |
| Positioning | preview, feedback collection | final open release with improved product and agent behavior |
The license difference matters: do not infer the final Hy3 license from old preview information. The final Hy3 model card lists Apache 2.0.
Privacy and compliance
Hy3 through OpenRouter is not a local privacy mode. Prompts, code, documents and tool outputs leave your Mac and run through OpenRouter and the active provider. For private experiments this may be fine; for personal data, customer code or unpublished research, you need clear rules.
Practical recommendation:
- Test private texts with Ollama, LM Studio or MLX first.
- Use Hy3 only for data that may be processed in the cloud.
- Check API logs, retention and provider routing before production use.
- Do not use free router slugs for sensitive projects without clear terms.
- For repeated long contexts, check costs and prompt caching behavior.
Practical takeaway
Tencent Hy3 is an open MoE model with 295B parameters, 21B active, 256K context, Apache 2.0 licensing and OpenRouter access through tencent/hy3. Its positioning is focused on agent workflows.
For Mac users, the crucial message is still: Hy3 is not suddenly a local Mac model. It is an open but server-sized model. On Mac, it makes sense as a cloud/API complement to local models. If you want privacy, offline work and Apple-Silicon inference, use smaller local models. If you need long agent runs, broader context understanding and strong tool workflows, test Hy3 through OpenRouter or dedicated GPU infrastructure.
Sources
- Tencent Hy3 on Hugging Face: https://huggingface.co/tencent/Hy3
- Tencent Hy3 on OpenRouter: https://openrouter.ai/tencent/hy3
- Tencent Hy3 Preview on OpenRouter: https://openrouter.ai/tencent/hy3-preview
- Tencent Hy3 Free on OpenRouter: https://openrouter.ai/tencent/hy3:free
- OpenRouter Models API: https://openrouter.ai/api/v1/models
- Tencent Hy3 Preview on Hugging Face: https://huggingface.co/tencent/Hy3-preview
- Tencent News on Hy3 Preview: https://www.tencent.com/en-us/articles/2202320.html
Frequently Asked Questions
What is Tencent Hy3?
Tencent Hy3 is a 295B-parameter Mixture-of-Experts model from the Tencent Hy Team. It activates 21B parameters per token, uses 192 experts with top-8 routing and has a 256K token context window.
What is the OpenRouter model ID?
The standard OpenRouter slug is tencent/hy3. There is also a free router slug, tencent/hy3:free. Check live pricing and provider availability on OpenRouter before production use.
Can Tencent Hy3 run locally on Mac?
Not realistically on normal Macs. The weights are open, but Tencent recommends serving Hy3 on 8 GPUs such as H20-3e or other large-memory GPUs. A Mac mini or MacBook is not a realistic target for this model.
Is Hy3 open source?
The final Hy3 release is listed under the Apache License 2.0 on the Hugging Face model card. The safer wording is: Hy3 is an open-weight model under Apache 2.0; practical local use still requires server-class hardware.
What changed from Hy3 Preview to Hy3?
Hy3 Preview was the April 2026 preview. The final Hy3 release builds on it with feedback from more than 50 Tencent products, improved post-training, more reliable tool calling, better anti-hallucination behavior and stronger agent workflows.
When should Mac users use Hy3?
Hy3 is most useful for coding agents, long tool workflows, document processing, financial analysis, frontend prototyping, game development and tasks where a model must remain stable across many steps. For private offline files, smaller local Mac models are usually the better fit.