Connect Qwen3-Coder-Next to Cline in VS Code for a private local coding assistant. The example changes a supplied calculator project, then checks the diff and runs independent tests.
Estimated for the supplied small task at 32K context. GPU rows need a supported Ollama backend. The 80B model does not fit entirely in a 32 GB card.
| Machine | Qwen3-Coder-Next 80B · Q4 | Qwen3-Coder-Next 80B · Uncensored Q4 |
|---|---|---|
| NVIDIA · 32 GB VRAM + 64 GB RAM | Runs with CPU offload; close other apps | Runs with CPU offload; close other apps |
| NVIDIA · 80 GB VRAM + 128 GB RAM | Comfortable full-GPU starting estimate | Comfortable full-GPU starting estimate |
| AMD · 24 GB VRAM + 64 GB RAM | CPU offload; supported ROCm/Vulkan driver required | CPU offload; supported ROCm/Vulkan driver required |
| Intel · 24 GB VRAM + 64 GB RAM | CPU offload; supported Vulkan backend required | CPU offload; supported Vulkan backend required |
| Apple Silicon · 64 GB unified memory | Tight at 32K; close other apps and check pressure | Tight at 32K; close other apps and check pressure |
| Apple Silicon · 96 GB unified memory | Recommended unified-memory starting point | Recommended unified-memory starting point |
| CPU only · 64 GB system RAM | Tight and slow; 128 GB RAM is more comfortable | Tight and slow; 128 GB RAM is more comfortable |
Context includes client instructions, tool calls, files and replies—not just your prompt. Keep the first example small.
| Machine | Qwen3-Coder-Next 80B · Q4 | Qwen3-Coder-Next 80B · Uncensored Q4 |
|---|---|---|
| 32 GB GPU + 64 GB RAM / 64 GB Mac | Start at 32,768 tokens; Compact Prompt and small files | Start at 32,768 tokens; Compact Prompt and small files |
| 80 GB GPU + 128 GB RAM / 96 GB Mac | Start at 32,768; optional 65,536 after memory check | Start at 32,768; optional 65,536 after memory check |
| CPU · 128 GB RAM | Start at 32,768; expect slower tool iterations | Start at 32,768; expect slower tool iterations |
The optional 64K preset is separate. Match Cline to the selected preset and verify the actual allocation with ollama ps. For larger repositories, limit scope or use more memory.
Set up a local coding assistant in VS Code with Cline. For the example, open the supplied calculator project, ask for a small change, and verify the result. Choose official or uncensored Q4; every choice includes Windows, Mac and Linux instructions.
Select the weights you want. The instructions, downloads and settings change with your choice.
Save your machine in My Hardware to get an automatic starting choice. You can always choose any package yourself.
Start at 32,768 tokens for this small Cline task with Compact Prompt. The 52 GB package can offload on a 32 GB GPU with 64 GB RAM; close other apps. 96 GB Mac or 80 GB VRAM is a more comfortable estimate. Longer context uses more memory; general agent workloads may need 64K or more.
Choose where you want to run it. The instructions below update to match your selection.
Native Ollama + Cline route. GPU acceleration depends on the exact driver/backend; CPU offload remains available.
Download the native Ollama installer, run it, and launch the tray app. Keep it running. Open a new PowerShell window for this guide. Install the current NVIDIA driver, supported AMD ROCm/Vulkan driver, or Intel Vulkan driver for your exact card. CPU inference is also available. These instructions do not require WSL. If it is already installed and running, skip installation.
Download Ollama for Windows Ollama GPU and driver supportInstall Visual Studio Code for Windows, then open the linked Cline extension and choose Install. Install the current Node.js LTS release as well; it supplies the built-in test runner used below. Open a new PowerShell after installing it. The next step supplies the project folder to open in VS Code.
Download Visual Studio Code Install Cline extension Download Node.js LTSDownload the ZIP below and extract it with File Explorer → Extract All. Move the extracted yourunai-coding-official-q4 folder into your home folder. Open this folder in VS Code using File → Open Folder. The starter contains calculator.mjs, its baseline tests, an independent acceptance checker, and the 32K/64K model presets.
Download prepared coding projectIn PowerShell, run these commands from the extracted folder. They download the exact selected package once and create its 32K preset using the supplied Modelfile. In VS Code you can use Terminal → New Terminal for the remaining commands. Keep at least 75 GB disk space for this full 80B Q4 package and runtime.
Exact selected package Persistent Ollama settingsSet-Location "$HOME\yourunai-coding-official-q4"
ollama pull qwen3-coder-next:q4_K_M
ollama create yourunai-coder-coding-official-q4-32k -f ModelfileIn VS Code, open calculator.mjs and calculator.test.mjs. This deliberately small project exports addition and subtraction; multiplication is the change Cline will make. In the integrated PowerShell terminal, run the baseline test below; both tests should pass. check-result.mjs is the separate acceptance checker—leave it unchanged, and do not run it until the change is complete.
node --test calculator.test.mjsOpen Cline Settings. Set provider to Ollama, Base URL to http://localhost:11434 and exact model ID to yourunai-coder-coding-official-q4-32k. Select this model for both Plan and Act if separate settings are enabled. In Features enable Use Compact Prompt. Set Cline's Ollama context size to 32768 if the field is shown; it must agree with the saved preset. Leave Auto Approve and YOLO off for this first run. Approve workspace reads and intended edits individually; browser access, MCP and unrelated shell commands are unnecessary. Keep this task confined to the open demo folder.
Cline local-model connection Cline permissionsIn the Cline message box, paste: “Read calculator.mjs and calculator.test.mjs. Add an exported multiply(a, b) function without changing addition or subtraction. Add three multiplication tests: positive, zero and negative inputs. Do not edit check-result.mjs or add dependencies. Run node --test calculator.test.mjs, then node check-result.mjs. Show the diff and test results.” Use Act mode when ready, inspect each proposed edit, then approve only those two file edits and the two named test commands. This is a tool-using code change in your actual project, not a chat-only code snippet.
In VS Code inspect the changed calculator and tests. Confirm multiply uses both arguments and the original functions remain. Then run the commands below from the demo folder in PowerShell. Expect five tests passing and the independent PASS line. If a check fails, give Cline the exact error and request a focused fix without changing the acceptance checker.
node --test calculator.test.mjs
node check-result.mjsThe 32K preset is for this deliberately small example with Compact Prompt, not an entire repository. General coding and agent work may need 64K or more. If memory is comfortable, this optional PowerShell block creates a separate 65536-token preset. Select yourunai-coder-coding-official-q4-64k in Cline, match its context setting to 65536, start a new task and check ollama ps. If latency or memory pressure rises, switch back to the 32K preset and narrow the task. The starter already includes Modelfile-64k; no file editing is needed.
Context length and memoryollama create yourunai-coder-coding-official-q4-64k -f Modelfile-64kClick Cancel in Cline to stop a running task. In PowerShell, the command below unloads only this preset; saved files remain in the demo folder. Next time, open Ollama, reopen that folder in VS Code and choose the same local preset in Cline. The first request loads it again. Start a fresh Cline task for a new goal instead of carrying unrelated files through one long conversation.
ollama stop yourunai-coder-coding-official-q4-32kCline changes the two requested files, all five tests pass, the unchanged independent checker prints PASS, and you have inspected the diff. The preset and workspace can be reopened later.
Source-checked instructions and estimated hardware requirements; this exact application/model task has not been physically executed by YouRunAI. The uncensored package is a Huihui community derivative; its behavior and tool reliability can differ from the official package.
Keep the Ollama app/service running, confirm ollama list shows the named 32K preset, and use provider Ollama with http://localhost:11434. Refresh the model list and select the same preset for Plan and Act.
Cancel the task. Enable Compact Prompt, use the official Q4 package first, confirm context is 32768 with ollama ps and start a fresh task restricted to the supplied files. Do not repeatedly approve unrelated actions. A community variant may be less reliable at tools.
Close other loaded models and large apps. Q4 still downloads 52 GB; a 32 GB GPU uses CPU/RAM offload. Return from the optional 64K preset to 32K, start a fresh small task and inspect the processor split. 96 GB unified memory or a larger GPU gives more headroom.
Check the exact GPU/OS on Ollama’s hardware support page, install its documented driver and restart the running Ollama app/service. Verify the CPU/GPU split with ollama ps while Cline is responding.
Run the independent check yourself in the same workspace. Give Cline the exact failing assertion and ask it to repair the calculator without changing check-result.mjs. Inspect the new diff before accepting it.
Original instructions, model files, and compatibility notes behind this setup.
Source-backed package and platform-route plan for private local chat with Qwen3.5 · 9B. Preserves the official Ollama 9B package, a smaller 4B family fallback, and a clearly labeled community uncensored GGUF option.
Run Qwen3.8 27B with Ollama, connect it to Cline in VS Code, and make one reviewable code change in a tiny local project.
Generate images from text prompts in ComfyUI with the fast distilled or more adjustable base 4B model. Save your results and reuse the visual workflow.