Coding agents · 32 GB · 256K context

Best local coding model for a 32 GB AMD GPU

Qwen3.6-35B-A3B at Q5 (Unsloth UD-Q5_K_XL) on one Radeon AI PRO R9700 (32 GB). It holds the model’s full 262,144-token context on the card with f16 KV and nothing offloaded.

As an Amazon Associate I earn from qualifying purchases. Some Newegg links use Rakuten Advertising and some B&H links use B&H’s affiliate program when those IDs are configured. Micro Center and AMD Store links are plain “also available at” links — no tracking. Buttons say “Check price” and never invent or live-quote a price. Full disclosure.

The short answer

We measured about 100 tok/s on short prompts, about 88 tok/s at 32K and about 50 tok/s at 256K (llama.cpp, Vulkan, one card) on the local desktop. Qwen’s card says to keep at least 128K context. Coding agents send large system prompts and whole files. A setup that only fits 8K–32K will fit the model but not the job.

Why this model for coding agents

Published by Qwen on the model card (their own agent scaffold, not our measurement): SWE-bench Verified 73.4, SWE-bench Pro 49.5, Terminal-Bench 2.0 51.5, LiveCodeBench v6 80.4. The dense 27B scores about the same on SWE-bench, but it reads all ~27B weights for every token while the 35B-A3B reads ~3B active, so on the same card the 35B should decode several times faster (estimate, not measured here). In an agent loop that speed is the difference between waiting seconds and waiting minutes per step.

Official Qwen model-card scores. Third-party. Read 2026-10-31.
BenchmarkQwen3.6-35B-A3BQwen3.5-27B (dense)Gemma 4 31BGemma 4 26B-A4B
SWE-bench Verified73.475.052.017.4
SWE-bench Pro49.551.235.713.8
Terminal-Bench 2.051.541.642.934.2
LiveCodeBench v680.480.780.077.1

Why context decides the card

Qwen’s card says to keep at least 128K context to preserve thinking capabilities. SWE-bench runs used a 200K window; Terminal-Bench used 256K. One 32 GB R9700 holds the Q5 at 262K on the local desktop. A 24 GB or 16 GB card must spill experts to system RAM. Two R9700s fit, but for one user a split is slower than one card; a second card is for a second 35B copy (two agents at once).

35B-A3B Q5 at 262K, all on GPU?
CardFits fully at 262K?
1× 32 GB (R9700)Yes (local desktop daily setup)
1× 24 GBNo: experts spill to system RAM; slower
1× 16 GBNo: experts in RAM
2× R9700Fits as two copies; a split is slower for one user

Connect it

Point Claude Code, Cline, OpenCode, Aider, Continue, or Codex CLI at llama-server /v1. The house file is Qwen3.6-35B-A3B-UD-Q5_K_XL.gguf at -c 262144. Attach steps live on the coding-assistant setup page. Most readers do not need more RAM for this model, because it never leaves the card. 96 GB DDR5 is still the house kit if you later add Flash.

What to buy

One R9700 is the whole GPU answer for a single coder. We omit a street price. Check the seller on marketplace listings.

Where to buy an R9700

FAQ

What is the best local coding model for 32GB VRAM?
Qwen3.6-35B-A3B at Q5 (UD-Q5_K_XL) on one 32 GB Radeon. It holds 262K context on the card. Official coding scores are on the Qwen card. Speed is measured on the local desktop with llama.cpp.
This page
Can Qwen3.6 35B run on one GPU with full context?
Yes on 32 GB. The local desktop daily driver is one R9700, UD-Q5_K_XL, 262K, f16 KV.
R9700
How much context do coding agents need?
Qwen recommends at least 128K. The published SWE and Terminal-Bench numbers used 200K–256K. Size the server at 262,144 when the card holds it.
Coding assistant setup

Sources

How we test — Measured cells cite official amdai-bench/run@1 cards. Estimates stay labeled. Q3 is estimate-only. Q1/Q2 stay off.

Next steps

Real pages on this site. We do not invent a next click.

esc

Type to filter. Enter opens the first match. Full-text search lives on /search.