Alibaba
Qwen4-Max
最大コンテキスト
1M
最大出力
262.1K
リリース日
N/A
qwen3.6-35b-a3bQwen3.6 35B A3B は、参照元で強調されている特徴として 35B 総 / about 3B 有効 MoE, long コンテキスト extendable toward 1M tokens を持ちます。主な価値は 効率的な導入, コーディング ベンチマーク and 長文脈 推論 にあります。そのため、汎用チャットモデルとしてではなく、このモデル固有の強みを中心に説明するのが自然です。
Context Window
262.1K tokens
Maximum Output
65.5K tokens
Release Date
2026年4月17日
Modalities
| 入力価格 | 出力価格 |
|---|---|
| $0.2571/M | $1.5429/M |
Reasoning
Tool calling
Temperature parameter
Attachments
Knowledge Base
Endpoint Protocols
Qwen3.6-35B-A3Bは、オープンウェイトの疎なMoEアーキテクチャ、ネイティブな視覚言語処理、強化されたエージェント型コーディングを備えます。
線形アテンションと疎な専門家混合を組み合わせ、約350億パラメータのうち約30億を有効化して推論効率を高めます。
ネイティブな視覚言語設計により、テキスト、画像、動画を入力し、視覚内容に基づくテキストを生成します。
ポストトレーニング済みのオープンウェイトモデルとして、独自に展開でき、フロントエンド作業とリポジトリ規模の推論を強化します。
Qwen3.6-35B-A3Bは、独自環境に展開するコーディングエージェント、リポジトリ分析、画像や動画を対象とした視覚推論に適しています。
管理下の環境にオープンウェイトを展開し、反復的なエージェント処理でコードの生成、修正、デバッグを行います。
リポジトリ内のファイル間関係を追跡し、実装構造を説明して連携した変更計画を作成します。
画像や動画から物体を特定し、空間的な関係を解釈して構造化されたテキスト説明を返します。
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 Intelligence Index | 総合能力の集約評価 | 33 |
| Artificial Analysis Coding Index | コーディング能力の集約評価 | 35.2 |
| 知識と推論 | ||
| GPQA | 高度な科学問題の解決 | 84.1% |
| HLE | 幅広い分野の専門家レベル試験 | 20.2% |
| コーディングとソフトウェア開発 | ||
| SciCode | 科学計算のコーディング課題 | 35.8% |
| Terminal-Bench Hard | 高難度のターミナル操作 | 34.8% |
| 指示追従とエージェントタスク | ||
| IFBench | プロンプト制約への準拠 | 64.4% |
| AA-LCR | 長いコンテキストでの推論 | 63.7% |
| τ²-Bench | エージェントのワークフロータスク | 95.3% |
指標の出典 Artificial Analysis
Qwen 3.6 35B A3B の能力、用途、制約、TokenHub利用ガイド。
Qwen 3.6 35B A3B は Alibaba Qwen のオープンモデルのマルチモーダル推論と効率的な導入向けモデルです。
セルフホスト運用、画像・動画理解、日常的なコーディング支援に向き、特に導入時の制御性重視の場面に適します。
主な強みはアクティブパラメータを抑えたオープンMoE、および熟考と直接応答を切り替えられるハイブリッド思考です。
オープン運用ではインフラ、配信、評価を自前で担う必要があります。 本番での安定性が重要重視なら Qwen 3.6 Plus を検討してください。
TokenHubの正確なIDを使い、ホスト版と自前運用の差を確認してください。
1つの API キーで 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
原文を見る