QwQ 32B (Ollama) is Qwen's dedicated reasoning model, and the only size on the QwQ page. QwQ thinks at length before answering, which suits the Atlas plan agent: let QwQ produce the plan, then hand execution to a faster coder tag. Context is 40K tokens (40,960), the pull is 20GB, and pricing is Free (self-hosted), so reasoning tokens cost nothing.
Why is QwQ 32B (Ollama) a good fit for the Atlas plan agent?
QwQ 32B (Ollama) thinks at length before answering, which is exactly what the Atlas plan agent is for. Atlas drafts a plan in a read-only plan agent and asks before switching to a build agent, so QwQ can deliberate safely with no write access to the repo.
Long deliberation is only useful when it happens in the right phase. QwQ 32B (Ollama) is Qwen's dedicated reasoning model, so it produces the kind of extended analysis that makes a plan worth reading. Because the Atlas plan agent is read-only, none of that thinking can touch a file until you approve the switch to a build agent. The documented pattern is explicit: use QwQ for the Atlas plan agent, then use `/models` or the model.cycle_recent command to switch to a coder tag for the build phase.
How much does QwQ 32B reasoning cost when self-hosted?
QwQ 32B (Ollama) is Free (self-hosted), and reasoning tokens are free when self-hosted, which removes the usual cost objection to long deliberation. A 20GB pull on a single 24GB card runs extended chain-of-thought that a metered reasoning API would bill for every time.
Reasoning models are expensive on metered APIs precisely because they emit a lot of tokens before they say anything useful. QwQ 32B (Ollama) inverts that economics: a purpose-built local reasoning model at 20GB means extended chain-of-thought runs on a single 24GB card instead of a metered API. The consequence for Atlas is that you can let the plan agent think as long as it wants. Reserve roughly 22GB of VRAM or unified memory, because reasoning traces also lengthen the KV cache, and let it deliberate.
Is the 40K context of QwQ 32B enough for an Atlas plan?
QwQ 32B (Ollama) has 40K tokens (40,960), which is enough to hold a full Atlas plan transcript plus the retrieved code it reasons over. Register qwq:32b under the ollama provider in atlas.json with limit.context 40960 and a generous limit.output of 16384.
The limit.output setting matters more for QwQ 32B (Ollama) than for an instruct model, because QwQ emits reasoning before it emits the plan. A generous limit.output (16384) keeps long reasoning from being truncated mid-thought, which is the most annoying failure mode with a reasoning model. On the input side, 40K tokens (40,960) covers a plan transcript plus retrieved code because Atlas indexes code by AST declarations using tree-sitter, not blind line windows, so what arrives is declarations rather than padding.
How do you hand off from QwQ 32B to a coder model in Atlas?
Use `/models` or the model.cycle_recent command in the Atlas TUI to switch from QwQ 32B (Ollama) to a coder tag after the plan is approved. Atlas lets you switch the active model and provider on the fly with favorites and recents, so the handoff is a keystroke.
The two-model pattern exists because QwQ 32B (Ollama) emits a lot of thinking tokens, so wall-clock latency per turn is high compared with an instruct model of the same size. You want that latency once, during planning, and never during a twenty-step edit loop. Once the plan is settled, model.cycle_recent flips Atlas to a coder tag that computes the unified diff for every file edit and surfaces it for approval before writing. QwQ decides what to do; a faster model does it.
What are the limits of running QwQ 32B locally?
QwQ 32B (Ollama) publishes only one size, 20GB aliased to :latest, so there is no smaller QwQ to fall back to on constrained hardware. QwQ also emits a lot of thinking tokens, so wall-clock latency per turn is high compared with an instruct model of the same size.
Both limits on QwQ 32B (Ollama) are hard. If your machine cannot reserve roughly 22GB of VRAM or unified memory, there is no 7B QwQ waiting for you: the 32B is the whole product line. And if you need fast turns, a reasoning model is the wrong tool regardless of hardware. Keep the codebase index on Ollama embeddings so the reasoning model retrieves against vectors that never left the machine, and use QwQ where the latency buys you something: the plan, not the build.
Setup
- 01Pull it: ollama pull qwq:32b (20GB, aliased to :latest and the only size published).
- 02Reserve roughly 22GB of VRAM or unified memory; reasoning traces also lengthen the KV cache.
- 03Register qwq:32b under the ollama provider in atlas.json with limit.context 40960 and a generous limit.output (16384) so long reasoning is not truncated.
- 04Use QwQ for the Atlas plan agent, which is read-only and asks before switching to a build agent.
- 05Use /models or the model.cycle_recent command to switch to a coder tag for the build phase.
- 06Keep the codebase index on Ollama embeddings so the reasoning model retrieves against vectors that never left the machine.
Frequently asked questions
- what is qwq 32b used for
- QwQ 32B (Ollama) is Qwen's dedicated reasoning model. It thinks at length before answering, which suits the Atlas plan agent: let QwQ produce the plan, then hand execution to a faster coder tag using /models or model.cycle_recent.
- is there a smaller version of qwq than 32b
- No. QwQ 32B (Ollama) is the only size on the QwQ page, published as a 20GB pull aliased to :latest. There is no smaller QwQ to fall back to on constrained hardware.
- how much vram does qwq 32b need
- Reserve roughly 22GB of VRAM or unified memory for QwQ 32B (Ollama). The pull is 20GB, and reasoning traces also lengthen the KV cache, so budget above the raw weight size.
- why is my local reasoning model getting cut off mid-thought
- Because limit.output is too low. Register qwq:32b under the ollama provider in atlas.json with limit.context 40960 and a generous limit.output (16384) so long reasoning from QwQ 32B (Ollama) is not truncated.
- are reasoning tokens expensive with qwq 32b
- No. QwQ 32B (Ollama) is Free (self-hosted), and reasoning tokens are free when self-hosted, which removes the usual cost objection to long deliberation in an Atlas plan agent session.
- is qwq 32b slow for agentic coding
- QwQ 32B (Ollama) emits a lot of thinking tokens, so wall-clock latency per turn is high compared with an instruct model of the same size. Use it for the Atlas plan agent, then switch to a faster coder tag for the build phase.
- how do i switch models between planning and building in atlas
- Use /models or the model.cycle_recent command in the Atlas TUI. Atlas lets you switch the active model and provider on the fly with favorites and recents, so QwQ 32B (Ollama) can plan and a coder tag can execute in the same session.
Try Atlas in your terminal
The terminal-native AI coding agent. Free core, single binary.
Install AtlasRelated guides
Atlas for JavaScript in 2026
In 2026, Atlas empowers JavaScript developers with a terminal-native AI coding agent. It indexes code by AST, uses local embeddings, and offers permission-gated tools for safe, efficient development.
Atlas for Java in 2026
Adopt Atlas, the terminal-native AI coding agent, for Java development in 2026. Enhance your workflow with intelligent code search, refactoring, and robust safety features for Maven and Gradle projects.
Atlas vs Jules: Terminal AI Coding Agents in 2026
Atlas and Jules comparison for 2026. Atlas offers terminal-native TUI and local code indexing. Jules provides cloud VMs and a Critic agent for PR review.
Atlas for Phoenix in 2026
Atlas is a terminal-native AI coding agent for Phoenix in 2026. It reads contexts, LiveView modules, and Ecto changesets, then runs mix test behind a prompt.
Atlas for PyTorch: Terminal-Native AI Coding for nn.Module, Devices, and Autograd in 2026
Atlas is a terminal-native AI coding agent for PyTorch in 2026, where device placement, autograd, and DataLoader worker counts cause most bugs and most slowness.
Atlas for .NET: Your AI Coding Agent in 2026
Atlas empowers .NET developers in 2026 with a terminal-native AI coding agent. Securely integrate Atlas with ASP.NET Core for web APIs and services, leveraging local embeddings and robust safety features for efficient
Atlas for Axum in 2026
Atlas is a terminal-native AI coding agent for Axum in 2026. It decodes tower trait-bound errors, adds IntoResponse types, and runs cargo nextest run.
Atlas vs Bolt.new in 2026: Terminal Agent or In-Browser WebContainer Builder
Atlas is a free, open source terminal-native AI coding agent. Bolt.new runs npm install and your dev server in-browser via WebContainers. Compared for 2026.