Command A vs Qwen3.6-35B-A3B

“The primitive here is a sparse MoE inference target that fits a two-GPU footprint — that's the whole value proposition stripped of marketing, and it's actually real. The DX bet Cohere made is that the right place to put complexity is in the model architecture, not in the operator's infrastructure YAML, and for any team that's ever lost a procurement fight over H100 allocation, that's the correct bet. The CC-BY-NC open weights with HuggingFace hosting means your first-10-minutes story is `transformers` + a weights download, not a sales call — that's enough to earn a ship on craft alone.”

“If you're running a self-hosted coding agent and paying $X/month in API bills, this is your exit ramp. 3B active params means a single 4090 can serve it comfortably, and the 262K context actually handles real codebases. Ship it as your backend and tune from there.”

“Direct competitors are Mistral Large 2 and Llama 3.1 405B quantized — Command A beats both on the hardware efficiency story, but the benchmark claims (outperforming GPT-4o on STEM and business tasks) come from Cohere's own evals, which is the exact category of evidence I discount until third-party replication exists. The scenario where this breaks is any enterprise that needs commercial on-prem weights, since CC-BY-NC shuts out paying customers who want to fine-tune and ship a product — those buyers will go to Mistral or wait for a commercial license tier. What kills this in 12 months isn't a competitor: it's that GPU hardware keeps getting cheaper and the two-GPU pitch loses its premium differentiation faster than Cohere can build the enterprise sales motion to monetize it.”

“We've seen 'beats models 10× its size' claims before — benchmark cherry-picking is rampant. The thinking preservation feature sounds promising, but agentic loop reliability is something you discover in production, not on leaderboards. Run your own evals before committing an entire stack to this.”

“The buyer is an enterprise IT or ML infrastructure team with a specific GPU budget constraint — that's a real, named buyer with a real budget line, and the two-GPU deployment story is a wedge into procurement conversations that most LLM vendors can't have. The moat isn't the model itself (MoE architectures are not proprietary), it's Cohere's enterprise sales motion, SLA stack, and the data residency story that comes with on-prem deployment — workflow lock-in through compliance requirements is underrated as a retention mechanism. The risk is the CC-BY-NC license creating a two-tier market where open-source adopters can't convert to paying customers without re-licensing friction, which caps the bottom-up growth flywheel that made models like Llama so sticky.”

“The thesis Command A is betting on: within three years, enterprise AI adoption will be gated not by model capability but by the organizational ability to deploy models inside a compliance perimeter, and the winner in that market is whoever makes sovereign deployment cheap enough to justify. That's a falsifiable claim and the trend line — edge inference economics improving 2–3x per year while regulatory pressure on data residency intensifies in the EU and APAC — makes it a well-timed bet, not early and not late. The second-order effect nobody's talking about: if two-GPU on-prem becomes the default deployment pattern, the hyperscalers lose the 'just use our API' argument with regulated industries, which shifts significant AI infrastructure spend from cloud consumption to on-premises hardware — and Cohere, not AWS or Azure, owns that positioning.”

“MoE is increasingly the dominant paradigm for the efficiency frontier, and this is one of the clearest demonstrations of why. 3B active params at 35B effective capacity is not a trick — it's an architecture win. The line between 'local model' and 'frontier model' is erasing faster than anyone predicted.”

“1M token context on a local model is a game-changer for creative workflows — entire novel manuscripts, full design system docs, long-form scripts fit in a single window. The zero API cost means no throttling during high-creativity sprints. This earns a spot in the local toolkit.”