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를 사용하고 호스팅과 자체 배포의 차이를 확인하세요.
하나의 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
원문 보기