Alibaba
Qwen4-Max
最大上下文
1M
最大輸出
262.1K
發布日期
暫無
qwen3.6-35b-a3bQwen3.6 35B A3B 是一个啟用參數较小的 MoE 模型:相关来源描述为 35B 總參數、约 3B 啟用參數,并具备可扩展到接近 1M token 的長上下文能力。官方資料还提到它在程式碼任務上可以与更大的 dense 模型竞争。它的核心价值是部署效率高,同时保留不错的程式碼和長上下文能力。
上下文視窗
262.1K Token
最大輸出
65.5K Token
發布日期
2026年4月17日
模態
| 輸入價格 | 輸出價格 |
|---|---|
| $0.2571/M | $1.5429/M |
推理
工具呼叫
Temperature 參數
附件
知識庫
Endpoint 協議
Qwen3.6-35B-A3B 結合開放權重的稀疏 MoE 架構、原生視覺語言處理與強化的 Agent 程式開發能力。
混合線性注意力與稀疏專家混合架構會在約 350 億參數中啟用約 30 億參數,以提升推論效率。
原生視覺語言架構可接收文字、圖片與影片,並產生以視覺內容為依據的文字結果。
這款後訓練開放權重模型強化前端工作流程與儲存庫層級推理,並可自行部署。
Qwen3.6-35B-A3B 適合自行部署的程式 Agent、儲存庫分析,以及針對圖片或影片的視覺推理工作。
在受控環境中部署開放權重,透過迭代式 Agent 流程產生、修改與除錯程式碼。
追蹤程式碼儲存庫中的跨檔案關係、說明實作結構,並擬定連動修改方案。
分析圖片或影片以定位物件、理解空間關係,並輸出結構化文字說明。
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)| 指數分數 | ||
|---|---|---|
| Artificial Analysis 綜合能力指數 | Artificial Analysis 綜合能力評分 | 33 |
| Artificial Analysis 程式碼能力指數 | Artificial Analysis 軟體任務評分 | 35.2 |
| 知識與推理 | ||
| GPQA | 高階科學問題求解 | 84.1% |
| HLE | 廣泛專家級考試集合 | 20.2% |
| 程式碼與工程 | ||
| SciCode | 科學計算程式碼挑戰 | 35.8% |
| Terminal-Bench Hard | 高難度終端任務執行 | 34.8% |
| 指令遵循與 Agent 任務 | ||
| IFBench | 指令約束遵循 | 64.4% |
| AA-LCR | 長上下文推理 | 63.7% |
| τ²-Bench | Agent 工作流程任務 | 95.3% |
指標來源 Artificial Analysis
Qwen 3.6 35B A3B 的能力、適用情境、限制與 TokenHub 使用指南。
Qwen 3.6 35B A3B 是 Alibaba Qwen 針對開放模型的多模態推理與高效率部署推出的模型。
適合自行託管部署、圖片與影片理解、日常程式開發協助,尤其適合重視部署控制權的情境。
核心優勢是開放的 MoE 變體與較小的啟用參數規模,並具備可在深度思考與直接回應間切換的混合思考。
開放部署需要自行負責基礎設施、推理服務與評估。 更重視重視穩定的正式環境表現時,可考慮 Qwen 3.6 Plus。
使用 TokenHub 的精確識別碼;託管行為可能與自行託管不同。
透過一個 API Key 接入 Qwen3.6 35B-A3B 與更多 AI 模型。
媒體與討論
精選與此模型相關的公開影片和貼文。
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.jpg查看原文Qwen ·
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.jpg查看原文Unsloth 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.jpg查看原文Reddit
Qwen3.6-35b-a3b seems like the best coding model rn
JSVD2 ·
what are your thoughts on this and real life cases and example?
查看原文Qwen 3.6 35b a3b is INSANE even for VRAM-constrained systems
Lucerys1Velaryon ·
展開全文
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 ·
展開全文
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
查看原文Qwen3.6-35B-A3B + OpenClaw - Agentic Coding Locally for Free
Fahd Mirza
查看原文Qwen3.6 Local Test | Can it Beat Gemma 4? | Coding, OCR, Image Understanding with llama.cpp | 🔴 Live
Venelin Valkov
查看原文