Alibaba
Qwen4-Max
Contexte total
1M
Sortie max.
262.1K
Date de sortie
N/A
qwen3.6-35b-a3bQwen3.6 35B A3B reprend les éléments mis en avant par les sources : 35B total / about 3B actifs MoE, long contexte extendable toward 1M tokens. Sa valeur principale se situe dans déploiement efficace, programmation benchmarks and long contextee raisonnement. La description doit donc insister sur ces caractéristiques propres au modèle, plutôt que le présenter comme un chatbot générique.
Context Window
262.1K tokens
Maximum Output
65.5K tokens
Release Date
17 avr. 2026
Modalities
| Prix entrée | Prix sortie |
|---|---|
| $0.2571/M | $1.5429/M |
Reasoning
Tool calling
Temperature parameter
Attachments
Knowledge Base
Endpoint Protocols
Qwen3.6-35B-A3B associe une architecture MoE clairsemée à poids ouverts, un traitement vision-langage natif et un codage agentique amélioré.
Son architecture hybride mêle attention linéaire et experts clairsemés, en activant environ 3 milliards de paramètres sur 35 milliards afin d’améliorer l’efficacité d’inférence.
Sa conception vision-langage native accepte le texte, les images et la vidéo, puis produit du texte fondé sur leur contenu visuel.
Ce modèle post-entraîné à poids ouverts améliore les processus frontend et le raisonnement à l’échelle d’un dépôt, tout en permettant un déploiement autonome.
Qwen3.6-35B-A3B convient aux agents de programmation déployés de façon autonome, à l’analyse de dépôts et au raisonnement visuel sur des images ou des vidéos.
Déployer les poids ouverts dans un environnement maîtrisé afin de générer, réviser et déboguer du code au moyen de processus agentiques itératifs.
Retracer les relations entre les fichiers d’un dépôt, expliquer la structure de l’implémentation et préparer un plan de modifications coordonnées.
Analyser des images ou des vidéos pour localiser les objets, interpréter leurs relations spatiales et produire un compte rendu textuel structuré.
import OpenAI from "openai"
const client = new OpenAI({
apiKey: process.env.TOKENHUB_API_KEY,
baseURL: "https://us-api.tokenhub.com/v1",
})
const result = await client.chat.completions.create({})
console.log(result.choices[0]?.message?.content)| Score d’indice | ||
|---|---|---|
| Artificial Analysis Intelligence Index | Synthèse générale des capacités par Artificial Analysis | 33 |
| Artificial Analysis Coding Index | Synthèse des tâches logicielles par Artificial Analysis | 35.2 |
| Connaissances et raisonnement | ||
| GPQA | Résolution avancée de problèmes scientifiques | 84.1% |
| HLE | Large ensemble d’examens de niveau expert | 20.2% |
| Programmation et ingénierie | ||
| SciCode | Défis de programmation scientifique | 35.8% |
| Terminal-Bench Hard | Exécution de tâches complexes dans un terminal | 34.8% |
| Respect des instructions et tâches d’agent | ||
| IFBench | Respect des contraintes du prompt | 64.4% |
| AA-LCR | Raisonnement en contexte long | 63.7% |
| τ²-Bench | Tâches de workflow agentique | 95.3% |
Mesures provenant de Artificial Analysis
Capacités, usages, limites et guide TokenHub pour Qwen 3.6 35B A3B.
Qwen 3.6 35B A3B est un modèle proposé par Alibaba Qwen pour le raisonnement multimodal ouvert et les déploiements efficaces.
Idéal pour le déploiement auto-hébergé, la compréhension d’images et de vidéos et l’assistance courante au code, surtout si l’objectif est le contrôle du déploiement.
Atout clé : une variante MoE ouverte avec peu de paramètres actifs ainsi que une pensée hybride alternant entre réflexion et réponse directe.
Un déploiement ouvert exige de gérer l’infrastructure, le service et l’évaluation. Pour la stabilité en production est prioritaire, envisagez Qwen 3.6 Plus.
Utilisez l’ID exact de TokenHub; le service hébergé peut différer de l’auto-hébergement.
Accédez à Qwen3.6 35B-A3B et à d’autres modèles d’IA avec une seule clé API TokenHub.
Medias Et Discussions
Selection de videos et publications publiques liees a ce modele.
X (Twitter)
Qwen ·
⚡ Meet Qwen3.6-35B-A3B:Now Open-Source!🚀🚀 A sparse MoE model, 35B total params, 3B active. Apache 2.0 license. 🔥 Agentic coding on par with models 10x its active size 📷 Strong multimodal perception and reasoning ability 🧠 Multimodal thinking + non-thinking modes https://t.co/UMiChPaLid
https://pbs.twimg.com/media/HGB1pOdbIAA_kyz.jpgVoir la sourceQwen ·
LM Performance:Qwen3.6-35B-A3B outperforms the dense 27B-param Qwen3.5-27B on several key coding benchmarks and dramatically surpasses its direct predecessor Qwen3.5-35B-A3B, especially on agentic coding and reasoning tasks. https://t.co/PyXDNruoy2
https://pbs.twimg.com/media/HGB1yASbcAEzWkd.jpgVoir la sourceUnsloth AI ·
2-bit Qwen3.6-35B-A3B did a complete repo bug hunt with evidence, repro, fixes, tests and a PR writeup. 🔥 Run it locally in Unsloth Studio with just 13GB RAM. 2-bit Qwen3.6 GGUF made 30+ tool calls, searched 20 sites and executed Python code. GitHub: https://github.com/unslothai/unsloth https://t.co/1YwMxrWOYr
https://pbs.twimg.com/amplify_video_thumb/2044849663774425088/img/fNsqbHmhlS3uC_47.jpgVoir la sourceReddit
Qwen3.6-35b-a3b seems like the best coding model rn
JSVD2 ·
what are your thoughts on this and real life cases and example?
Voir la sourceQwen 3.6 35b a3b is INSANE even for VRAM-constrained systems
Lucerys1Velaryon ·
Lire la publication complète
Apologies for the 1345th post glazing QWEN but it has literally been a game-changer for me. I’m relatively new to running local LLMs, but the appeal of having a private AI assistant for coding and experimentation is significant. As a software engineer, I’ve also embraced the recent “vibe-coding” trend, mostly using AI to build hobby Android apps in my spare time. Over the past month, I created a web scraper app designed to extract images from ad-heavy websites that are otherwise frustrating to navigate. The project was entirely AI-generated. I didn’t write the code myself, though I did design the architecture and suggest optimizations, which AI still struggles with. I’ll admit I haven’t reviewed most of the code; it’s messy, but since it’s purely a personal hobby project, that’s acceptable. Until recently, I relied on services like Antigravity and Codex, which worked well enough on free plans. However, tighter usage quotas pushed me toward local models. My hardware is modest by local LLM standards: an AMD 7700 XT, 32GB DDR4 RAM, and a Ryzen 5 5600. I experimented with Gemma 3, Gemma 4, and Qwen 2.5 Coder (mostly Q3/Q4 quantizations under 20GB due to VRAM constraints), using LM Studio as the backend with various frontends like GitHub Copilot, RooCode, Cline, Android Studio AI Chat, and OpenCode. Unfortunately, none of these models fit my workflow well. They struggled with even minor bug fixes, frequently exhausted context windows, got stuck in reasoning loops, or failed tool calls repeatedly. Then I tried Qwen 3.6 35B-A3B. Initially, I expected little, but I installed the i1-q4_k_s quant, offloaded all 40 layers to GPU, configured 128k context, enabled flash attention, and used Q8_0 KV quantization. For testing, I gave it a practical task: fix the scraper logic for a problematic website. Gemini Flash (in Antigravity) and MinMax (the free version in Opencode) had both failed to solve this issue despite multiple attempts. Using LM Studio as an OpenAI-compatible endpoint with GitHub Copilot in VS Code, I let it run. It took about 25 minutes, but it succeeded in one shot. With a single initial prompt, it analyzed the site’s HTML structure, compared it against my Kotlin scraper code, and resolved three critical bugs without a single failed tool call. That result was impressive enough that I gave it a second challenge: update the project README with real app screenshots by driving an Android emulator, selecting screenshots based on specific criteria. Using RooCode this time, the process took around 45 minutes. I had to teach it some emulator workflow conventions, such as taking screenshots after every action and analyzing them to track app state, but once instructed, it executed flawlessly. For the first time, I feel like I have a local model capable of reliably handling most of my coding tasks, while reserving cloud-based premium models for more demanding work. Qwen has genuinely made local AI coding practical for me.
Qwen3.6 35B-A3B on a Laptop: My Zero to One Moment
rolznz ·
Lire la publication complète
Hi everyone, I'm new here - because I only have a laptop and I only just realized local models are actually good enough now. So I'd like to share my experience, in case it helps others, and also to learn from the more experienced people here. This is the first model that works for me on my ASUS Zenbook Pro 14 (RTX 4060 8GB VRAM, 64GB RAM): fast enough: ~27TPS generation speed at 32k context, or ~18TPS at 256k context smart enough: it can read and write files, use skills, execute CLI commands, use git, follow instructions, and act as a useful thinking partner. Why it's important to me For me this is important because it's where I unconsciously decided to draw the line - that I didn't want to share private information or more personal thoughts with cloud models (even TEE ones). I know I can still get hacked and my data leaked, but for me that's different than giving it up from the first prompt. So for the first time, I now have this fully local, second brain. For me, it's a game changer. I still use cloud models for public stuff I'm still using cloud models for public projects, but for brainstorming and simple personal projects, local is now good enough for me. I'm also now looking into a more powerful desktop machine where maybe I can do some more serious coding. I have had a taste and I want more 😄 Now whenever I see Claude's black box "✽ Envisioning… (41s · ↓ 2.9k tokens · thinking some more with high effort)" it's so frustrating. I have no idea if it's going in the right direction. (whether this is an "efficient" way to do things is another story) My issues so far with Qwen3.6 Qwen3.6 35B A3B is not perfect, here are some minor issues I observed, which I can work around: It makes some mistakes, but normally recovers on its own. Very occasionally it does get stuck in a loop. It does need some human monitoring, which is fine for me. It sometimes doesn't read a skill in full or make the best decision even when it can fit it in context. It seems to sometimes be "lazy". It is very non-deterministic. I didn't do any tweaks here though (because normally it ends up with the result I need). I guess some of these could be improved if I used a larger quantization. My setup For inference I use llama.cpp, with unsloth's Qwen3.6-35B-A3B-UD-IQ3_XXS.gguf. For my harness, I use Pi with pi-llama-cpp extension. The harness runs in multipass and connects to the host running llama.cpp. I've also connected it to my phone through an E2EE Matrix chat (a custom one I built off of pi-messenger-bridge) - although it means I have to keep my laptop on all the time, which is annoying. Another reason for buying another machine which I'm more comfortable to run 24/7. llama.cpp flags for 256k context(18tps): ./build/bin/llama-server -m Qwen3.6-35B-A3B-UD-IQ3_XXS.gguf -ngl 24 -np 1 -fa on -ctk q4_0 -ctv q4_0 -c 262144 --host 0.0.0.0 --port 8088 -ncmoe 32 --no-mmap --jinja llama.cpp flags for the 32k context (27tps): ./build/bin/llama-server -m Qwen3.6-35B-A3B-UD-IQ3_XXS.gguf -ngl 99 -np 1 -fa on -ctk q4_0 -ctv q4_0 -c 32000 --host 0.0.0.0 --port 8088 -ncmoe 32 --no-mmap --jinja What was your Zero to One moment?
YouTube
Qwen3.6 35B-A3B Full Test – Is THIS the Best LOCAL Model Yet?
Bijan Bowen
Voir la sourceQwen3.6-35B-A3B + OpenClaw - Agentic Coding Locally for Free
Fahd Mirza
Voir la sourceQwen3.6 Local Test | Can it Beat Gemma 4? | Coding, OCR, Image Understanding with llama.cpp | 🔴 Live
Venelin Valkov
Voir la source